Important: When restoring from file-based backup, you must use the same build of vCenter Server installation media that corresponds with the vCenter Server build of the backed up instance. If you have vCenter Server instances participating in ELM then you should avoid using image-based backup solutions and use only the native file-based backup feature of the vCenter Server. If you have a standalone vCenter Server instances, not participating in ELM, then using image-based backup solutions should have no issues. When is it ok to use image-based backups? This allows the restoring vCenter Server to correctly synchronize with the current state of the running SSO domain. When using image-based backup and restore methods, this reconciliation cannot happen.ĭuring a file-based restoration, you are prompted for the SSO administrator credentials. The restoring vCenter Server will be restored to the SSO domain without conflicts. This can lead to SSO domain data conflicts.įile-based restores handle this back-in-time situation by authenticating with the SSO domain and reconciling the SSO domain data during restoration. In the event that you restore a vCenter Server from backup, it’s akin to sending that instance back-in-time, while the other members of the SSO domain are still in the present. The state of the vCenter Server and its data, at that moment.
When you take a backup of a vCenter Server instance, it is a snapshot in time. When you have multiple vCenter Server instances in a single SSO domain, participating in Enhanced Linked Mode (ELM), you have data replicating between each instance. In this blog, we will answer the question why use file-based backups versus image-based backups when it comes to vCenter Server? The short answer is because of SSO domain data. VCenter Server can be backed up using two methods today image-based (VM backup) and file-based backup built into the vCenter Server itself.
0 kommentar(er)
