The backup might fail if the storage is not added into the storage infrastructure within the backup and replication console. When using Direct Storage Access, the storage must be properly configured and recognized within the backup console to ensure that the proxy can access and process the necessary data. If the storage is not added, the proxy server will not be able to see and back up the VMs on that storage, leading to a failure.
To ensure that the database VMs start before the application VMs in a disaster recovery situation, a failover plan should be configured. A failover plan in Veeam allows you to set the order in which VMs are powered on and to include delay intervals between the startups of different VMs, ensuring proper sequencing and interdependency handling.
The old restore points will be deleted after the new restore chain meets the retention policy. This is because backup software such as Veeam typically retains more restore points than configured until a new restore chain is created and meets the specified retention policy. Once this occurs, the old restore points that fall outside of the retention policy will be deleted to ensure that only the configured number of restore points are kept.
The best choice for restoring a missing VMware VM configuration file (VMX) is the VM file restore process. This process allows you to restore specific files related to the virtual machine, such as the VMX configuration file, without needing to perform a full VM restore. This method is more efficient and targeted for the specific issue of a missing VMX file.
The first step to switch back to the primary data center without losing data is to initiate a 'Failback to production'. This process involves transferring the operations back to the original VMs in the primary data center from the disaster recovery site. Once this is done and the systems are stable, further steps can be taken to finalize the process, such as committing the failback.