Veritas Backup Exec restore process is very simple and one click job to restore any data from all types of storage devices like Disk, Tape, Dedup and other devices.
There are certain things we need to keep in mind while trying to restore files and folders in Veritas Backup Exec. The data restore process depends upon the the type of storage devices used during backup. For example if a Disk storage was used then you can simply restore from below options:
You go to Backup and Restore Tab > right click the server where you want to perform the restore> click Restore and follow instruction to complete the restore process.
Also in case Disk store you don’t need to run Inventory and Catalog because storage is not kept offline. You can restore from a disk storage in simple way.
But if the data needs to be restored from a Tape Library / Tape drive then you must run Inventory and Catalog because catalog needs to be updated for populate all the data available in tape so that you can make your restore selection or you can choose which file you need to restore. We’ll discuss in detail about the restore process in the next post.
Lets check how the restore process actually works in Veritas Backup Exec.
Once you right click on a server to restore the data then submit the restore job then it executes the restore. Then restore is initialized and dispatched to BE Engine and Bengine takes over.
Then BE Engine retrieves the restore job and tries to find out storage device associated with it. Once the storage device which was used in backup job is located to restore the requested data in the restore job it reads the file and transfer the data to remote agent to write the data to the destined server / remote agent server.
Post writing the data to the server which was in restore job selection list, the storage device / storage media is released to its original location. For example if tape cartridge was used then the tape is released and sent back to its slot in the tape library.
The restore job status was reported to backup database and logs are generated as well. It also reports if the status of restore job if it was successful or failed. Now the restore job ends. You can see the restored data to its location where the restore job was pointed to be saved / written.