A method for constructing a persistent memory index in a non-uniform memory access architecture includes: maintaining partial persistent views in a persistent memory and maintaining a global volatile view in a DRAM; an underlying persistent memory index processing a request in a foreground thread when cold data is accessed; when hot data is accessed, reading a key-value pair for a piece of hot data in the global volatile view in response to a query operation carried in the request, and in response to an insert/update/delete operation carried in the request, updating a local partial persistent view and the global volatile view; and in response to a hotspot migration, a background thread generating new partial persistent views and a new global volatile view, and recycling the partial persistent views and the global volatile view for old hot data into the underlying persistent memory index.

Examples described herein include systems and methods for backing up and recovering a software-defined data center (“SDDC”). In one example, entities of the SDDC, such as virtual machines, hosts, and clusters, can coexist with corresponding entity stores. The entity stores can store current state information for each SDDC entity. For example, an identifier or name of a virtual machine can be stored in that virtual machine's corresponding entity store. When recovery of a controller is needed, the controller can rebuild state information that has changed after the controller was backed up, by retrieving state information from entity stores of the various SDDC entities.

According to some embodiments, a system to manage database management system backups may include a plurality of database services. For each database service, a database backup resource (e.g., a human-readable structured document) may specify desired backup state information (e.g., a buffer size, a schedule, an amount of memory, etc.). A stateless backup operator component may then compare a present backup state of each database service with the associated desired backup state information. When a mismatch is identified between the present backup state of a database service and the associated desired backup state information, that database service may be automatically reconfigured (e.g., in connection with a recover job, backup job, backup configuration job, keystore backup job, etc.) in accordance with the desired backup state information.

A memory image can be captured by generating metadata indicative of a state of volatile memory and/or byte-addressable PMEM at a particular time during execution of a process by an application. This memory image can be persisted without copying the in-memory data into a separate persistent storage by storing the metadata and safekeeping the in-memory data in the volatile memory and/or PMEM. Metadata associated with multiple time-evolved memory images captured can be stored and managed using a linked index scheme. A linked index scheme can be configured in various ways including a full index and a difference-only index. The memory images can be used for various purposes including suspending and later resuming execution of the application process, restoring a failed application to a previous point in time, cloning an application, and recovering an application process to a most recent state in an application log.

Distributed application orchestration management is provided. A first passive member of a set of passive members sends a notification message to other members indicating that the first passive member is initiating start of a distributed application in response to the first passive member validating that a self-restart by a leader member failed. The first passive member compares timestamps associated with an attempt to start the distributed application by other passive members in the set of passive members. The first passive member stops a particular attempt to start the distributed application in response to the first passive member determining that a timestamp associated with the particular attempt to start the distributed application by the first passive member is newer than another timestamp of another passive member. The first passive member designates the other passive member having an older timestamp as a new leader member to continue starting the distributed application.

A method for managing a client environment includes obtaining, by a device emulation orchestration engine in an emulation system, an upgrade estimation time request associated with an application upgrade, in response to the upgrade estimation time request: performing a device emulation container analysis to determine a client device that requires the application upgrade, wherein the client device executes in the client environment, initiating an upgrade emulation using a device emulation container corresponding to the client device, obtaining, from a device emulation agent executing in the device emulation container, an upgrade estimation, and providing the upgrade estimation to the application upgrade monitoring agent.

Disclosed is a server. A server according to an embodiment of the present disclosure includes a gatherer configured to receive a file collection list from an external server, at least one wagon configured to collect data from the external server based on the file collection list received from the gatherer, a historian file configured to store a transmission history or a file collection history, and a destination folder configured to store the data collected by the wagon, and the wagon is further configured to, when an error occurs during data collection, collect data for a file again in which the error occurs. Accordingly, it is possible to quickly collect data again when an error occurs.

The disclosure describes techniques that enable detection of memory leaks of software executing on devices within a computer network. An example network device includes memory and processing circuitry. The processing circuitry monitors a usage of the memory by a software component operating within the network device. The processing circuitry periodically determines a memory growth pattern score for the software component based on the usage of the memory. The processing circuitry also predicts whether the user-level process is experiencing a memory leak based on the memory growth pattern score. The processing circuitry applies confirmation criteria to current memory usage of the software component to confirm that the software component is experiencing the memory leak. When the software component is experiencing the memory leak, the processing circuitry generates an alert.

A separate, central server operating in a system including one or more database server machines and a graphical user interface displayed on a user's computer is disclosed and provides a technological improvement. In one example, computer-readable instructions are stored in computer memory on this shutdown control server. A user, such as a database administrator, may access the shutdown control server to initiate the shutdown, reboot, and/or restart of database services on one or more separate database servers. At least one advantage of such an arrangement is that the shutdown control server provides plug-and-play capabilities that may allow one or more database servers of one or more different database types to concurrently connect to the shutdown control server.

For each respective virtual machine (VM) of a plurality of VMs, a distributed computing system generates a unique Application Binary Interface (ABI) for an operating system for the respective VM, compiles a software application to use the unique ABI, and installs the operating system and the compiled software application on the respective VM. A dispatcher node dispatches, to one or more VMs of the plurality of VMs that provide a service and are in the active mode, request messages for the service. Furthermore, a first host device may determine, in response to software in the first VM invoking a system call in a manner inconsistent with the unique ABI for the operating system of the first VM, that a failover event has occurred. Responsive to the failover event, the distributed computing system fails over from the first VM to a second VM.