Abstract: Systems, devices, and techniques are disclosed for cryptographic key migration. A tenant host may determine a first Key Management Service (KMS) indicated as storing a cryptographic key associated with the tenant host from a new KMS mapping. The tenant host may send a request for the cryptographic key associated with the tenant host to the first KMS. The tenant host may receive an indication from the first KMS that the first KMS does not store the cryptographic key. The tenant host may determine a second KMS indicated as storing the cryptographic key associated with the tenant host from an original KMS mapping. The tenant host may receive the cryptographic key associated with the tenant host from the second KMS. The tenant host may send a request to the second KMS that the cryptographic key associated with the tenant host be replicated from the second KMS to the first KMS.

Abstract: Reference voltage generators including a header circuit configured to pass current from a power supply to a time-to-digital converter, an amount of the current to pass determined by a thermometer code, and logic to update the thermometer code based on a comparison between an output of the time-to-digital converter and a digital code representing a reference voltage level.

Abstract: Power delivery systems for integrated circuits that include a first metal path traversing first metal layers from a global power domain supply to a voltage regulator, a second metal path traversing second metal layers from a local power domain supply to the voltage regulator, and a third metal path traversing third metal layers from the local power domain supply to an integrated circuit. Electrical isolation gaps are formed between the first metal layers, the second metal layers, and the third metal layers.

Abstract: Techniques are provided to manage data on shutdown of a data storage system. For example, a method comprises initiating a process to shut down a data storage system which comprises storage devices that store data associated with one or more non-persistent logical storage resources of a virtual storage layer which is configured by the data storage system. In response to initiating the process to shut down the data storage system, the method comprises: storing configuration data associated with the virtual storage layer, the configuration data comprising unique identifiers associated with the one or more non-persistent logical storage resources; and performing a data backup process to persistently store a copy of the data associated with the one or more non-persistent logical storage resources to a backup storage system.

Abstract: Systems, devices, and techniques are disclosed for cryptographic key migration. A tenant host may determine a first Key Management Service (KMS) indicated as storing a cryptographic key associated with the tenant host from a new KMS mapping. The tenant host may send a request for the cryptographic key associated with the tenant host to the first KMS. The tenant host may receive an indication from the first KMS that the first KMS does not store the cryptographic key. The tenant host may determine a second KMS indicated as storing the cryptographic key associated with the tenant host from an original KMS mapping. The tenant host may receive the cryptographic key associated with the tenant host from the second KMS. The tenant host may send a request to the second KMS that the cryptographic key associated with the tenant host be replicated from the second KMS to the first KMS.

Abstract: Techniques are provided to manage data on shutdown of a data storage system. For example, a method comprises initiating a process to shut down a data storage system which comprises storage devices that store data associated with one or more non-persistent logical storage resources of a virtual storage layer which is configured by the data storage system. In response to initiating the process to shut down the data storage system, the method comprises: storing configuration data associated with the virtual storage layer, the configuration data comprising unique identifiers associated with the one or more non-persistent logical storage resources; and performing a data backup process to persistently store a copy of the data associated with the one or more non-persistent logical storage resources to a backup storage system.

Abstract: A fuel injector (1) including a fuel injector housing (2), a valve seat (4) formed at one end of the fuel injector housing, and a valve body (10) disposed in the fuel injector housing and operable to open and close a spray hole (20) in the valve seat. The valve seat includes a base portion (16) and insert portion (26) having spray holes (8) that is secured to the base portion (16).

Abstract: A method, computer program product, and computing system for locally processing a plurality of data files stored on a local data storage system to effectuate the storage of one or more archivable files at one or more defined remote addresses on a remote data storage system. One or more identifiers, that locate the one or more archivable files at the one or more defined remote addresses on the remote data storage system, are stored on the local data storage system. A local database, that defines the one or more identifiers, is maintained on the local data storage system.

Abstract: Techniques are presented for dynamically allocating memory between containers.

Abstract: Described herein is a system that provides data service failover in shared storage clusters. An example shared storage cluster can include multiple data node devices equipped to access to a shared storage location. Each of the data node devices can host multiple network attached storage (NAS) servers. For each NAS server at a data node device, a different data node device in the shared storage cluster can be designated as a backup node. The designated backup nodes for NAS servers at any one data node device in the shared storage cluster can be distributed across multiple other data node devices in the shared storage cluster, thereby sharing the burden of data node device failure across multiple other data node devices.

Abstract: A fuel injector including a fuel injector housing (2), a valve seat (4) formed at one end of the fuel injector housing (2), and a valve body (10) disposed in the fuel injector housing (2) and operable to open and close a spray hole (8) in the valve seat. The valve seat (4) includes abase portion (16) and insert portion (26) having spray holes (8) that is secured to the base portion (16).

Abstract: A fuel injector including a fuel injector housing (2), a valve seat (4) formed at one end of the fuel injector housing (2), and a valve body (10) disposed in the fuel injector housing (2) and operable to open and close a spray hole in the valve seat (4). The valve seat (4) includes a base portion (16) and insert portion (26) having spray holes (8) that is secured to the base portion (16).

Abstract: A technique for managing data objects in a data storage cluster realizes an application-accessible data object within a file that belongs to an internal file system. The internal file system runs on a computing node of the cluster and is backed by a LUN realized in block storage. The storage cluster achieves snapshots of the data object at the level of the file system, e.g., by snapshotting the file, such that the data object and its snapshots are all backed by the same LUN in the block storage.

Abstract: A fuel injector (1) including a fuel injector housing (2), a valve seat (4) formed at one end of the fuel injector housing, and a valve body (10) disposed in the fuel injector housing and operable to open and close a spray hole (20) in the valve seat. The valve seat includes a base portion (16) and insert portion (26) having spray holes (8) that is secured to the base portion (16).

Abstract: A technique for replicating file systems to any number of targets includes obtaining a writeable snapshot of a file system on a source, performing cloud tiering of files in the snapshot, replacing the file contents of the snapshot with stubs pointing to the cloud, and generating a namespace backup of the snapshot that includes directories and stubs. The source system ships the namespace backup to the cloud, allowing any authorized target system to restore from the namespace backup to a local file-system replica, such that contents of the cloud-tiered files are made accessible on the target system from the restored namespace via the stubs.

Abstract: A fuel injector including a fuel injector housing, a valve seat formed at one end of the fuel injector housing, and a valve body disposed in the fuel injector housing and operable to open and close a spray hole in the valve seat. The valve seat includes a base portion and insert portion having spray holes that is secured to the base portion.

Abstract: Described herein is a system that provides data service failover in shared storage clusters. An example shared storage cluster can include multiple data node devices equipped to access to a shared storage location. Each of the data node devices can host multiple network attached storage (NAS) servers. For each NAS server at a data node device, a different data node device in the shared storage cluster can be designated as a backup node. The designated backup nodes for NAS servers at any one data node device in the shared storage cluster can be distributed across multiple other data node devices in the shared storage cluster, thereby sharing the burden of data node device failure across multiple other data node devices.

Abstract: An apparatus in one embodiment comprises a storage system having at least first and second storage tiers each comprising a plurality of storage devices. The first storage tier implements a file system having a user visible name space and a corresponding hidden data store. The second storage tier implements a cloud-based object store. The storage system is configured to controllably relocate files from the hidden data store of the file system of the first storage tier to the cloud-based object store of the second storage tier. In conjunction with the relocation of a given one of the files, the given file is replaced in the hidden data store with a corresponding stub providing user access via the user visible name space to an object comprising the given file in the cloud-based object store of the second storage tier. The controllable relocation is illustratively performed in accordance with one or more configured policies.

Abstract: A method, computer program product, and computing system for locally processing a plurality of data files stored on a local data storage system to identify an archivable file for storage on a remote data storage system. A remote tiering appliance is enabled to obtain the archivable file, wherein the remote tiering appliance stores the archivable file at a defined remote address on the remote data storage system. An identifier is received from the remote tiering appliance that locates the archivable file at the defined remote address on the remote data storage system. The identifier is stored on the local data storage system.

Abstract: An apparatus comprises a storage system comprising a plurality of storage nodes each comprising one or more storage devices. Each of the storage nodes further comprises a network protocol target configured to receive delivery of input-output (IO) operations from a network protocol initiator of a host device, a data server configured to execute the IO operations on a given storage node, and a data client configured to communicate the IO operations to at least one of the data server on the given storage node and one or more data servers corresponding to one or more additional ones of the plurality of storage nodes. The data client has knowledge of a distribution of data across the plurality of storage nodes.