February 9, 2007 at 6:04 pm
February 9, 2007 at 11:33 pm
Follow this order while restoring the database.
1. Restore your full database backup
2. Restore your last differential backup
3. restore your transactional logs in a one by one in increasing time order.
You should be able to restore the database without any problems if u do this way.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
February 12, 2007 at 7:05 am
February 12, 2007 at 7:55 am
problem solved, permissions issue
March 25, 2008 at 4:54 am
Hi, can I ask please what the permissions issue was and what you did to fix it as I am having a similar problem to what you described above with the same type of setup (i.e. no log shipping, one maintenance plan etc)? Thanks
March 25, 2008 at 7:15 am
at this point with as long ago as that was, I don't remember what I did.
I have however discovered if you have a maintence Job set up, do not under any circumstance manually process a backup. (right clicking the database in Management Studio or Enterprise Manager) Tasks -- Backup
If you do a manual backup, as opposed to launching the backup from the Job in Server Agent, you will mess up the LSN numbers stored in the msdb database (I think it's msdb it stores it) and then any backups that process between when you did that and your next full backup, will not work.
The system records the beginning and ending record number and if that changes then it thinks you're missing one, and wont' let you process them.
I hope this makes sense, and I hope everything works for you (PS I am not doing Log Shipping, so there may be some things you can do to help you there.)
March 27, 2008 at 3:29 pm
Thanks for the reply. I'll give it another try. Fortunately its not very urgent, just doing some testing on how we would get back up and running should anything go belly up on the prodction db. Thanks again
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply