hi snap Center 4.6 is introducing a feature via rest API to backup snap Center server and recover it on the secondary site in case of a disaster recovery so that you can continue to protect and manage Enterprise workload and the same process can also be used in case if the snap Center server crashes at your primary location and you have to rebuild your snap Center server so the benefit of snap Center rest API is customer can script and customize solution based on the business requirement and migrate snap Center metadata and jobs to secondary site the process is first to backup all the metadata and configuration file on host using rest API in the event of a disaster thebackup copy should be restored on a secondary snap Center instance again using a rest API application database failover including snaper related operation should be managed outside of snap Center will then continue to trigger backup and manage data protection additionally there is a new setting in snap Center to enable Dr mode for SQL Server plugin which ensures to treat previously set snap mirror destination as a new primary storage copy after the failover and maintain the backuprepository let's see a quick demo on using this API so this is the Swagger page to access the Swagger page if you're using this for the first time it is the same snap Center URL followed by the Swagger so at the bottom uh under this category you will see a disaster recovery and it will have multiple options like viewing the available backup and then triggering a Dr backup so we'll select the first option to trigger a Dr backup there are very minimum option that you need to pass in while executing this API one is the token that is after you create an authentication via rest API a token ID will be generated you need to pass on the token ID and then provide the path where this backup file needs to be created and executed so this backup folder will contain the repository backup as well as your schedules as well as your configuration fileso you can copy this back a folder to your secondary side using x copy or maybe you using a different method and then performer restore the restoration process is also similar and simple to that as we did earlier for the backup just provide the token detail and select from which backup you want to perform the restore and the path of the backup file once you provide those detail you execute it so this process needs to be executed from your secondary snap Center server just ensure that you rename your secondary snap Center host name as same as that of your primary snap Center server name the other setting that you should be aware is that of enabling Dr board and this is specifically for SQL Server host so this is to make snap Center aware that the primary storage is down and to treat the snap mirror destination as kind of an primary storage for that database so once this feature is enabled you will see a cross mark visible in the topology View for the primary storage so next time when you take a backup snap Center will take a backup on the previously snap mirror destination which is now the primary storage for that databaseresource so you see how easy it is to create a Dr workflow for your snap Center using the rest API you can create Powershell or a python script on top of this rest API to create an endtoend Dr solution and orchestrate the complete workflow so thank you for watching this video you saw how you can continue to protect databases after migrating snap Center to alternate site organization can perform in place restore or clone of a snapshot from secondary storage even if primary storage is not available the process can be used in case of disaster recovery process or snap Center need to be moved to a different hose as a part of a platform refresh or o upgrade thanks again and have a great day