Abstract: Snapshots of a first logical storage unit (LSU) (R1) on a first storage system (A1) may be taken while replication is inactive between A1 and a second storage system (A2), such that these outstanding snapshots are not replicated to a second replica LSU (R2) on A2. Upon replication becoming active, the outstanding snapshots may be replicated to R2 without disrupting or impairing the remote replication of write operations between R1 and R2 as part of standard remote replication. A process on A1 executing the replication of the outstanding snapshots from R1 to R2 may be a separate process than one or more processes on A1 executing standard remote replication including the replication of write operations from R1 to R2. The process may be given low priority on A1 so as to not impair performance of other operations, including standard remote replication and replicating outstanding write operations on A1.

Abstract: Snapshots from a first LSU (R1) on a first storage system (A1) may be replicated to a second replica LSU (R2) on a second storage system (A2), for example, concurrently to remotely replicating (e.g., synchronously) write operations for R1 to R2. A process, P, on A1 executing the replication of the snapshots from R1 to R2 may be a separate process than the one or more processes on A1 executing remote replication of write operations for R1 to R2. During a consistency window on A1, outstanding write operations for R1 at the time the consistency window opened may be logged, and a pair of snapshots, SS11 and SS12 may be activated on R1 and R2, respectively. After the consistency window has closed, the SS12 snapshot metadata and snapshot data may be updated based on the outstanding write operations.

Abstract: Snapshots may be remotely replicated asynchronously from a first LSU (R1) on a first storage system (A) to a second replica LSU (R2) on a second storage system (A2). The storage system A1 may open a consistency window to suspend initiating processing of new write operations received on A1. While the consistency window is open, A1 may: take a first snapshot, SS11, of R1; record, in association with the first replication cycle, an indication to replicate SS11 on A2; and initiate a next replication cycle to record write operations of the next new write requests to be received from hosts. After initiating a next replication cycle, A1 may close the consistency and transmit the first replication cycle to A2. A2 may apply the write operations of the first replication cycle to R2, and then take a second snapshot SS12 of R2, which should be a replica of SS11.

Abstract: A target-less point in time image (snapshot) of a storage volume is allowed to be built after activation, by enabling the snapshot data to be modified to create a crash-consistent replica of the source data after the snapshot has been activated. The data of the snapshot remains immutable from a user standpoint, but the snapshot is able to be quickly activated before all of the data of the snapshot has been included in the snapshot, to thus reduce an amount of time IO operations on the source volume are quiesced. A first snapshot of a storage volume is created on a primary storage system and a corresponding second snapshot of the storage volume is activated on a backup storage system before all the data of the first snapshot is received at the backup storage system. Entries of the activated second snapshot are then changed to point to correct back-end allocations.

Abstract: A wiring clip is provided for securing one or more conductors to a stud. The wiring clip can include a support portion configured to engage the one or more wires and an attachment portion that at least partly defines an inner recess that can be configured to receive the stud. The attachment portion can be configured to secure the wiring clip to the stud without the use of separate fasteners, including through selectively engagement of hooks of the attachment portion with open or closed sides of the stud.

Abstract: Storage objects and targetless snaps of the storage objects are represented using a system replication data pointer table (SRT), direct index lookup (DIL) tables, and virtual replication data pointer tables (VRTs). The SRT is a system level track-based data structure that stores metadata indicative of the actual (physical layer) allocations for all targetless snapshots in a storage array. The size of the SRT in terms of total entries corresponds to the overall storage capacity of the managed drives of the storage array. Each utilized entry of the SRT includes backend metadata with a pointer to a managed drive and metadata that identifies the associated storage object and track via the VRTs and DIL tables. SRT metadata is created and discarded as backend allocations are utilized and freed so the SRT is a dynamic data structure that can efficiently adjust its size and corresponding memory requirements.

