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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |