An illustrative storage management appliance is interposed between client computing devices and one or more cloud storage resources. The appliance uses cloud storage resources in conjunction with a network attached storage device configured within the appliance to provide to the client computing devices seemingly unlimited network attached storage on respective network shares. The storage management appliance monitors data objects on the network shares and when a data object meets one or more criteria for archiving, the storage management appliance archives the data object to a cloud storage resource and replaces it with a stub and preview image on the network share. When access to the stub and/or preview image is detected, the storage management appliance restores the data object from the cloud storage resource. The criteria for archiving flexibly allow individual data objects to be archived to cloud storage without archiving frequently-accessed “neighboring” data objects on the same network share.

An illustrative storage management appliance is interposed between client computing devices and one or more cloud storage resources. The appliance uses cloud storage resources in conjunction with a network attached storage device configured within the appliance to provide to the client computing devices seemingly unlimited network attached storage on respective network shares. The storage management appliance monitors data objects on the network shares and when a data object meets one or more criteria for archiving, the storage management appliance archives the data object to a cloud storage resource and replaces it with a stub and preview image on the network share. When access to the stub and/or preview image is detected, the storage management appliance restores the data object from the cloud storage resource. The criteria for archiving flexibly allow individual data objects to be archived to cloud storage without archiving frequently-accessed “neighboring” data objects on the same network share.

A method of recording layer-2 (L2) mappings created for workloads executing on a plurality of hosts in a first database managed by a network management server: upon receipt of a first mapping reported by a first host, determining that the first mapping is not recorded in the first database; and in response to the determining that the received first mapping is not recorded in the first database, generating a first timestamp and persisting a first record in the first database that includes the first mapping and the first timestamp.

A method of migrating a network file copy (NFC) operation from a first host computing device to a second host computing device includes the steps of: transmitting a first request to the first host computing device to execute the NFC operation, wherein the NFC operation comprises transferring data from a shared datastore to another datastore; after transmitting the first request, selecting the second host computing device to complete the NFC operation in place of the first host computing device, and transmitting a second request to the first host computing device to stop executing the NFC operation; after transmitting the second request, detecting a message indicating that the first host computing device completed the copying of a first portion of the data; and in response to the detection of the message, transmitting a third request to the second host computing device to perform the remainder of the NFC operation.

Systems and methods for managing concurrent secure elements on a mobile device to coordinate with an application or “app” running on the mobile device and an appropriate communications protocol for conducting transactions using the mobile device include: informing, by the processor, the reader device of a preferred app and a communication protocol usable by the preferred app; receiving, by the processor, information about which apps and communication protocols are supported by a reader for processing a transaction; locating, by the processor, a secure element supporting an app and a communication protocol supported by the reader; channeling the communication protocol for the specific configuration of the app and the supporting secure element; activating the secure element that supports the app; and processing, with the activated secure element, using the supported app and communication channel, the transaction with the reader.

Systems and methods for managing concurrent secure elements on a mobile device to coordinate with an application or “app” running on the mobile device and an appropriate communications protocol for conducting transactions using the mobile device include: informing, by the processor, the reader device of a preferred app and a communication protocol usable by the preferred app; receiving, by the processor, information about which apps and communication protocols are supported by a reader for processing a transaction; locating, by the processor, a secure element supporting an app and a communication protocol supported by the reader; channeling the communication protocol for the specific configuration of the app and the supporting secure element; activating the secure element that supports the app; and processing, with the activated secure element, using the supported app and communication channel, the transaction with the reader.

Self-replicating management services for distributed computing architectures are provided herein. An example method includes providing one or more nodes providing services; and maintaining a quorum of a plurality of management servers by: providing a distributed coordination service for the one or more nodes on each of the plurality of management servers; managing, via a director, requests for data on the distributed coordination service from the one or more nodes; promoting at least one of the one or more nodes to being one of the plurality of management servers; and maintaining secure tunnels between the plurality of management servers and the one or more nodes.

Self-replicating management services for distributed computing architectures are provided herein. An example method includes providing one or more nodes providing services; and maintaining a quorum of a plurality of management servers by: providing a distributed coordination service for the one or more nodes on each of the plurality of management servers; managing, via a director, requests for data on the distributed coordination service from the one or more nodes; promoting at least one of the one or more nodes to being one of the plurality of management servers; and maintaining secure tunnels between the plurality of management servers and the one or more nodes.

Systems and methods for namespace masking in an integration flow. In order to mitigate issues arising due to application updates impacting integration flows, during the metadata generation phase, all the elements which are available for operation selection can be cloned and replaced with a new namespace. The original elements are deleted from the metadata. The systems and methods can maintain the original namespace and the element name at a predefined place in the metadata (e.g., as an attribute of the cloned Element). The cloned element in addition to all the original fields of the element, can have one additional field which will store the value of the original namespace.

Various systems and methods are provided in which a replication process is initiated between a primary site and a recovery site, each having plurality of gateway appliances. Replication loads are evaluated for each given gateway appliance of the plurality of gateway appliances. If a determination is made that at least one gateway appliance of the plurality of gateway appliances is not overloaded, the plurality of gateway appliances are sorted based on replication loads respectively associated with each gateway appliance, and a determination is made as to whether a relative difference in replication loads between a gateway appliance having a highest replication load and a gateway appliance having a lowest replication load exceeds a difference threshold to determine whether the replication workloads between the gateway appliances should be rebalanced.