Abstract: An IoT Smart Sound Level Meter that is connected through the internet via ethernet cable, wifi or cellular network. The IoT Smart Sound Level Meter measures and monitors sound pressure levels. Sound pressure levels are measured in decibels. The sound pressure level data that is sent via the internet through ethernet, wifi or cellular network to cloud servers where the data is stored and saved. The cloud servers are connected to Application Programming Interfaces (API) connected to web-based software that converts the sound pressure level data into decibel measurements. These measurements are displayed to the end-user through the web-based software and/or application providing real-time decibel level measurements and historic sound pressure level recordings. The web-based software and/or application provides access to view decibel measurement data remotely from a computer, laptop, tablet, smart watch, or mobile device.

Abstract: A silk blend ballistic fabric for creating comfortable and flexible bulletproof apparel includes a plurality of silk threads and a plurality of para-aramid fiber threads interwoven with the plurality of silk threads to create a fabric. An alternative embodiment of the disclosure generally comprises a hybrid thread comprising a silk thread and a para-aramid fiber thread twisted with the silk thread. The resulting hybrid thread can be woven to create the fabric. The resulting fabric is bulletproof and substantially flexible to create articles of clothing such as, but not limited to, trousers, shirts, and the like.

Abstract: A snapshot for use in a cascaded snapshot environment includes a device level source sequence number and a Direct Image Lookup (DIL) data structure. The device level source sequence number indicates the level of the snapshot in the cascade, and the snapshot DIL indicates the location of the data within the snapshot cascade. A target device for use in the cascaded snapshot environment includes a device level target sequence number, a track level sequence data structure, and a DIL. When the target device is linked to a snapshot, the device level target sequence number is incremented, which invalidates all tracks of the target device. The snapshot DIL is copied to the target device, but a define process is not run on the target device such that the tracks of the target device remain undefined. IO operations use the device level target sequence number to identify data on the target device.

Abstract: Snapshot metadata may include a plurality of pages of nodes, including active nodes and free nodes. It may be determined whether a snapshot metadata object is eligible for de-allocation, for example, of one or more of the pages of its snapshot metadata nodes. This determination may be based on a number of free nodes in the snapshot metadata object, for example, in relation to the quantity of nodes that are included in a snapshot metadata page. This determination may be made based on previous usage of the nodes allocated to the snapshot metadata object, for example, the number of active nodes relative to a total size of the snapshot metadata object. For example, a maximum extent of active nodes during one or more periods may be compared to a current extent of active nodes to determine whether the snapshot metadata object is eligible.

Abstract: A snapshot lookup table (SLT) and snapshot pointer structure(s) (SPSs) may be provided for a logical data unit (LSU), each SPS entry corresponding to an LSU data portion and a physical storage location at which data is stored for the data portion for a particular snapshot. A current lookup table (CLT) for a current time may be provided for an LSU, including an entry for each LSU data that points to a respective entry of an SPS. Each time a first write following the creation of a snapshot is made to an LSU data portion, the corresponding CLT entry may be updated to point to the SPS entry that was updated to point to an LSU track table entry. To create a snapshot, a snapshot lookup table (SLT) is created for each snapshot, and the contents of the CLT are copied to the newly created SLT.

Abstract: A snapshot for use in a cascaded snapshot environment includes a device level source sequence number and a Direct Image Lookup (DIL) data structure. The device level source sequence number indicates the level of the snapshot in the cascade, and the snapshot DIL indicates the location of the data within the snapshot cascade. A target device for use in the cascaded snapshot environment includes a device level target sequence number, a track level sequence data structure, and a DIL. When the target device is linked to a snapshot, the device level target sequence number is incremented, which invalidates all tracks of the target device. The snapshot DIL is copied to the target device, but a define process is not run on the target device such that the tracks of the target device remain undefined. IO operations use the device level target sequence number to identify data on the target device.

