mandrewartha
MIS
Hi,
I'm a newbie, so sorry if this is obvious.
I've been asked to inivestigate log shipping as part of a disaster recovery solution.
The set up went fine and log shipping was running sucessfully. Then to test it I set up a job to copy a tables append a tables contents onto the end of itself every minute for twenty minutes. ie double the table size
Anyhow this caused the standby to go out of sync but after about an hour it seemed to have recovered. That is until I tried to look at the standby which I found stuck in "loading" status and thus inaccessible.
The following is from the error logs of the stanby:
2002-09-06 15:07:01.29 spid54 Starting up database 'Northwind'.
2002-09-06 15:07:01.34 spid54 Bypassing recovery for database 'Northwind' because it is marked IN LOAD.
2002-09-06 15:07:05.12 backup Log restored: Database: Northwind, creation date(time): 2000/08/06(01:41:00), first LSN: 284:2349:1, last LSN: 284:2353:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\LS-dest\Northwind_tlog_200209061500.TRN'}).
2002-09-06 16:07:01.35 spid55 Starting up database 'Northwind'.
2002-09-06 16:07:01.40 spid55 Bypassing recovery for database 'Northwind' because it is marked IN LOAD.
2002-09-06 16:07:05.15 backup Log restored: Database: Northwind, creation date(time): 2000/08/06(01:41:00), first LSN: 284:2353:1, last LSN: 284:2357:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\LS-dest\Northwind_tlog_200209061600.TRN'}).
Any clues as to how I can safetly recover access to the warm-standby?
Cheers in advance.
I'm a newbie, so sorry if this is obvious.
I've been asked to inivestigate log shipping as part of a disaster recovery solution.
The set up went fine and log shipping was running sucessfully. Then to test it I set up a job to copy a tables append a tables contents onto the end of itself every minute for twenty minutes. ie double the table size
Anyhow this caused the standby to go out of sync but after about an hour it seemed to have recovered. That is until I tried to look at the standby which I found stuck in "loading" status and thus inaccessible.
The following is from the error logs of the stanby:
2002-09-06 15:07:01.29 spid54 Starting up database 'Northwind'.
2002-09-06 15:07:01.34 spid54 Bypassing recovery for database 'Northwind' because it is marked IN LOAD.
2002-09-06 15:07:05.12 backup Log restored: Database: Northwind, creation date(time): 2000/08/06(01:41:00), first LSN: 284:2349:1, last LSN: 284:2353:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\LS-dest\Northwind_tlog_200209061500.TRN'}).
2002-09-06 16:07:01.35 spid55 Starting up database 'Northwind'.
2002-09-06 16:07:01.40 spid55 Bypassing recovery for database 'Northwind' because it is marked IN LOAD.
2002-09-06 16:07:05.15 backup Log restored: Database: Northwind, creation date(time): 2000/08/06(01:41:00), first LSN: 284:2353:1, last LSN: 284:2357:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\LS-dest\Northwind_tlog_200209061600.TRN'}).
Any clues as to how I can safetly recover access to the warm-standby?
Cheers in advance.
