After completing the backup schedule configuration, its information is available by expanding the backup schedule status. When the backup location reaches the retention number, the oldest backup gets removed. Two options are available, keep all backups or specify the number of backups to keep. The retention option allows the selection of the number of backups to keep. Subfolders with the corresponding VCSA FQDN will also be created.Īlso included in the backup schedule configuration is a new retention option. A default backup folder called vCenter will be created during the backup if one is not supplied. The backup folder and subfolder do not need to be created before running the backup schedule wizard. Now the backup protocol is part of the backup location, using the following format: Protocol://Server Address: Port/Backup Folder/Subfolder. The backup location format has changed from vSphere 6.5. Here we can configure the backup schedule including location, frequency, and time. Right below is the new built-in backup scheduling option. One of these protocols must be set up and accessible to the VCSA before taking a backup. At the top, there is now an informational banner about the supported backup protocols. Front and center are several noticeable changes when going into the new backup tab. File-Based Backup 6.7įile-Based Backup has moved from under the summary tab and to its own backup tab. Now with the release of vSphere 6.7 comes new enhancements for file-based backup and restore. Then it imports the backup files from the selected backup bringing the VCSA back online. This is key since other solutions communicating to the VCSA will continue to do so as its UUID remains the same. The restore workflow first deploys a new appliance, retaining its original identity. Select the restore option and point to the backup protocol used.
#Acronis backup for vmware socket license iso#
Restoring the VCSA or PSC only requires mounting the VCSA ISO used during its deployment. These are all the files that make-up the VCSA, including the database. The backup files are then streamed to a backup target using one of the supported protocols: FTP(s), HTTP(s), and SCP. There is no need for any type of backup agents, nor is any quiescing or downtime of the VCSA or PSC required. It supports backing up both the vCenter Server Appliance or Platform Services Controller (PSC). This native backup solution is available within the VMware Appliance Management Interface on port 5480. One of those features was the built-in file-based backup and restore.
The vCenter Server Appliance (VCSA) had several exclusive features introduced in vSphere 6.5. File-Based Backup and Restore 6.7 Overview
0 kommentar(er)