Abstract: Providing automated targetless snapshots for storage volumes includes estimating storage space needed for a new set of the snapshots based on an amount of expected change of data on the storage volumes, deleting current snapshots to free up an amount of space corresponding to estimated storage space for the new set of the snapshots, and creating the new set of the snapshots. The current snapshots may be selected for deletion based on creation date of the snapshots. Snapshots with an oldest creation data may be deleted. The storage volumes may be provided on a storage system. The storage system may show storage space used by the snapshots as unallocated. Storage space used by the snapshots may be managed by a storage resource pool. The storage resource pool may convert storage space shown as unallocated into allocated storage space in response to snapshots provided therein being converted into accessible snapshots.

Abstract: Embodiments of the present disclosure relate to autonomous data protection. One or more input/output (I/O) streams can be received by one or more storage devices. One or more snapshots of each storage device can be obtained. One or more anomalies can be identified based on a change rate corresponding to each storage device's memory allocated to store user data included in the I/O streams.

Abstract: A no-copy clone of a logical storage unit is created. A define process is initiated for defining a target logical storage unit as the clone before activation of the target logical storage unit. By initiating the define process before activating the logical storage unit, there is a greater likelihood that, when a write operation is received for a data portion on the source logical storage unit or target logical storage unit after activation of the target LSU, the data portion will already be defined and not need to be defined when performing the write operation. When a write operation is received at the source logical storage unit, if the target logical storage unit is not active yet, the data of the write operation may be written to an allocated physical location for the data portion shared between the source and target logical storage units without updating any clone metadata.

Abstract: Embodiments of the present disclosure relate to autonomous data protection. An input/output (I/O) stream can be received for a storage device. One or more anomalies corresponding to the I/O stream can be identified. At least one of the one or more anomalies can be offloaded anomalies to a remote storage based on a capacity of memory allocated to store at least one snapshot of the storage device that include at least one of the one or more anomalies.

Abstract: A method implements an embedded remote desktop in integrated module. An integrated application is received, by a client device, from an integrated server. The integrated application includes an access link to a remote server and integrated application content that references live information from a live application. The live application is executing concurrently with the integrated application and is configured to produce the live information responsive to the integrated application content. A connection is established to the remote application. The remote application establishes a connection to the live application. The live information is received at the client device. A user input is received responsive to the live information. The user input is transmitted to the integrated server.

Abstract: Snapshots may be managed on a data storage system including logical storage unit including data portions. For a first logical storage unit, a first snapshot pointer structure may be provided including entries, each entry corresponding to a physical storage location at which data is stored for a data portion of the first logical storage unit at a particular point in time. A first virtual snapshot lookup table may be provided for a first portion of the first logical storage unit, the first virtual snapshot lookup table including a plurality of entries, each entry corresponding to a respective data portion of the first logical storage unit and including a reference to a respective entry of the first snapshot pointer structure. The virtual lookup table may correspond to multiple snapshots of the first logical storage unit that have a same value for each data portion of the at least first portion.

Abstract: Storage objects and targetless snaps of the storage objects are represented using a system replication data pointer table (SRT), direct index lookup (DIL) tables, and virtual replication data pointer tables (VRTs). The SRT is a system level track-based data structure that stores metadata indicative of the actual (physical layer) allocations for all targetless snapshots in a storage array. The size of the SRT in terms of total entries corresponds to the overall storage capacity of the managed drives of the storage array. Each utilized entry of the SRT includes backend metadata with a pointer to a managed drive and metadata that identifies the associated storage object and track via the VRTs and DIL tables. SRT metadata is created and discarded as backend allocations are utilized and freed so the SRT is a dynamic data structure that can efficiently adjust its size and corresponding memory requirements.

Abstract: A first direct index lookup table represents the current state of a storage object using entries with references corresponding to tracks of the storage object. A second direct index lookup table represents a first targetless snapshot of the storage object. A virtual replication data pointer table maps the entries of both the first direct index lookup table and the entries of the second direct index lookup table to backend storage via a system replication data pointer table. Updates to the storage object are represented using new entries in the first direct index lookup table and the system replication data pointer table. Movement of a track that is represented in multiple targetless snapshots that are represented by multiple direct index lookup tables is represented by updating the corresponding virtual replication data pointer table and system replication data pointer table rather than updating each of the direct index lookup tables.