I need some help with a Redirected SQL Restore. I thought I had it down and when the restore job ran, what happened next is both unexplainable and unwanted.
I used a previous, successful B2D job as my restore point so I would not be touching the actual, production DB which was in use. I configured the restore job to send the restore to a different folder/directory location than the original DB resides. All permissions/credentials in place and working. Windows Server 2003 SP2 and Symantec Backup Exec 11d.
So, when the restore job started it looked as if it were running but on the other end, what happened was it began to restore the LIVE DB, thus freezing out any users who were working in that live DB at the time. Also, the restore job automatically(?) sent the restore to the original DB directory instead of the redirected path I had specified during the configuration/setup of the restore job.
I cannot - CANNOT - have something like that happen again but I DO need to run a successful SQL restore to prove to my boss and the higher-ups that we can restore the DB's if needed.
SO - I am VERY novice when it comes to server side stuff and backups, but nonetheless, I have to figure this out....
Specific Questions I have:
Why did the restore job not restore the DB to the redirected location that I had specified during job setup?
Why did the restore job pull the live DB data instead of from the B2D job that I had specified during job setup?
Why did the live DB go "offline - restore in progress" when there was nothing (that I know of anyway) that told the restore job to even touch the live DB?
This is a huge issue here and I'm at a loss for what to do next, let alone understanding what went wrong before.
Any help you can provide would be greatly appreciated.