Hey guys
Just a question.
If I use NtBackup with Sql server 2005 & sql writer started, the NtBackup use the Volume shadow Copy Service and the Sql Server Writer ?
That is if do I do the backup of the log and data files, is these correctly and with consistence?
Very Tanks
Wouldn't you know it I have to restore a database and my tape device is kaput.
The database I need to restore was backed up with TSQL commands. Does anyone know how or if I can use the ntbackup.exe to restore the file to disk ?
I have a similar tape device on another server (but no sql server on that server) and if I could just get the file down to disk I think I can restore from disk.
Any ideas?
I wanted to prevent ntbackup from locking my databases during the nightly backup, so I excluded the ...Data folder from the backup set. However, I think that ntbackup is backing up the databases during the volume shadow copy phase of the backup, even though their folder was excluded from the backup set (I verified this setting in the .bks file). Although the lock only lasts a few seconds, the error message is worrisome and I would prefer to skip the databases completely. How can I stop the volume shadow copy from doing this?
Below is the the sequence of events leading up to the error, most recent first:
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 3/23/2007
Time: 3:01:49 AM
Description:
SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release mutex not owned by caller.
. Process=8684. Thread=7556. Client. Instance=. VD=.
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 18264
Date: 3/23/2007
Time: 3:01:48 AM
Description:
Database backed up. Database: master, creation date(time): 2007/03/12(15:08:23), pages dumped: 1, first LSN: 268:352:37, last LSN: 269:24:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{66DC3082-FB76-4312-AD74-4BDAD9FC7209}1'}). This is an informational message only. No user action is required.
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 3198
Date: 3/23/2007
Time: 3:01:47 AM
Description:
I/O was resumed on database master. No user action is required.
Event Type: Information
Event Source: ESENT
Event Category: ShadowCopy
Event ID: 2003
Date: 3/23/2007
Time: 3:01:47 AM
Description:
lsass (956) Shadow copy 24 freeze stopped.
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 3197
Date: 3/23/2007
Time: 3:01:45 AM
Description:
I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
Event Type: Information
Event Source: ESENT
Event Category: ShadowCopy
Event ID: 2001
Date: 3/23/2007
Time: 3:01:45 AM
Description:
lsass (956) Shadow copy 24 freeze started.
Event Type: Information
Event Source: NTBackup
Event Category: None
Event ID: 8018
Date: 3/23/2007
Time: 3:00:14 AM
Description:
Begin Operation