08-03-2009 07:58 AM
08-03-2009 08:34 AM
You can set up a duplicate backup job in backup exec for duplicating the backup set from the onsite b2d to offsite b2d . You can click on file | new | Duplicate backup set job
select the option to duplicate backup for an existing job .
So as per your question it work ... well I am not sure about this statement "Then as a post backup command we would run a RoboCopy of the on-site disk to the off-site disk that is connected to the server at that time"....
Instead of running any post backup commad it would be easier to run a duplicate backup Job
08-03-2009 09:12 AM
08-03-2009 10:05 AM
08-03-2009 10:22 AM
08-03-2009 10:38 AM
08-21-2009 09:19 AM
We do a very similar thing here. I run full backups every Friday night to Friday backup to disk folders. Then I copy these Friday folders with a batch file along with other files to a 400GB removable disk and send them off site. I have successfully restored files from the off site removables drives but it is a little tricky. It seems that backup exec thinks the off site file is already cataloged. There must be something in this old Friday backup file that tricks backup exec into thinking it is the current Friday backup file. This is probably because I just copied the file instead of running a duplicate backup sets job. Here is how I work around the issue.
Before I attempt the restore, I "delete" the back up to disk file from my catalog. To delete the file from the catalog I first associate the file with the retired media set and then using backup exec "delete" it. This removes it from the catalog but does not remove the actual file from the file system.
Then I copy the off site file to a special backup to disk folder I have named Restore. I Inventory the backup to disk folder and catalog the "imported media ". Now every thing is synced up and I run my restore job.
After restoring the files I needed, I have to put things right. I remove the off site file that I used from the catalog much the same as I did for the current Friday back up to disk file . Then I Inventory my Friday folder to get the current Friday back to disk file back in the catalog. Finally I associate the current Friday backup to disk file with the scratch media set so that it will can be used on Friday again. I don't bother to catalog the media unless I need it for a restore as it is going to be overwritten on Friday any how.
The longest part of this process is cataloging the imported media. We run separate backup jobs for each server to separate backup to disk folders and that helps reduce the time it takes to catalog the media. Our largest backup to disk file is 137Gigabytes. It takes about 30 minutes to catalog the file. Considering that it usually takes a day to get the off site disk back on site, it is not so bad.
It is not the most Ideal plan. But the primary focus of this strategy is a disaster recovery situation in which our servers were lost so I would be installing Backup Exec and then copying the off site files to the backup to disk folders.
Hope it helps.
08-21-2009 10:53 AM