Hi All,
We recently upgraded a box running Windows Server 2003 SP1 with SQL Server
2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
For some time we have had the following backup regime for some SQL Server
full recovery model databases that are present on this server:
1) SQL Server Full backup on a Sunday night at around midnight
2) SQL Server Transaction log backups every three hours from 03:00
until 18:00
3) SQL Server Differential backups at 21:00 every day except Sunday
night.
4) NTBACKUP at 22:00 every night to do a differential backup of the
server using option /SNAP:on (Use Volume Shadow Copy) but with the directory
containing SQL Server database files excluded.
5) Note the output TRN files and BAK files from points 1 to 4 above are
mirrored off to another server by a 3rd party application, not by using
NTBACKUP.
All has worked fine for many months until our upgrade of the server to SP2
of SQL Server and SP2 of Windows Server 2003.
Immediately after that upgrade we would get the Full backup at point 1
completing as planned, the transaction log backups at point 2 complete on
the Monday, then the differential SQL backup on Monday night works fine as
well followed by the NT Backup at point 4. The cycle works fine on the
Tuesday up to the repeat of the SQL Server differential backup at point 3
which fails for every database with an error message not unlike this
example:
[QUOTE]
Executing the query "BACKUP DATABASE [dbTPL] TO DISK = N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10" failed
with the following error: "Cannot perform a differential backup for database
"dbTPL", because a current database backup does not exist. Perform a full
database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL
option. BACKUP DATABASE is terminating abnormally.". Possible failure
reasons: Problems with the query, "ResultSet" property not set correctly,
parameters not set correctly, or connection not established correctly.
[END QUOTE]
As if NTBackup has broken the link to the original full backup.
There used to be a problem with the Volume Shadow Copy Service whereby
NTBACKUP would not manage a backup of SQL Server Full recovery model
databases. As in this article here: http://support.microsoft.com/kb/903643
I noticed in the event log since our upgrade to SP2 of Windows Server 2003
and SQL Server 2005 we get errors around the time NTBACKUP runs that are
like this one:
[QUOTE]
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 29/03/2007
Time: 07:03:47
User: N/A
Computer: SERVERA
Description:
SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
ErrorCode=(288)Attempt to release mutex not owned by caller.. Process=1968.
Thread=3564. Client. Instance=. VD=.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
[END QUOTE]
The SQL Server maintenance plans at points 1 through to 3 above are not hand
crafted scripts, just output from the Maintenance plan wizard. Furthermore
they have been deleted and recreated since updating to SP2 in case that was
the cause but the problem remains.
The only way around this problem has been to amend the NTBACKUP command at
point 4 above and use /SNAP:off so that it doesn't use the Volume Shadow
Copy service. I can only draw the conclusion that the Shadow Copy Service or
NTBackup has something to do with this? Has anybody else encountered a
similar problem?
I have been researching this for days but due to the relative brief period
since the release of Service Pack 2 for Windows Server 2003 there isn't
really too much about on the web regarding this. In fact I hadn't even
though of it being the NTBACKUP if it hadn't been for the thread I found
here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
Any tips / ideas much appreciated.
Kind RegardsCan you configure NTBACKUP to not grab the SQL Server database files? Just thinking out loud...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
> Hi All,
>
> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to Windows
> Server 2003 SP2 and SQL Server SP2.
>
> For some time we have had the following backup regime for some SQL Server full recovery model
> databases that are present on this server:
>
> 1) SQL Server Full backup on a Sunday night at around midnight
> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database files
> excluded.
> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
> another server by a 3rd party application, not by using NTBACKUP.
>
> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and SP2
> of Windows Server 2003.
>
> Immediately after that upgrade we would get the Full backup at point 1 completing as planned, the
> transaction log backups at point 2 complete on the Monday, then the differential SQL backup on
> Monday night works fine as well followed by the NT Backup at point 4. The cycle works fine on the
> Tuesday up to the repeat of the SQL Server differential backup at point 3 which fails for every
> database with an error message not unlike this example:
>
> [QUOTE]
> Executing the query "BACKUP DATABASE [dbTPL] TO DISK => N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH DIFFERENTIAL
> , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
> failed with the following error: "Cannot perform a differential backup for database "dbTPL",
> because a current database backup does not exist. Perform a full database backup by reissuing
> BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP DATABASE is terminating
> abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set
> correctly, parameters not set correctly, or connection not established correctly.
> [END QUOTE]
>
> As if NTBackup has broken the link to the original full backup.
>
> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not manage a
> backup of SQL Server Full recovery model databases. As in this article here:
> http://support.microsoft.com/kb/903643
>
> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server 2005 we
> get errors around the time NTBACKUP runs that are like this one:
>
> [QUOTE]
> Event Type: Error
> Event Source: SQLVDI
> Event Category: None
> Event ID: 1
> Date: 29/03/2007
> Time: 07:03:47
> User: N/A
> Computer: SERVERA
> Description:
> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release mutex
> not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>
> For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
> [END QUOTE]
>
> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted scripts, just
> output from the Maintenance plan wizard. Furthermore they have been deleted and recreated since
> updating to SP2 in case that was the cause but the problem remains.
>
> The only way around this problem has been to amend the NTBACKUP command at point 4 above and use
> /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the conclusion
> that the Shadow Copy Service or NTBackup has something to do with this? Has anybody else
> encountered a similar problem?
>
> I have been researching this for days but due to the relative brief period since the release of
> Service Pack 2 for Windows Server 2003 there isn't really too much about on the web regarding
> this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for the thread I
> found here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>
> Any tips / ideas much appreciated.
>
> Kind Regards
>
>
>|||Hi Tibor,
Some of the databases are quite large and backing them up fully using
NTBACKUP with snap:on option is not really an option. The idea is to leave
the SQL databases' backups outside of the control of NTBACKUP. This used to
work though until application of the Service Packs and now NTBACKUP seems to
be breaking that Differential chain. Although I hasten to add, that is the
only possible cause I have been able to identify thus far however I accept
there could be other causes. Luckily this server doesn't have a basket load
of other applications / services that could have any indirect effect on this
problem.
Kind Regards
Nick
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
> Can you configure NTBACKUP to not grab the SQL Server database files? Just
> thinking out loud...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL
>> Server 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL Server
>> full recovery model databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from 03:00
>> until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except Sunday
>> night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of the
>> server using option /SNAP:on (Use Volume Shadow Copy) but with the
>> directory containing SQL Server database files excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4 above
>> are mirrored off to another server by a 3rd party application, not by
>> using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server to
>> SP2 of SQL Server and SP2 of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point 1
>> completing as planned, the transaction log backups at point 2 complete on
>> the Monday, then the differential SQL backup on Monday night works fine
>> as well followed by the NT Backup at point 4. The cycle works fine on the
>> Tuesday up to the repeat of the SQL Server differential backup at point 3
>> which fails for every database with an error message not unlike this
>> example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
>> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME =>> N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
>> failed with the following error: "Cannot perform a differential backup
>> for database "dbTPL", because a current database backup does not exist.
>> Perform a full database backup by reissuing BACKUP DATABASE, omitting the
>> WITH DIFFERENTIAL option. BACKUP DATABASE is terminating abnormally.".
>> Possible failure reasons: Problems with the query, "ResultSet" property
>> not set correctly, parameters not set correctly, or connection not
>> established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service whereby
>> NTBACKUP would not manage a backup of SQL Server Full recovery model
>> databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server
>> 2003 and SQL Server 2005 we get errors around the time NTBACKUP runs that
>> are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
>> ErrorCode=(288)Attempt to release mutex not owned by caller..
>> Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are not
>> hand crafted scripts, just output from the Maintenance plan wizard.
>> Furthermore they have been deleted and recreated since updating to SP2 in
>> case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP command
>> at point 4 above and use /SNAP:off so that it doesn't use the Volume
>> Shadow Copy service. I can only draw the conclusion that the Shadow Copy
>> Service or NTBackup has something to do with this? Has anybody else
>> encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief
>> period since the release of Service Pack 2 for Windows Server 2003 there
>> isn't really too much about on the web regarding this. In fact I hadn't
>> even though of it being the NTBACKUP if it hadn't been for the thread I
>> found here:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>|||I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
> Hi Tibor,
> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on option
> is not really an option. The idea is to leave the SQL databases' backups outside of the control of
> NTBACKUP. This used to work though until application of the Service Packs and now NTBACKUP seems
> to be breaking that Differential chain. Although I hasten to add, that is the only possible cause
> I have been able to identify thus far however I accept there could be other causes. Luckily this
> server doesn't have a basket load of other applications / services that could have any indirect
> effect on this problem.
> Kind Regards
> Nick
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to Windows
>> Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL Server full recovery model
>> databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database files
>> excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>> another server by a 3rd party application, not by using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and SP2
>> of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point 1 completing as planned,
>> the transaction log backups at point 2 complete on the Monday, then the differential SQL backup
>> on Monday night works fine as well followed by the NT Backup at point 4. The cycle works fine on
>> the Tuesday up to the repeat of the SQL Server differential backup at point 3 which fails for
>> every database with an error message not unlike this example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD,
>> STATS = 10" failed with the following error: "Cannot perform a differential backup for database
>> "dbTPL", because a current database backup does not exist. Perform a full database backup by
>> reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP DATABASE is terminating
>> abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set
>> correctly, parameters not set correctly, or connection not established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not manage
>> a backup of SQL Server Full recovery model databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server 2005
>> we get errors around the time NTBACKUP runs that are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted scripts,
>> just output from the Maintenance plan wizard. Furthermore they have been deleted and recreated
>> since updating to SP2 in case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and use
>> /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the conclusion
>> that the Shadow Copy Service or NTBackup has something to do with this? Has anybody else
>> encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief period since the release of
>> Service Pack 2 for Windows Server 2003 there isn't really too much about on the web regarding
>> this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for the thread I
>> found here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>>
>|||Hi Tibor,
Unfortunately now you cannot. The only way to prevent this is to turn off
the command line SNAP option of NTBACKUP with /snap:off however this defeats
the object since there are other files (Non-SQL Server) on the drive that I
do want to have backed up even though they maybe in use.
Regards
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>I see. SQL Server get confused even if NTBACKUP excludes the database
>files. Can you configure NTBACKUP to not interface with SQL Server? It
>seems from the eventlog entry you posted that SQL Server got some VDI call
>from NTBACKUP. This is probably the one that broke the backup chain.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using
>> NTBACKUP with snap:on option is not really an option. The idea is to
>> leave the SQL databases' backups outside of the control of NTBACKUP. This
>> used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten
>> to add, that is the only possible cause I have been able to identify thus
>> far however I accept there could be other causes. Luckily this server
>> doesn't have a basket load of other applications / services that could
>> have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files?
>> Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL
>> Server 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL
>> Server full recovery model databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from 03:00
>> until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except
>> Sunday night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of
>> the server using option /SNAP:on (Use Volume Shadow Copy) but with the
>> directory containing SQL Server database files excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4
>> above are mirrored off to another server by a 3rd party application,
>> not by using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server to
>> SP2 of SQL Server and SP2 of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point 1
>> completing as planned, the transaction log backups at point 2 complete
>> on the Monday, then the differential SQL backup on Monday night works
>> fine as well followed by the NT Backup at point 4. The cycle works fine
>> on the Tuesday up to the repeat of the SQL Server differential backup
>> at point 3 which fails for every database with an error message not
>> unlike this example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
>> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME =>> N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
>> failed with the following error: "Cannot perform a differential backup
>> for database "dbTPL", because a current database backup does not exist.
>> Perform a full database backup by reissuing BACKUP DATABASE, omitting
>> the WITH DIFFERENTIAL option. BACKUP DATABASE is terminating
>> abnormally.". Possible failure reasons: Problems with the query,
>> "ResultSet" property not set correctly, parameters not set correctly,
>> or connection not established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service whereby
>> NTBACKUP would not manage a backup of SQL Server Full recovery model
>> databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server
>> 2003 and SQL Server 2005 we get errors around the time NTBACKUP runs
>> that are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
>> ErrorCode=(288)Attempt to release mutex not owned by caller..
>> Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are not
>> hand crafted scripts, just output from the Maintenance plan wizard.
>> Furthermore they have been deleted and recreated since updating to SP2
>> in case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP command
>> at point 4 above and use /SNAP:off so that it doesn't use the Volume
>> Shadow Copy service. I can only draw the conclusion that the Shadow
>> Copy Service or NTBackup has something to do with this? Has anybody
>> else encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief
>> period since the release of Service Pack 2 for Windows Server 2003
>> there isn't really too much about on the web regarding this. In fact I
>> hadn't even though of it being the NTBACKUP if it hadn't been for the
>> thread I found here:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>>
>>
>|||> Unfortunately now you cannot.
That sounds horrible to me, to be honest. I'd talk to the guys who wrote this software...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
> Hi Tibor,
> Unfortunately now you cannot. The only way to prevent this is to turn off the command line SNAP
> option of NTBACKUP with /snap:off however this defeats the object since there are other files
> (Non-SQL Server) on the drive that I do want to have backed up even though they maybe in use.
> Regards
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
>>NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
>>Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on
>> option is not really an option. The idea is to leave the SQL databases' backups outside of the
>> control of NTBACKUP. This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten to add, that is the
>> only possible cause I have been able to identify thus far however I accept there could be other
>> causes. Luckily this server doesn't have a basket load of other applications / services that
>> could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to Windows
>> Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL Server full recovery model
>> databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database files
>> excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>> another server by a 3rd party application, not by using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and
>> SP2 of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point 1 completing as planned,
>> the transaction log backups at point 2 complete on the Monday, then the differential SQL
>> backup on Monday night works fine as well followed by the NT Backup at point 4. The cycle
>> works fine on the Tuesday up to the repeat of the SQL Server differential backup at point 3
>> which fails for every database with an error message not unlike this example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND,
>> NOUNLOAD, STATS = 10" failed with the following error: "Cannot perform a differential backup
>> for database "dbTPL", because a current database backup does not exist. Perform a full
>> database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP
>> DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query,
>> "ResultSet" property not set correctly, parameters not set correctly, or connection not
>> established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not
>> manage a backup of SQL Server Full recovery model databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server 2005
>> we get errors around the time NTBACKUP runs that are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted scripts,
>> just output from the Maintenance plan wizard. Furthermore they have been deleted and recreated
>> since updating to SP2 in case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and
>> use /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the
>> conclusion that the Shadow Copy Service or NTBackup has something to do with this? Has anybody
>> else encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief period since the release
>> of Service Pack 2 for Windows Server 2003 there isn't really too much about on the web
>> regarding this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for
>> the thread I found here:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>>
>>
>>
>|||NTBACKUP is Microsoft. It's the default backup software in the operating
system. I don't think talking to them is going to get me anywhere.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
> That sounds horrible to me, to be honest. I'd talk to the guys who wrote
> this software...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn off
>> the command line SNAP option of NTBACKUP with /snap:off however this
>> defeats the object since there are other files (Non-SQL Server) on the
>> drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database
>>files. Can you configure NTBACKUP to not interface with SQL Server? It
>>seems from the eventlog entry you posted that SQL Server got some VDI
>>call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using
>> NTBACKUP with snap:on option is not really an option. The idea is to
>> leave the SQL databases' backups outside of the control of NTBACKUP.
>> This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I
>> hasten to add, that is the only possible cause I have been able to
>> identify thus far however I accept there could be other causes. Luckily
>> this server doesn't have a basket load of other applications / services
>> that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files?
>> Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL
>> Server 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL
>> Server full recovery model databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from
>> 03:00 until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except
>> Sunday night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of
>> the server using option /SNAP:on (Use Volume Shadow Copy) but with
>> the directory containing SQL Server database files excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4
>> above are mirrored off to another server by a 3rd party application,
>> not by using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server
>> to SP2 of SQL Server and SP2 of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point
>> 1 completing as planned, the transaction log backups at point 2
>> complete on the Monday, then the differential SQL backup on Monday
>> night works fine as well followed by the NT Backup at point 4. The
>> cycle works fine on the Tuesday up to the repeat of the SQL Server
>> differential backup at point 3 which fails for every database with an
>> error message not unlike this example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
>> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME =>> N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
>> failed with the following error: "Cannot perform a differential
>> backup for database "dbTPL", because a current database backup does
>> not exist. Perform a full database backup by reissuing BACKUP
>> DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP DATABASE is
>> terminating abnormally.". Possible failure reasons: Problems with the
>> query, "ResultSet" property not set correctly, parameters not set
>> correctly, or connection not established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service
>> whereby NTBACKUP would not manage a backup of SQL Server Full
>> recovery model databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server
>> 2003 and SQL Server 2005 we get errors around the time NTBACKUP runs
>> that are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
>> ErrorCode=(288)Attempt to release mutex not owned by caller..
>> Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are
>> not hand crafted scripts, just output from the Maintenance plan
>> wizard. Furthermore they have been deleted and recreated since
>> updating to SP2 in case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP
>> command at point 4 above and use /SNAP:off so that it doesn't use the
>> Volume Shadow Copy service. I can only draw the conclusion that the
>> Shadow Copy Service or NTBackup has something to do with this? Has
>> anybody else encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief
>> period since the release of Service Pack 2 for Windows Server 2003
>> there isn't really too much about on the web regarding this. In fact
>> I hadn't even though of it being the NTBACKUP if it hadn't been for
>> the thread I found here:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>>
>>
>>
>>
>|||> NTBACKUP is Microsoft.
I know. I was just suggestion that this should be configurable in this app. Perhaps ask in a Windows
forum? To the best of my knowledge, there's no way to say to SQL Server to ignore this backup VDI
message.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:OOVKXyhcHHA.984@.TK2MSFTNGP04.phx.gbl...
> NTBACKUP is Microsoft. It's the default backup software in the operating system. I don't think
> talking to them is going to get me anywhere.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
>> That sounds horrible to me, to be honest. I'd talk to the guys who wrote this software...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn off the command line SNAP
>> option of NTBACKUP with /snap:off however this defeats the object since there are other files
>> (Non-SQL Server) on the drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
>>NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
>>Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on
>> option is not really an option. The idea is to leave the SQL databases' backups outside of the
>> control of NTBACKUP. This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten to add, that is the
>> only possible cause I have been able to identify thus far however I accept there could be
>> other causes. Luckily this server doesn't have a basket load of other applications / services
>> that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out
>> loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>>> Hi All,
>>>
>>>
>>>
>>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to
>>> Windows Server 2003 SP2 and SQL Server SP2.
>>>
>>>
>>>
>>> For some time we have had the following backup regime for some SQL Server full recovery
>>> model databases that are present on this server:
>>>
>>>
>>>
>>> 1) SQL Server Full backup on a Sunday night at around midnight
>>>
>>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>>>
>>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>>>
>>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database
>>> files excluded.
>>>
>>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>>> another server by a 3rd party application, not by using NTBACKUP.
>>>
>>>
>>>
>>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and
>>> SP2 of Windows Server 2003.
>>>
>>>
>>>
>>> Immediately after that upgrade we would get the Full backup at point 1 completing as
>>> planned, the transaction log backups at point 2 complete on the Monday, then the
>>> differential SQL backup on Monday night works fine as well followed by the NT Backup at
>>> point 4. The cycle works fine on the Tuesday up to the repeat of the SQL Server differential
>>> backup at point 3 which fails for every database with an error message not unlike this
>>> example:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND,
>>> NOUNLOAD, STATS = 10" failed with the following error: "Cannot perform a differential backup
>>> for database "dbTPL", because a current database backup does not exist. Perform a full
>>> database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP
>>> DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query,
>>> "ResultSet" property not set correctly, parameters not set correctly, or connection not
>>> established correctly.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> As if NTBackup has broken the link to the original full backup.
>>>
>>>
>>>
>>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not
>>> manage a backup of SQL Server Full recovery model databases. As in this article here:
>>> http://support.microsoft.com/kb/903643
>>>
>>>
>>>
>>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server
>>> 2005 we get errors around the time NTBACKUP runs that are like this one:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Event Type: Error
>>>
>>> Event Source: SQLVDI
>>>
>>> Event Category: None
>>>
>>> Event ID: 1
>>>
>>> Date: 29/03/2007
>>>
>>> Time: 07:03:47
>>>
>>> User: N/A
>>>
>>> Computer: SERVERA
>>>
>>> Description:
>>>
>>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted
>>> scripts, just output from the Maintenance plan wizard. Furthermore they have been deleted
>>> and recreated since updating to SP2 in case that was the cause but the problem remains.
>>>
>>>
>>>
>>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and
>>> use /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the
>>> conclusion that the Shadow Copy Service or NTBackup has something to do with this? Has
>>> anybody else encountered a similar problem?
>>>
>>>
>>>
>>> I have been researching this for days but due to the relative brief period since the release
>>> of Service Pack 2 for Windows Server 2003 there isn't really too much about on the web
>>> regarding this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for
>>> the thread I found here:
>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>>
>>>
>>>
>>> Any tips / ideas much appreciated.
>>>
>>>
>>>
>>> Kind Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Come to think of it, perhaps stopping the SQL Server VSS service... But I don't know what side
effects that would have. I'd check with MS first.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:OOVKXyhcHHA.984@.TK2MSFTNGP04.phx.gbl...
> NTBACKUP is Microsoft. It's the default backup software in the operating system. I don't think
> talking to them is going to get me anywhere.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
>> That sounds horrible to me, to be honest. I'd talk to the guys who wrote this software...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn off the command line SNAP
>> option of NTBACKUP with /snap:off however this defeats the object since there are other files
>> (Non-SQL Server) on the drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
>>NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
>>Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on
>> option is not really an option. The idea is to leave the SQL databases' backups outside of the
>> control of NTBACKUP. This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten to add, that is the
>> only possible cause I have been able to identify thus far however I accept there could be
>> other causes. Luckily this server doesn't have a basket load of other applications / services
>> that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out
>> loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>>> Hi All,
>>>
>>>
>>>
>>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to
>>> Windows Server 2003 SP2 and SQL Server SP2.
>>>
>>>
>>>
>>> For some time we have had the following backup regime for some SQL Server full recovery
>>> model databases that are present on this server:
>>>
>>>
>>>
>>> 1) SQL Server Full backup on a Sunday night at around midnight
>>>
>>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>>>
>>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>>>
>>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database
>>> files excluded.
>>>
>>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>>> another server by a 3rd party application, not by using NTBACKUP.
>>>
>>>
>>>
>>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and
>>> SP2 of Windows Server 2003.
>>>
>>>
>>>
>>> Immediately after that upgrade we would get the Full backup at point 1 completing as
>>> planned, the transaction log backups at point 2 complete on the Monday, then the
>>> differential SQL backup on Monday night works fine as well followed by the NT Backup at
>>> point 4. The cycle works fine on the Tuesday up to the repeat of the SQL Server differential
>>> backup at point 3 which fails for every database with an error message not unlike this
>>> example:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND,
>>> NOUNLOAD, STATS = 10" failed with the following error: "Cannot perform a differential backup
>>> for database "dbTPL", because a current database backup does not exist. Perform a full
>>> database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP
>>> DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query,
>>> "ResultSet" property not set correctly, parameters not set correctly, or connection not
>>> established correctly.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> As if NTBackup has broken the link to the original full backup.
>>>
>>>
>>>
>>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not
>>> manage a backup of SQL Server Full recovery model databases. As in this article here:
>>> http://support.microsoft.com/kb/903643
>>>
>>>
>>>
>>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server
>>> 2005 we get errors around the time NTBACKUP runs that are like this one:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Event Type: Error
>>>
>>> Event Source: SQLVDI
>>>
>>> Event Category: None
>>>
>>> Event ID: 1
>>>
>>> Date: 29/03/2007
>>>
>>> Time: 07:03:47
>>>
>>> User: N/A
>>>
>>> Computer: SERVERA
>>>
>>> Description:
>>>
>>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted
>>> scripts, just output from the Maintenance plan wizard. Furthermore they have been deleted
>>> and recreated since updating to SP2 in case that was the cause but the problem remains.
>>>
>>>
>>>
>>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and
>>> use /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the
>>> conclusion that the Shadow Copy Service or NTBackup has something to do with this? Has
>>> anybody else encountered a similar problem?
>>>
>>>
>>>
>>> I have been researching this for days but due to the relative brief period since the release
>>> of Service Pack 2 for Windows Server 2003 there isn't really too much about on the web
>>> regarding this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for
>>> the thread I found here:
>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>>
>>>
>>>
>>> Any tips / ideas much appreciated.
>>>
>>>
>>>
>>> Kind Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Btw again. I found some words on this in BOL 2005, searching for VSS, like:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/0f299867-f499-4c2a-ad6f-b2ef1869381d.htm
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:OOVKXyhcHHA.984@.TK2MSFTNGP04.phx.gbl...
> NTBACKUP is Microsoft. It's the default backup software in the operating system. I don't think
> talking to them is going to get me anywhere.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
>> That sounds horrible to me, to be honest. I'd talk to the guys who wrote this software...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn off the command line SNAP
>> option of NTBACKUP with /snap:off however this defeats the object since there are other files
>> (Non-SQL Server) on the drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
>>NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
>>Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on
>> option is not really an option. The idea is to leave the SQL databases' backups outside of the
>> control of NTBACKUP. This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten to add, that is the
>> only possible cause I have been able to identify thus far however I accept there could be
>> other causes. Luckily this server doesn't have a basket load of other applications / services
>> that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out
>> loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>>> Hi All,
>>>
>>>
>>>
>>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to
>>> Windows Server 2003 SP2 and SQL Server SP2.
>>>
>>>
>>>
>>> For some time we have had the following backup regime for some SQL Server full recovery
>>> model databases that are present on this server:
>>>
>>>
>>>
>>> 1) SQL Server Full backup on a Sunday night at around midnight
>>>
>>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>>>
>>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>>>
>>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database
>>> files excluded.
>>>
>>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>>> another server by a 3rd party application, not by using NTBACKUP.
>>>
>>>
>>>
>>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and
>>> SP2 of Windows Server 2003.
>>>
>>>
>>>
>>> Immediately after that upgrade we would get the Full backup at point 1 completing as
>>> planned, the transaction log backups at point 2 complete on the Monday, then the
>>> differential SQL backup on Monday night works fine as well followed by the NT Backup at
>>> point 4. The cycle works fine on the Tuesday up to the repeat of the SQL Server differential
>>> backup at point 3 which fails for every database with an error message not unlike this
>>> example:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND,
>>> NOUNLOAD, STATS = 10" failed with the following error: "Cannot perform a differential backup
>>> for database "dbTPL", because a current database backup does not exist. Perform a full
>>> database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP
>>> DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query,
>>> "ResultSet" property not set correctly, parameters not set correctly, or connection not
>>> established correctly.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> As if NTBackup has broken the link to the original full backup.
>>>
>>>
>>>
>>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not
>>> manage a backup of SQL Server Full recovery model databases. As in this article here:
>>> http://support.microsoft.com/kb/903643
>>>
>>>
>>>
>>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server
>>> 2005 we get errors around the time NTBACKUP runs that are like this one:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Event Type: Error
>>>
>>> Event Source: SQLVDI
>>>
>>> Event Category: None
>>>
>>> Event ID: 1
>>>
>>> Date: 29/03/2007
>>>
>>> Time: 07:03:47
>>>
>>> User: N/A
>>>
>>> Computer: SERVERA
>>>
>>> Description:
>>>
>>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted
>>> scripts, just output from the Maintenance plan wizard. Furthermore they have been deleted
>>> and recreated since updating to SP2 in case that was the cause but the problem remains.
>>>
>>>
>>>
>>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and
>>> use /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the
>>> conclusion that the Shadow Copy Service or NTBackup has something to do with this? Has
>>> anybody else encountered a similar problem?
>>>
>>>
>>>
>>> I have been researching this for days but due to the relative brief period since the release
>>> of Service Pack 2 for Windows Server 2003 there isn't really too much about on the web
>>> regarding this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for
>>> the thread I found here:
>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>>
>>>
>>>
>>> Any tips / ideas much appreciated.
>>>
>>>
>>>
>>> Kind Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Hi
Take a look at
http://support.microsoft.com/kb/903643
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
> Hi All,
>
> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server
> 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>
> For some time we have had the following backup regime for some SQL Server
> full recovery model databases that are present on this server:
>
> 1) SQL Server Full backup on a Sunday night at around midnight
> 2) SQL Server Transaction log backups every three hours from 03:00
> until 18:00
> 3) SQL Server Differential backups at 21:00 every day except Sunday
> night.
> 4) NTBACKUP at 22:00 every night to do a differential backup of the
> server using option /SNAP:on (Use Volume Shadow Copy) but with the
> directory containing SQL Server database files excluded.
> 5) Note the output TRN files and BAK files from points 1 to 4 above
> are mirrored off to another server by a 3rd party application, not by
> using NTBACKUP.
>
> All has worked fine for many months until our upgrade of the server to SP2
> of SQL Server and SP2 of Windows Server 2003.
>
> Immediately after that upgrade we would get the Full backup at point 1
> completing as planned, the transaction log backups at point 2 complete on
> the Monday, then the differential SQL backup on Monday night works fine as
> well followed by the NT Backup at point 4. The cycle works fine on the
> Tuesday up to the repeat of the SQL Server differential backup at point 3
> which fails for every database with an error message not unlike this
> example:
>
> [QUOTE]
> Executing the query "BACKUP DATABASE [dbTPL] TO DISK => N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME => N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
> failed with the following error: "Cannot perform a differential backup for
> database "dbTPL", because a current database backup does not exist.
> Perform a full database backup by reissuing BACKUP DATABASE, omitting the
> WITH DIFFERENTIAL option. BACKUP DATABASE is terminating abnormally.".
> Possible failure reasons: Problems with the query, "ResultSet" property
> not set correctly, parameters not set correctly, or connection not
> established correctly.
> [END QUOTE]
>
> As if NTBackup has broken the link to the original full backup.
>
> There used to be a problem with the Volume Shadow Copy Service whereby
> NTBACKUP would not manage a backup of SQL Server Full recovery model
> databases. As in this article here: http://support.microsoft.com/kb/903643
>
> I noticed in the event log since our upgrade to SP2 of Windows Server 2003
> and SQL Server 2005 we get errors around the time NTBACKUP runs that are
> like this one:
>
> [QUOTE]
> Event Type: Error
> Event Source: SQLVDI
> Event Category: None
> Event ID: 1
> Date: 29/03/2007
> Time: 07:03:47
> User: N/A
> Computer: SERVERA
> Description:
> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
> ErrorCode=(288)Attempt to release mutex not owned by caller..
> Process=1968. Thread=3564. Client. Instance=. VD=.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> [END QUOTE]
>
> The SQL Server maintenance plans at points 1 through to 3 above are not
> hand crafted scripts, just output from the Maintenance plan wizard.
> Furthermore they have been deleted and recreated since updating to SP2 in
> case that was the cause but the problem remains.
>
> The only way around this problem has been to amend the NTBACKUP command at
> point 4 above and use /SNAP:off so that it doesn't use the Volume Shadow
> Copy service. I can only draw the conclusion that the Shadow Copy Service
> or NTBackup has something to do with this? Has anybody else encountered a
> similar problem?
>
> I have been researching this for days but due to the relative brief period
> since the release of Service Pack 2 for Windows Server 2003 there isn't
> really too much about on the web regarding this. In fact I hadn't even
> though of it being the NTBACKUP if it hadn't been for the thread I found
> here:
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>
> Any tips / ideas much appreciated.
>
> Kind Regards
>
>
>|||Hi all of u, unluckly i am also facing this problem since last month :(.
very horrible thisng this is. I have all of senerio that is dececribed in
this thread I got out from some of articles that that it is due toinserting
LSN number by ntBackup utility in sql server database msdb (from where we can
get all of LSN number).
Wheneever our diff backup job attempt to take backup then its found latest
LSN number (because it takes backup since last full backup, ntbackup writes
LSN for full backup and file over which backup was take unreachable due to
its ntbackup file structure :( ) and al last diff fail because it could not
get last backup.
its prooof is this that u just took full backup and just run diff job u
could get success.
SNAP :OFF option never works even i start/off its serveice too.
"Uri Dimant" wrote:
> Hi
> Take a look at
> http://support.microsoft.com/kb/903643
>
> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
> > Hi All,
> >
> >
> >
> > We recently upgraded a box running Windows Server 2003 SP1 with SQL Server
> > 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
> >
> >
> >
> > For some time we have had the following backup regime for some SQL Server
> > full recovery model databases that are present on this server:
> >
> >
> >
> > 1) SQL Server Full backup on a Sunday night at around midnight
> >
> > 2) SQL Server Transaction log backups every three hours from 03:00
> > until 18:00
> >
> > 3) SQL Server Differential backups at 21:00 every day except Sunday
> > night.
> >
> > 4) NTBACKUP at 22:00 every night to do a differential backup of the
> > server using option /SNAP:on (Use Volume Shadow Copy) but with the
> > directory containing SQL Server database files excluded.
> >
> > 5) Note the output TRN files and BAK files from points 1 to 4 above
> > are mirrored off to another server by a 3rd party application, not by
> > using NTBACKUP.
> >
> >
> >
> > All has worked fine for many months until our upgrade of the server to SP2
> > of SQL Server and SP2 of Windows Server 2003.
> >
> >
> >
> > Immediately after that upgrade we would get the Full backup at point 1
> > completing as planned, the transaction log backups at point 2 complete on
> > the Monday, then the differential SQL backup on Monday night works fine as
> > well followed by the NT Backup at point 4. The cycle works fine on the
> > Tuesday up to the repeat of the SQL Server differential backup at point 3
> > which fails for every database with an error message not unlike this
> > example:
> >
> >
> >
> > [QUOTE]
> >
> > Executing the query "BACKUP DATABASE [dbTPL] TO DISK => > N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
> > WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME => > N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
> > failed with the following error: "Cannot perform a differential backup for
> > database "dbTPL", because a current database backup does not exist.
> > Perform a full database backup by reissuing BACKUP DATABASE, omitting the
> > WITH DIFFERENTIAL option. BACKUP DATABASE is terminating abnormally.".
> > Possible failure reasons: Problems with the query, "ResultSet" property
> > not set correctly, parameters not set correctly, or connection not
> > established correctly.
> >
> > [END QUOTE]
> >
> >
> >
> > As if NTBackup has broken the link to the original full backup.
> >
> >
> >
> > There used to be a problem with the Volume Shadow Copy Service whereby
> > NTBACKUP would not manage a backup of SQL Server Full recovery model
> > databases. As in this article here: http://support.microsoft.com/kb/903643
> >
> >
> >
> > I noticed in the event log since our upgrade to SP2 of Windows Server 2003
> > and SQL Server 2005 we get errors around the time NTBACKUP runs that are
> > like this one:
> >
> >
> >
> > [QUOTE]
> >
> > Event Type: Error
> >
> > Event Source: SQLVDI
> >
> > Event Category: None
> >
> > Event ID: 1
> >
> > Date: 29/03/2007
> >
> > Time: 07:03:47
> >
> > User: N/A
> >
> > Computer: SERVERA
> >
> > Description:
> >
> > SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
> > ErrorCode=(288)Attempt to release mutex not owned by caller..
> > Process=1968. Thread=3564. Client. Instance=. VD=.
> >
> >
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > [END QUOTE]
> >
> >
> >
> > The SQL Server maintenance plans at points 1 through to 3 above are not
> > hand crafted scripts, just output from the Maintenance plan wizard.
> > Furthermore they have been deleted and recreated since updating to SP2 in
> > case that was the cause but the problem remains.
> >
> >
> >
> > The only way around this problem has been to amend the NTBACKUP command at
> > point 4 above and use /SNAP:off so that it doesn't use the Volume Shadow
> > Copy service. I can only draw the conclusion that the Shadow Copy Service
> > or NTBackup has something to do with this? Has anybody else encountered a
> > similar problem?
> >
> >
> >
> > I have been researching this for days but due to the relative brief period
> > since the release of Service Pack 2 for Windows Server 2003 there isn't
> > really too much about on the web regarding this. In fact I hadn't even
> > though of it being the NTBACKUP if it hadn't been for the thread I found
> > here:
> > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
> >
> >
> >
> > Any tips / ideas much appreciated.
> >
> >
> >
> > Kind Regards
> >
> >
> >
> >
> >
> >
>
>|||Found the solution and many thanks to those that contributed to this thread.
I thought I should post my findings back here for anybody else. The first
weird thing was that I found contributions to this thread on other sites
that weren't in my download of the newsgroup from msnews. Ho hum. Anyway,
back to the findings.
I couldn't understand why all of a sudden I was getting broken differential
chains when NT BACKUP was run using volume shadow copy service after
upgrading the servers to SP2 of SQL Server 2005 and SP2 of Windows Server
2003. As in this KB http://support.microsoft.com/kb/903643. I hadn't had
this problem until this upgrade.
Here's the reason:
The "Readme for Microsoft SQL Server 2005 Service Pack 2" at
http://download.microsoft.com/download/2/b/5/2b5e5d37-9b17-423d-bc8f-b11ecd4195b4/ReadmeSQL2005SP2.htm
states:
[Quote]
3.2.6 SQL Server 2005 SP2 Changes the SQL Writer Service Default Startup
Type and Default State
Note the following changes to the SQL Writer service default startup type
and default state:
The SQL Writer service startup type is changed from Manual to Automatic.
The SQL Writer service default state is changed from Stopped to Started.
[END QUOTE]
So I changed it back to manual and stopped the service. This of course
behaved as expected, the VSS didn't try to lock my Full recovery model
databases and break the differential chain. I can still allow /volsnap:on
option with my NTBACKUP commands to backup all the other "open" files on the
volume without breaking the database differential chain.
The thing that started me looking into this was this line in the BOL article
that Tibor mentioned.
[QUOTE]
This SQL Writer Service is automatically installed but not enabled by
default. It must be explicitly enabled to run on the server machine and must
be running at the time that the Volume Shadow Copy Service (VSS) application
requests a backup or restore. Use the Microsoft Windows Services applet to
configure the service. The SQL Writer Service installs on all operating
systems but is only needed on server systems. For Microsoft Windows XP, use
the MSDE Writer.
[END QUOTE]
Hope the above helps somebody else out and once again, thanks to those that
contributed.
Regards
Nick
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:OOVKXyhcHHA.984@.TK2MSFTNGP04.phx.gbl...
> NTBACKUP is Microsoft. It's the default backup software in the operating
> system. I don't think talking to them is going to get me anywhere.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
>> That sounds horrible to me, to be honest. I'd talk to the guys who wrote
>> this software...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn
>> off the command line SNAP option of NTBACKUP with /snap:off however this
>> defeats the object since there are other files (Non-SQL Server) on the
>> drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database
>>files. Can you configure NTBACKUP to not interface with SQL Server? It
>>seems from the eventlog entry you posted that SQL Server got some VDI
>>call from NTBACKUP. This is probably the one that broke the backup
>>chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using
>> NTBACKUP with snap:on option is not really an option. The idea is to
>> leave the SQL databases' backups outside of the control of NTBACKUP.
>> This used to work though until application of the Service Packs and
>> now NTBACKUP seems to be breaking that Differential chain. Although I
>> hasten to add, that is the only possible cause I have been able to
>> identify thus far however I accept there could be other causes.
>> Luckily this server doesn't have a basket load of other applications /
>> services that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files?
>> Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>>> Hi All,
>>>
>>>
>>>
>>> We recently upgraded a box running Windows Server 2003 SP1 with SQL
>>> Server 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>>>
>>>
>>>
>>> For some time we have had the following backup regime for some SQL
>>> Server full recovery model databases that are present on this
>>> server:
>>>
>>>
>>>
>>> 1) SQL Server Full backup on a Sunday night at around midnight
>>>
>>> 2) SQL Server Transaction log backups every three hours from
>>> 03:00 until 18:00
>>>
>>> 3) SQL Server Differential backups at 21:00 every day except
>>> Sunday night.
>>>
>>> 4) NTBACKUP at 22:00 every night to do a differential backup of
>>> the server using option /SNAP:on (Use Volume Shadow Copy) but with
>>> the directory containing SQL Server database files excluded.
>>>
>>> 5) Note the output TRN files and BAK files from points 1 to 4
>>> above are mirrored off to another server by a 3rd party application,
>>> not by using NTBACKUP.
>>>
>>>
>>>
>>> All has worked fine for many months until our upgrade of the server
>>> to SP2 of SQL Server and SP2 of Windows Server 2003.
>>>
>>>
>>>
>>> Immediately after that upgrade we would get the Full backup at point
>>> 1 completing as planned, the transaction log backups at point 2
>>> complete on the Monday, then the differential SQL backup on Monday
>>> night works fine as well followed by the NT Backup at point 4. The
>>> cycle works fine on the Tuesday up to the repeat of the SQL Server
>>> differential backup at point 3 which fails for every database with
>>> an error message not unlike this example:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
>>> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME =>>> N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
>>> failed with the following error: "Cannot perform a differential
>>> backup for database "dbTPL", because a current database backup does
>>> not exist. Perform a full database backup by reissuing BACKUP
>>> DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP DATABASE is
>>> terminating abnormally.". Possible failure reasons: Problems with
>>> the query, "ResultSet" property not set correctly, parameters not
>>> set correctly, or connection not established correctly.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> As if NTBackup has broken the link to the original full backup.
>>>
>>>
>>>
>>> There used to be a problem with the Volume Shadow Copy Service
>>> whereby NTBACKUP would not manage a backup of SQL Server Full
>>> recovery model databases. As in this article here:
>>> http://support.microsoft.com/kb/903643
>>>
>>>
>>>
>>> I noticed in the event log since our upgrade to SP2 of Windows
>>> Server 2003 and SQL Server 2005 we get errors around the time
>>> NTBACKUP runs that are like this one:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Event Type: Error
>>>
>>> Event Source: SQLVDI
>>>
>>> Event Category: None
>>>
>>> Event ID: 1
>>>
>>> Date: 29/03/2007
>>>
>>> Time: 07:03:47
>>>
>>> User: N/A
>>>
>>> Computer: SERVERA
>>>
>>> Description:
>>>
>>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
>>> ErrorCode=(288)Attempt to release mutex not owned by caller..
>>> Process=1968. Thread=3564. Client. Instance=. VD=.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> The SQL Server maintenance plans at points 1 through to 3 above are
>>> not hand crafted scripts, just output from the Maintenance plan
>>> wizard. Furthermore they have been deleted and recreated since
>>> updating to SP2 in case that was the cause but the problem remains.
>>>
>>>
>>>
>>> The only way around this problem has been to amend the NTBACKUP
>>> command at point 4 above and use /SNAP:off so that it doesn't use
>>> the Volume Shadow Copy service. I can only draw the conclusion that
>>> the Shadow Copy Service or NTBackup has something to do with this?
>>> Has anybody else encountered a similar problem?
>>>
>>>
>>>
>>> I have been researching this for days but due to the relative brief
>>> period since the release of Service Pack 2 for Windows Server 2003
>>> there isn't really too much about on the web regarding this. In fact
>>> I hadn't even though of it being the NTBACKUP if it hadn't been for
>>> the thread I found here:
>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>>
>>>
>>>
>>> Any tips / ideas much appreciated.
>>>
>>>
>>>
>>> Kind Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment