In one aspect, a computerized method for managing tombstones in a node of a Distributed Database Base System (DDBS) includes the step of providing a rule that, for a namespace in a record of the node of the DDBS that allows expiration, mandates that a later generation's expiration time of the namespace never decreases. The computerized method includes the step of determining that an administrator of the DDBS has set an expiration time of the namespace to infinity. The computerized method includes the step of implementing a background process of the DDBS, wherein the background process scans a DDBS node's drive and flags a set of extant tombstones that are no longer covering viable namespaces or viable records. The computerized method includes the step of deleting all the flagged tombstones.

Methods and apparatus are disclosed to update software on a legacy system without disruption of live applications. In a database server environment, a nameserver restart can utilize a pre-existing hook facility to detect a newly introduced script and execute an initialization function of the script, leading to activation or launch of the script. In a use case of a high availability database server, the script can cause a copy of a replication status to be stored at a remote location. Upon failure of the database server, retrieval and verification of the replication status from the remote location enables failover to a replica server to be performed safely and automatically.

A secondary pool of VMs is used to run secondary services or jobs, which may be evicted upon failure of a corresponding primary VM. Upon detection of a failure of a primary resource, the secondary services or jobs are evicted from secondary pool resources, and the secondary pool resources can be automatically allocated to the jobs of the failed primary resource. In this regard, a secondary job may be thought of as a preemptible job and comprises services or jobs that are lower priority than the service or job on the primary resource. By using computing resources in the secondary pool to run secondary or preemptible jobs, this technology makes use of what would be otherwise idle resources. This beneficially avoids having to allocate additional and separate computing resources for secondary jobs, leads to more efficient use of network resources, and reduces costs.

Each redundancy group is constituted by one active program (storage control software of the active program) and N standby programs (N is an integer of two or more). Each of the N standby programs is associated with a priority to be determined as a failover (FO) destination. In the same redundancy group, FO is performed from the active program to the standby program based on the priority. For the plurality of pieces of storage control software including the active programs and the standby programs that change to be active by FO in the plurality of redundancy groups arranged in the same node, standby storage control software that can set each of the programs as a FO destination are arranged in different nodes.

A three-dimensional stacked integrated circuit (3D SIC) that can have at least a first 3D XPoint (3DXP) die and, in some examples, can have at least a second 3DXP die too. In such examples, the first 3DXP die and the second 3DXP die can be stacked. The 3D SIC can be partitioned into a plurality of columns that are perpendicular to each of the stacked dies. In such examples, when a first column of the plurality of columns is determined as failing, data stored in the first column can be replicated to a second column of the plurality of columns. Also, for example, when a part of a first column of the plurality of columns is determined as failing, data stored in the part of the first column can be replicated to a corresponding part of a second column of the plurality of columns.

Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I/O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).

A resource matching technique between a primary site and one or more secondary sites accommodates a configuration update of a virtual machine (VM) in a disaster recovery (DR) environment. The resource matching technique determines whether a proposed resource configuration update or change to a primary VM running at the primary site is permissible on a secondary VM configured for failover operation at a secondary site in the event of failure to the primary VM. The technique continuously monitors the availability of resources at each secondary site and enables negotiation between the primary and secondary sites of the proposed configuration change based on corresponding indications resource availability. The resources may include generic resources (e.g., memory, storage capacity and CPU processing capacity) and specialized resources (e.g., GPU types and/or models).

A system determines that a primary event processor, included in a primary data center, is associated with a failure. The primary event processor is included in the primary data center and configured to process first events stored in a main event store of the primary data center. The system identifies a secondary event processor, in a secondary data center, that is to process one or more first events based on the failure. The primary event processor and the secondary event processor are configured to process a same type of event. The system causes, based on a configuration associated with the primary or secondary event processor, the one or more first events to be retrieved from one of the main event store or a replica event store. The replica event store is included in the secondary data center and mirrors the main event store of the primary data center.

A method is provided for a hyper-converged storage-compute system to implement an active-active failover architecture for providing Internet Small Computer System Interface (iSCSI) target service. The method intelligently selects multiple hosts to become storage nodes that process iSCSI input/output (I/O) for a target. The method further enables iSCSI persistent reservation (PR) to handle iSCSI I/Os from multiple initiators.

Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I/O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).