Topic outline:
MS SQL Restore
Previously Restored Data
Restore Data from Backup
Time Stamp
Type of Restore
Recovery State
- Login into Vembu Network Backup page and check the last successfully completed backup.

2. Now Click on Restore option and you can see available backup to restore.

3. Now there are two options given below:
a) Restore Data from backup server. And
b) I have previously restored data from my backup server to a local folder. I now want to use this data to restore the MS SQL Server.

4. Browse the previously restored data from the backup server to a local folder.

5. Select the data location of the folder or path to the folder . Click Ok.

6. Click on Yes.

7. Let’s select the first one to get an overview of this option “Restore data from backup server”.

8. Now select the below information:
a) Database Name.
b) Select Time Stamp.
c) Location of file.

9. We have selected the VIM_UMDB as the database name.

10. We have selected the the Time Stamp of the backup for restore.

11. We have the prompt with the Full Backup to be restored option. Select Full and click next.

12. After restoring data from backup server, continue to auto restore data into SQL Server Database.
- Choosing this option will let user restore data into SQL Server database, where user have the option to either overwrite an existing database or restore as separate database.


13. Restore data from backup server only (we will separately run Vembu NetworkBackup through the ‘locally restored files’ to restore the SQL Server database later).
- Choosing this option will restore data in a separate user defined location instead restoring data into SQL Server.

14. We have got these three options given below:
- Leave database in ready-to-use state by rolling back uncommitted transactions. Additional transaction logs cannot be restored (Restore with recovery).
- Leave database non-operational, and do not rollback uncommitted transactions. Additional transaction logs can be restored (Restore with Non-Recovery).
- Leave database in read-only mode. Undo uncommitted transactions, but save undo action in a standby file so that recovery effects can be reversed (Restore with Standby).

15. Lets choose the third option here and provide the Standby file location. Click Next.

16. Now you can review the configuration and click on Restore Now.

17. It will prompt you to confirm the restore operation to be executed. Click yes.

18. You can see the status for successful completion of the restore job.




19. You can also check the report by clicking on Reports > Restore Reports.

20. Click on Summary option and on VM hyperlink for report.

21. This is the restore report with all the details.


































2. Here you can see all these options but only one is highlighted which is Finalize Failover select and click on next.
3. Here select the VM and click next.
4. Failover is a temporary state that may be further finalized using any of the below processes:
Lets talk about these options:5. Permanent Failover: In case the source machine is not recoverable after a disaster or you want to continue business operations with the replica VM itself, then you can use permanent failover option. Permanent Failover helps IT admin to use the replica VM for production purpose permanently instead of source VM.All changes made during the failover process will be committed to the disk once the permanent failover is done. So, all the snapshots of the replica VMs will be consolidated. Further incremental will be blocked for the replica VM after the permanent failover process and the VM will be excluded from the VM replication job.
6. Undo Failover: Undo Failover is a process of reverting back the replica to its original state before failing over replica VM. The data added after failing over the replica VM will be terminated after the Undo Failover process.Undo Failover might be useful if the replica failover was initiated for testing purpose or if you get the original production server back after troubleshooting and if you don’t want the data that has been added after the failover process.
7. Failback: If you want to resume the source VM operation after disaster recovery and shift the production load back to the source VM, you can use failback process. (source: vembu.com)
8. Here it will start progress as per your selection.
9. In vCenter server under recent tasks you can see the progress for this VM.
10. It will show you the completed status under the restore progress option.







































































































