not as far as I know. I'll ask my DBA but my actual guess is the log-Backup
running while DB-Full Backup is running.
anacreo wrote:
> Out of curiosity is it possible some other backup mechanism is hitting this
> database as well?
>
> Like maybe a maintenance plan is running or a 3rd party tool in the middle
> of your backup (well even outside of your backup you can have problems)?
>
> Alec
>
> On Wed, Feb 24, 2010 at 5:54 AM, spaceball <
> networker-forum < at > backupcentral.com> wrote:
>
>
> > Hi,
> > Using NW 7.5.1 and mssql-client 5.2 I do have Problems during a directed
> > point-in-time (db)recovery.
> >
> > Recovering files of client 'db_client_1' from server 'nsrserverhost' to
> > client 'db_client_2'.
> > 43708:nsrsqlrc:Start time: Tue Feb 23 16:19:04 2010
> > 43621:nsrsqlrc:Computer Name: db_client_2 User Name: admin
> > NSR_CLIENT: db_client_1.bla.blub.local;
> > NSR_SERVER: nsrserverhost.bla.blub.local;
> > 37725:nsrsqlrc:Recovering database 'DB3' into 'DB3' ...
> > 4690:nsrsqlrc:RESTORE database [PB3] FROM
> > virtual_device='Legato#xxxx-yyy-....-....' WITH move 'DB3DATA1' to
> > 'P:\DB3DATA1\DB3DATA1.mdf', move 'DB3DATA2' to 'P:\DB3DATA2\DB3DATA2.ndf',
> > move 'DB3DATA3' to 'P:\DB3DATA3\DB3DATA3.ndf', move 'DB3DATA4' to
> > 'P:\DB3DATA4\DB3DATA4.ndf', move 'DB3LOG1' to 'J:\DB3LOG1\DB3LOG1.ldf',
> > replace, norecovery
> > 35866:nsrsqlrc:The restore of database 'DB3' completed successfully.
> > 4690:nsrsqlrc:RESTORE log [DB3] FROM
> > virtual_device='Legato#xxxx-yyy-....-....' WITH norecovery
> > 29085:nsrsqlrc:Microsoft SQL Server Provider error:
> > 38006:nsrsqlrc:The log in this backup set terminates at LSN
> > 2245000325536700001, which is too early to apply to the database. A more
> > recent log backup that includes LSN 2246000301201200001 can be restored..
> > 38006:nsrsqlrc:RESTORE LOG is terminating abnormally..
> > 37708:nsrsqlrc:nsrsqlado.cpp(2353): ExecuteFailed event arrived.
> > 35867:nsrsqlrc:Error processing SQL database 'DB3'.
> > Internal error.
> >
> > unknown XBSA error 1359 (0x54f)
> > 43709:nsrsqlrc:Stop time: Tue Feb 23 21:23:52 2010
> >
> > Restore completion time: Tue Feb 23 21:23:54 2010
> >
> >
> > As I've seen, there was a DB-Log backup (forced as incremental) running
> > while the DB-Full Backup was in progress (both on db_client_1).
> >
> > Is this causing the Problem -and in case it is- how could I avoid it
> > without pre/post scripting?
> >
> > help would be great...
> >
> >
> > Regards spaceball
> >
> > +----------------------------------------------------------------------
> > |This was sent by thorsten.linow < at > talkline.de via Backup Central.
> > |Forward SPAM to abuse < at > backupcentral.com.
> > +----------------------------------------------------------------------
> >
> >
> > "signoff networker" in the body of the email. Please write to
> > networker-request < at > listserv.temple.edu if you have any problems with
> > this
> > list. You can access the archives at
> > http://listserv.temple.edu/archives/networker.html or
> > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
> >
>
>
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
+----------------------------------------------------------------------
|This was sent by thorsten.linow AT talkline DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|