At the prompt, type wbadmin get versions. This will show you all the backups on this machine. Figure 4: The backup versions available to me at this time. Note the version identifier, as this is the key string we need to identify this version in future commands. Figure 5: The items included in that backup. Note the Cluster application - this is what we're looking for! We always advise that an administrator take all applications in the cluster offline prior to recovering the cluster configuration.
This will take care of the applications. I specify that I want to perform an Application level recovery -itemType:App and restore the Cluster application -items:Cluster.
Again, here is my output:. After restoring the cluster database, the Cluster service will be stopped and then started, which may take a few minutes. Please be patient. After that, cluster service needs to be started on the nodes identified in the restored cluster database.
However, it is still possible to use basic virtual machine backup jobs to process virtual clusters without Veeam Agents. At the Active Directory step specify the domain name and account if required and select the Active Directory cluster name object.
Specify the common master account and set custom credentials for particular hosts if needed. Check the box to Install backup agent at the Options step of the wizard to install backup agents automatically during the rescan installation can be performed manually if required.
Rescan the protection group to discover the newly added cluster account, all its nodes and install backup agent to every node. Once the rescan is completed you should see the cluster and all child nodes under the protection group NOTE: To avoid installation issues, make sure that all required network and DNS requirements are fulfilled.
There may be various infrastructure changes required to grant that access: network configuration, firewall and security software settings. Configure the backup job Once you install the backup agent on every node, you can create a cluster job. Failover Clusters must be processed by backup server jobs with the Failover cluster type. At the Computers step of the wizard hit Add and select cluster account or the parent protection group for this cluster.
Only volume-level backup and entire system backup modes are available for the failover cluster job. Define the appropriate application-aware processing options at the Guest Processing step of the wizard. The first step in backing up or recovering a clustered system is to detect clustering services and determine their state using the GetNodeClusterState function.
If clustering services are installed and running, backup applications requesters should choose to treat the system as a cluster. If clustering services are installed but not running, backup applications should treat the system as a stand-alone server.
If clustering services are detected, a backup application can display the cluster by name for backup. The cluster name can be determined by passing either the machine name or NULL to the OpenCluster function and retrieving a handle to the cluster to which the current node running the backup application belongs. It is best to pass "machine name" as a parameter to the OpenCluster function if possible because this will ensure that the client is connected to the cluster even if the cluster service stops on the node to which the client is initially connected.
After the application has a handle to the cluster, the GetClusterInformation function will provide information about the cluster, including its name. Restoring the node. This is completely taken care of in a system state restore on that particular node.
0コメント