October 15, 2002 at 2:17 pm
I just restored last nigthts backup and left the db able to restore transaction log. After the successfull restore I tried to restore transaction logs but get "database has been marked inaccesable error 22274". The db icon has (loading) next to it in Ent. Manager. Can't get any database info. How can I get make db accessable to restore trans. logs?
Thanks
October 15, 2002 at 2:53 pm
I'd recommend calling MS, but they might tell you this.
detach the db. Create a new db and retry your restores.
Can't hurt.
Steve Jones
October 15, 2002 at 3:13 pm
I waited a bit longer and was able to get to the restore database screen. I tried to apply the first tran. log after the backup but got message "db not rolled forward enough-restore earlier tran.log". I know this is the first so I guess this is really hosed. I think I need to go the detach route. Any more detailed advice before I launch into it?
Thanks again
October 15, 2002 at 3:32 pm
The "restore earlier log" means you are restoring out of order. Logs MUST be restored in the order they were taken.
If you are missing one, you can only restore to the last log that works. At that point, mark the db as live and go. When restoring from EM, check "unable to restore additional logs and database functional" when you get to this last log.
If you mess up, go back and start over with the full and then start applying logs.
Steve Jones
October 15, 2002 at 5:03 pm
Restart the Resote Process from the full backup first, and then restore the logs backups in order.
October 16, 2002 at 9:50 am
Now that the dust has settled and calmness prevails...
I now realize that all of my trouble stemmed from impatience (maybe justified). Once I had succsefully restored the complete backup, I right clicked the database to open the restore window again to begin applying transaction logs. I got an hour glass and no action (no backup window) for about 3 minutes. I tasked managered and saw "not responding". Uh oh. I stopped the process and right cliked the db again to look at its properties and got "DB inaccesible". Oh ****!
Well after my coworker pointed out the processor was chugging away while I waited for the backup screen I decided to try again. After a full 5 minutes the screen popped up and I was able to apply my first log. I had this 5 to 6 minute wait for the window between each log application (4 logs applied). Has anyone else experienced such a delay?
The part about "db not rolled forward enough" was an out and out bone head move, I picked the wrong transaction log backup.
In the future I will stack the logs in the device window and apply all at once.
Thanks for your help, it is greatly appreciated!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply