- Notes, cautions, and warnings
- Preface
- Introduction
- Architecture
- Backup
- File system restore
- Disaster recovery
- Installation
- Preparing to install the Avamar client software
- System requirements
- Windows Server cluster requirements
- Windows Server 2019, 2016, or 2012 for SOFS or SMB cluster requirements
- Multi-homed cluster requirements
- VSS requirements
- Supported Windows features
- Hardware requirements
- Networking requirements
- Additional software requirements
- Unsupported configurations and features
- Preparing a Windows Server 2019, 2016, or 2012 for SOFS or SMB cluster
- Downloading the software
- Verifying the environment
- Installing the Avamar client software
- Installation road maps
- Stand-alone installation road map
- Installation road map for Windows Server clusters
- Installation road map for Windows Server active/active clusters
- Installation road map for Windows Server 2019, 2016, or 2012 clusters with SOFS or SMB
- Installation road map for Windows Server 2019, 2016, or 2012 active/active clusters with SOFS or SMB
- Installing the Avamar Client for Windows
- Registering the client
- Configuring the federated cluster client on Windows Server
- Configuring the proxy cluster client on Windows Server 2019, 2016, or 2012 for SOFS or SMB clusters
- Adding permissions for hidden file access in a cluster
- Adding permissions for non-administrator user access in a cluster
- Viewing the cluster client configuration
- Installation road maps
- Upgrading the Avamar client software
- Uninstalling the Avamar client software
- Preparing to install the Avamar client software
- Backup
- Performing on-demand backups
- Schedule backups using the AUI Policy wizard
- Monitor backups
- Cancel backups
- Enforcement of backups to Data Domain
- File System Restore
- Bare Metal Recovery
- Plug-in Options
- Command Line Interface
- Troubleshoot
- activation
- Active Directory
- administrator
- avagent
- Avamar Administrator
- Avamar Bare Metal Recovery Wizard
- Avamar client
- avtar
- backup
- backup policy
- bare metal recovery (BMR)
- browse
- client activation
- client agent
- client registration
- cluster
- Cluster Configuration Tool
- cluster shared volumes (CSV)
- clustered file server for general use
- critical disk
- Data Domain system
- database
- dataset
- Directory Services Restore Mode (DSRM)
- disaster recovery
- DNS
- domain
- federated cluster client
- file system
- group
- group policy
- LAN
- MCS
- metadata
- nonauthoritative restore
- noncritical disk
- plug-in
- plug-in options
- policy
- proxy cluster client
- proxy node
- redirected restore
- registration
- restore
- retention
- Scale-Out File Server (SOFS)
- schedule
- Server Core
- Server Message Block (SMB) 3.0 file shares
- shadow copy volume
- System State
- virtual hard disk (VHD) files
- virtual machine (VM)
- Volume Shadow Copy Service (VSS)
- VSS provider
- VSS requestor
- VSS writer
- Windows Deployment Services (WDS)
- WinPE ISO image
Dell EMC Avamar for Windows Servers 19.7 User Guide
Restoring a cluster node
Steps
- Ensure that at least one node in the cluster is still functioning.
- Shut down the damaged node.
- Perform an offline BMR of the node. BMR of Windows clients provides instructions.
- Reboot the node.
- If you applied any Windows service packs or hotfixes to the cluster node after the backup, then reapply the service packs or hotfixes to the restored cluster node to bring the node to the same service pack level as the other nodes in the cluster.
-
If required, rejoin the node to the cluster.
NOTE BMR restores the System State and critical disks on cluster nodes. After BMR, use the Windows File System plug-in to restore file system data, non-critical disks, and critical disks on shared storage. Also, use application plug-ins to restore application data.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\