June 8, 2012 at 4:41 am
3041 :
BACKUP failed to complete the command BACKUP LOG [XXXXXXXX] TO DISK = N'\\XXXXXXXX\W$\LOG_BACKUP\XXXXXXXX_tlog_201206072000.TRN' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
This is odd as we have no N: drive on the system, yet this is a part of the routine log shipping process, any advice?
June 8, 2012 at 4:46 am
jblovesthegym (6/8/2012)
3041 :BACKUP failed to complete the command BACKUP LOG [XXXXXXXX] TO DISK = N'\\XXXXXXXX\W$\LOG_BACKUP\XXXXXXXX_tlog_201206072000.TRN' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
This is odd as we have no N: drive on the system, yet this is a part of the routine log shipping process, any advice?
N indicates is is NVARCHAR - you are backing up to W$
e.g.
declare @myvar nvarchar(100)
set @myvar=N'somevalue'
MVDBA
June 8, 2012 at 4:46 am
the N specifies that the following string is a NVARCHAR string
N'\\XXXXXXXX\W$\LOG_BACKUP\XXXXXXXX_tlog_201206072000.TRN'
Your actually backing up to \\XXXXXXXX\W$\LOG_BACKUP\, not the N drive
Edit
Mike beat me to it again
June 8, 2012 at 4:48 am
anthony.green (6/8/2012)
the N specifies that the following string is a NVARCHAR stringN'\\XXXXXXXX\W$\LOG_BACKUP\XXXXXXXX_tlog_201206072000.TRN'
Your actually backing up to \\XXXXXXXX\W$\LOG_BACKUP\, not the N drive
Edit
Mike beat me to it again
lol - my kung fu typing is faster than yours
MVDBA
June 8, 2012 at 9:17 am
Cheers guys, actually narrowed it down to a bunch of SPIDs (that's me being polite) doing a data migration project and using tons of exclusive latch locks, which I think are disrupting the backup jobs.
In other words - not my fault. 🙂
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply