Patent classifications
G06F11/2046
SELF-HEALING VIRTUALIZED FILE SERVER
In one embodiment, a system for managing a virtualization environment comprises a plurality of host machines, one or more virtual disks comprising a plurality of storage devices, a virtualized file server (VFS) comprising a plurality of file server virtual machines (FSVMs), wherein each of the FSVMs is running on one of the host machines and conducts I/O transactions with the one or more virtual disks, and a virtualized file server self-healing system configured to identify one or more corrupt units of stored data at one or more levels of a storage hierarchy associated with the storage devices, wherein the levels comprise one or more of file level, filesystem level, and storage level, and when data corruption is detected, cause each FSVM on which at least a portion of the unit of stored data is located to recover the unit of stored data.
Processing apparatus, process system, and non-transitory computer-readable recording medium
A processing apparatus includes a precursor detection unit that detects a precursor event indicating a precursor that a target process cannot be executed by a process unit, and a control unit that sends a preparation request to a substitution processing apparatus when the precursor detection unit detects the precursor event in which the preparation request requests the substitution processing apparatus being a ready state for starting a substitution processing. The control unit sends a termination request to the substitution processing apparatus when a predetermined condition is satisfied after the control unit sends the preparation request, in which the termination request requests the substitution processing apparatus terminating the ready state.
Virtual machine recovery on non-shared storage in a single virtual infrastructure management instance
Techniques for enabling virtual machine (VM) recovery on non-shared storage in a single virtual infrastructure management server (VIMS) instance are provided. In one set of embodiments, a VIMS instance can receive an indication that a VM in a first cluster of the VIMS instance has failed, and can determine whether the VM's files were being replicated to a storage component of the VIMS instance at the time of the VM's failure. If the VM's files were being replicated at the time of the failure, the VIMS instance can search for and identify a cluster of the VIMS instance and a host system within the cluster that (1) are compatible with the VM, and (2) have access to the storage component. The VIMS instance can then cause the VM to be restarted on the identified host system of the identified cluster.
Node down recovery method and apparatus, electronic device, and storage medium
A method and apparatus for recovery from node crash, an electronic device, and a storage medium are provided. The method is applicable to a proxy server in a master-slave system. The master-slave system further includes a target master node controlled by the proxy server and a target slave node corresponding to the target master node. If the target master node and the target slave node crash, the proxy server obtains a pre-stored persistent file from the target slave node. The target slave node stores a backup of cache data cached in the target master node, and the persistent file is generated based on cache data in the target slave node. A target master node that does not crash is deployed based on the persistent file; and a target slave node corresponding to the target master node that does not crash is deployed. In this solution, after the target master node and the target slave node both crash, the master-slave system can be recovered to a normal working state.
Two-tier failover service for data disaster recovery
Technologies are described herein for providing a two-tier failover service. A request to access content by an application associated with an application identifier may be identified. A first record corresponding to the application identifier may be retrieved from a database information table. The first record may include a reference identifier, a database name of a database, and a failover value. A second record corresponding to the reference identifier may be retrieved from a server information table. The second record may include an indication of a first server computer as a primary server computer and an indication of a second server computer as a secondary server computer. A connection specification to either the first server computer or the second server computer may be generated based on the first record and the second record.
Memory management method, memory storage device and memory control circuit unit
A memory management method, a memory storage device and a memory control circuit unit are provided. The memory management method includes: detecting a replacement physical unit number of a rewritable non-volatile memory module; adjusting an available capacity of the rewritable non-volatile memory module from a first available capacity to a second available capacity if the replacement physical unit number meets a default condition. Therefore, a lifespan of the memory storage device may be prolonged by adjusting the available capacity of the rewritable non-volatile memory module.
SYSTEM AND METHOD FOR BACKING UP DATA IN A LOAD-BALANCED CLUSTERED ENVIRONMENT
Disclosed herein are systems and method for backing up data in a load-balanced clustered environment. A clustered resource to be backed up is selected, wherein the clustered resource is stored on a common storage system and operated on by a cluster-aware application executing on at least a first node and a second node of a computing cluster. A load-balanced application may migrate the clustered resource from the first node with a high-load consumption to the second node with low-load consumption. A list of changes made by both nodes are received and merged. A backup agent then generates a consistent incremental backup using data retrieved from the common storage system according to the merged list of changes to the clustered resource.
DISASTER RECOVERY FOR DISTRIBUTED FILE SERVERS, INCLUDING METADATA FIXERS
Examples of systems described herein include a virtualized file servers. Examples of virtualized file servers described herein may support disaster recovery of the virtualized file server. Accordingly, examples of virtualized file servers may support metadata fixing procedures to update metadata in a recovery setting. Examples of virtualized file servers may support hypervisor-agnostic disaster recovery.
FAST DISASTER RECOVERY IN THE CLOUD FOR VIRTUAL MACHINES WITH SIGNIFICANT MEDIA CONTENT
One example method includes processing a file of a VM to create a decreased quality file that is a version of the file, storing the decreased quality file at a recovery site along with metadata indicating a file type and path name for the decreased quality file, in response to a disaster recovery request, creating a partial user VM at the recovery site, and the partial user VM includes the decreased quality file, and with the partial user VM, serving the decreased quality file to a user in response to a request from the user.
System and method for crash-consistent incremental backup of cluster storage
Disclosed herein are systems and method for backing up data in a clustered environment. A clustered resource to be backed up is selected, wherein the clustered resource is stored on a common storage system and operated on by a cluster-aware application executing on two or more nodes of a computing cluster. A first backup agent executing on a first node of the computing cluster may determine a list of changes to the clustered resource and may receive at least one list of changes to the clustered resource that are tracked by peer backup agents executing on other nodes of the computing cluster. The first backup agent may merge the lists of changes to the clustered resource, and may generate a consistent incremental backup using data retrieved from the common storage system according to the merged lists of changes to the clustered resource.