Abstract: Techniques for reducing the startup latency of functions in a Functions-as-a-Service (FaaS) infrastructure are provided. In one set of embodiments, a function manager of the FaaS infrastructure can receive a request to invoke a function uploaded to the infrastructure and can retrieve information associated with the function. The retrieved information can include an indicator of whether instances of the function may be sticky (i.e., kept in host system primary memory after function execution is complete), and a list of zero or more host systems in the FaaS infrastructure that currently have an unused sticky instance of the function in their respective primary memories. If the indicator indicates that instances of the function may be sticky and if the list identifies at least one host system with an unused sticky instance of the function in its primary memory, the function manager can select the at least one host system for executing the function.

Abstract: The disclosure provides an approach for distribution of functions among data centers of a cloud system that provides function-as-a-service (FaaS). For example, the disclosure provides one or more function distributors configured to receive a request for loading or executing a function, automatically determine an appropriate data center to load or execute the function, and automatically load or execute the function on the determined data center. In certain embodiments, the function distributors are further configured to determine an appropriate data center to provide storage resources for the function and configure the function to utilize the storage resources of the determined data center.

Abstract: The disclosure provides an approach for distribution of functions among data centers of a cloud system that provides function-as-a-service (FaaS). For example, the disclosure provides one or more function distributors configured to receive a request for loading or executing a function, automatically determine an appropriate data center to load or execute the function, and automatically load or execute the function on the determined data center. In certain embodiments, the function distributors are further configured to determine an appropriate data center to provide storage resources for the function and configure the function to utilize the storage resources of the determined data center.

Abstract: Techniques for reducing the startup latency of functions in a Functions-as-a-Service (FaaS) infrastructure are provided. In one set of embodiments, a function manager of the FaaS infrastructure can receive a request to invoke a function uploaded to the infrastructure and can retrieve information associated with the function. The retrieved information can include an indicator of whether instances of the function may be sticky (i.e., kept in host system primary memory after function execution is complete), and a list of zero or more host systems in the FaaS infrastructure that currently have an unused sticky instance of the function in their respective primary memories. If the indicator indicates that instances of the function may be sticky and if the list identifies at least one host system with an unused sticky instance of the function in its primary memory, the function manager can select the at least one host system for executing the function.

Abstract: The disclosure provides an approach for distribution of functions among data centers of a cloud system that provides function-as-a-service (FaaS). For example, the disclosure provides one or more function distributors configured to receive a request for loading or executing a function, automatically determine an appropriate data center to load or execute the function, and automatically load or execute the function on the determined data center. In certain embodiments, the function distributors are further configured to determine an appropriate data center to provide storage resources for the function and configure the function to utilize the storage resources of the determined data center.

Abstract: In one example, resilient software application upgrades in a virtual datacenter is disclosed, in which network flow data is periodically obtained between a plurality of APPVMs and/or containers and deep packet inspection information from firewalls associated with the obtained network flow data in the virtual datacenter. Dependency relationships between the plurality of APPVMs and/or containers are then obtained based on the periodically obtained network flow data, the periodically obtained deep packet inspection information, and a network flow criteria. An upgrade that is about to happen to a software residing in one or more of the plurality of APPVMs and/or containers is determined. One or more of the plurality of APPVMs and/or containers affected by the software upgrade is determined based on the determined dependency relationships. Snapshots of the affected one or more of the plurality of APPVMs and/or containers are then obtained before initiating the software upgrade.

Abstract: An approach for intercepting and caching Domain Name System (DNS) related data and sharing the cached DNS related data among hypervisors is provided. In an embodiment, a method comprises: receiving a DNS query from a virtual machine, determining whether a DNS reply to the DNS query has been received from a DNS server and whether an Internet Protocol (IP) address has been stored in a local DNS cache; in response to determining that tire DNS reply to the DNS query has been received from the DNS server and the IP address has been stored in the local DNS cache; retrieving the IP address from the local DNS cache; and providing the IP address to the virtual machine.

Abstract: In one example, resilient software application upgrades in a virtual datacenter is disclosed, in which network flow data is periodically obtained between a plurality of APPVMs and/or containers and deep packet inspection information from firewalls associated with the obtained network flow data in the virtual datacenter. Dependency relationships between the plurality of APPVMs and/or containers are then obtained based on the periodically obtained network flow data, the periodically obtained deep packet inspection information, and a network flow criteria. An upgrade that is about to happen to a software residing in one or more of the plurality of APPVMs and/or containers is determined. One or more of the plurality of APPVMs and/or containers affected by the software upgrade is determined based on the determined dependency relationships. Snapshots of the affected one or more of the plurality of APPVMs and/or containers are then obtained before initiating the software upgrade.

Abstract: A method and apparatus for facilitating application recovery using configuration information is described. In one embodiment, a method for facilitating application recovery using configuration information includes accessing information in memory associated with an application configuration that correlates with source computer hardware for operating an application using at least one processor, identifying at least one portion that is to be restored of the application configuration using the at least one processor and applying the at least one portion of the application configuration in the memory to destination computer hardware using the at least one processor.

Abstract: A method for integrating data deduplication with block level incremental data backup is described. In one embodiment, the method includes accessing from memory at least one modified data block of a file, wherein the file is partitioned into a plurality of deduplication segments, identifying at least one deduplication segment that corresponds with the at least one modified data block, computing using at least one processor a signature for each deduplication segment of the at least one corresponding deduplication segment and comparing using at least one processor each signature that is associated with the at least one corresponding deduplication segment with signature information that is associated with backup data to identify at least one duplicate data block within the backup data and the at least one modified data block.

Abstract: A method and apparatus for providing single instance restoration of data files is provided. In one embodiment, a method for using a signature database to provide a single instance data restoration solution includes processing a restore request for a data file, wherein the data file is associated with a signature and examining a signature database using the signature to identify at least one locally available data file having at least one signature that matches the signature associated with the data file.

Abstract: A method and apparatus for continuous data protection is provided. In one embodiment, the method for continuous data protection comprises receiving a write request for writing at least one data segment to storage; computing, using at least one processor, a signature for the at least one segment; comparing, using at least one processor, the signature that is associated with the at least one segment with a plurality of data signatures for previously stored data segments; and processing the data segment in a manner dependent upon whether the signature matches any one of the plurality of data signatures.

Abstract: A method and apparatus for automating device recovery using device configuration information is described. In one embodiment, a method for restoring a configuration of a source device includes accessing device configuration information from memory associated with a plurality of devices to identify using at least one processor a configuration associated with a source device of the plurality of devices, determining using at least one processor a common configuration between the configuration associated with the source device and a configuration associated with a target device and applying, using the at least one processor, the common configuration to the target device.

Abstract: A method and apparatus for providing single instance restoration of data files is provided. In one embodiment, a method for using a signature database to provide a single instance data restoration solution includes processing a restore request for a data file, wherein the data file is associated with a signature and examining a signature database using the signature to identify at least one locally available data file having at least one signature that matches the signature associated with the data file.