Is NTBACKUP breaking SQL Server 2005 differential backup chain..again?

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\\d bTPL_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...
>
>