Systems and methods are described for implementing load-dependent encryption mechanism selection in an elastic computing system. The elastic computing system can include a set of host devices configured to implement block storage volumes on behalf of users. Users may desire that such volumes be encrypted prior to storing data. It may be generally preferable for encryption to occur on the same host devices that host the volume, to reduce latency and bandwidth usage needed to encrypt the data. However, encryption of data can utilize significant computational resources, which may not be available on host devices that also have sufficient storage resources to host the volume. The present disclosure describes systems and methods that can account for computational resource availability on host devices, selecting “in-place” encryption only when available resources exist on host devices, and otherwise implementing remote encryption of volume data.

Scalable content delivery resource usage is performed by operations including provisioning an initial edge virtualization provisioned with an allocation of local resources and an edge application. The operations further include provisioning additional edge virtualizations in response to an increase in concurrent data requests. The operations may further include provisioning an initial storage virtualization provisioned with an allocation of the local resources and a storage application. The operations further include provisioning an additional storage virtualization in response to an increase in data on the local resources.

A method of reassembling a local disk manager (LDM) and array group (AGRP) includes starting a physical extent manager (PEM) configured to run on a number of nodes. The PEM on each node is configured to manage an AGRP running on the same node. A number of LDMs are reassembled, and each LDM is configured to manage virtual disks on each of the nodes. Once enough LDMs are reassembled, an AGRP can be reassembled.

An apparatus supports single root input/output virtualization (SR-IOV) capable devices. The apparatus includes input/output ports, and SR-IOV capable PCIe devices. Each SR-IOV capable PCIe device has one or more namespaces or controller memory buffers. The SR-IOV capable PCIe device provides one or more physical functions and virtual functions that can access the one or more namespaces or controller memory buffers. A PCIe switch controller communicates with host servers coupled to the input/output ports, and assigns one or more virtual functions to each host device, and enables the host devices to access one or more namespaces or controller memory buffers through the assigned virtual functions. The PCIe device is configured to attach one or more namespaces or one or more partitions of one or more controller memory buffers to each virtual function, set at least one namespace or controller memory buffer to a shared state and allow different host devices to access the same namespace or controller memory buffer using respective assigned virtual functions.

A unique identifier is stored in shared data storage that is accessible to at least a first virtual storage processor and a second virtual storage processor within a virtual storage appliance. The unique identifier is generated when the virtual storage appliance is first started up, and then used by the first virtual storage processor to obtain at least one Internet Protocol (IP) address for use by a management stack that initially executes in the first virtual storage processor. In response to failure of the first virtual storage processor, the unique identifier is used by the second virtual storage processor to obtain, for use by the management stack while the management stack executes in the second virtual storage processor after the failure, the same IP address obtained by the first virtual storage processor.

The present disclosure generally relates to creating virtualized block storage devices whose data is replicated across isolated computing systems to lower risk of data loss even in wide-scale events, such as natural disasters. The virtualized device can include at least two volumes, each of which is implemented in a distinct computing system. Each volume can be implemented by at least two computing devices, a first of which is configured as a primary device to which reads from and writes to the volume are directed. Of the two volumes, one can be indicated as primary, indicating authority to accept reads to and writes from the virtualized device. A primary device of the primary volume, on obtaining a write to the volume, can replicate the write to both a secondary device of a primary volume and to the secondary volume.

Technologies for switching network traffic include a network switch. The network switch includes one or more processors and communication circuitry coupled to the one or more processors. The communication circuity is capable of switching network traffic of multiple link layer protocols. Additionally, the network switch includes one or more memory devices storing instructions that, when executed, cause the network switch to receive, with the communication circuitry through an optical connection, network traffic to be forwarded, and determine a link layer protocol of the received network traffic. The instructions additionally cause the network switch to forward the network traffic as a function of the determined link layer protocol. Other embodiments are also described and claimed.

A backup and restore coordinator configured to receive a plurality of backup and restore requests from at least two uncoordinated backup functionalities implemented in a virtual environment, the virtual environment including a hypervisor hosting a plurality of virtual machines and a backup server. The backup and restore coordinator configured to extract respective information from the plurality of backup and restore requests including target data, backup resource information, and a type of request. The backup and restore coordinator configured to order the plurality of backup and restore requests in a prioritized queue based on the information extracted from the plurality of backup and restore requests.

Reversing deletion of a virtual machine including managing, by a storage system, a repository of virtual machine snapshots on a datastore; receiving, by the storage system, a request to recover a deleted virtual machine from the datastore; accessing, by the storage system, the repository of virtual machine snapshots on the datastore to generate a list of deleted virtual machines associated with virtual machine snapshots in the repository of virtual machine snapshots; receiving, by the storage system, a selection of one of the deleted virtual machines in the list of deleted virtual machines; and recovering, by the storage system, the selected deleted virtual machine using a virtual machine snapshot for the selected deleted virtual machine.

A cellular modem processor can include dedicated processing engines that implement specific, complex data processing operations. The processing engines can be arranged in pipelines, with different processing engines executing different steps in a sequence of operations. Flow control or data synchronization between pipeline stages can be provided using a hybrid of firmware-based flow control and hardware-based data dependency management. Firmware instructions can define data flow by reference to a virtual address space associated with pipeline buffers. A hardware interlock controller within the pipeline can track and enforce the data dependencies for the pipeline.