Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- VOX
- Data Protection
- Backup Exec
- BEREMOTE dies after enumerating SQL Databases on x...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
BEREMOTE dies after enumerating SQL Databases on x64 Win2003
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2006 02:27 AM
Setup:
Media Server: Windows Server 2003 Std SP1 (32-bit) Backup Exec: 10.1.5629
Remote Server: Windows Server 2003 Std SP1 (x64) w/ SQL server 2005 x64 standard non-cluster BEREMOTE.EXE v10.1.5629.34. BE installed with AOFO option.
Both servers fully-up-to-date with Windows Updates except IE7.
Symtoms:
When backing up the SQL Server (System State, some files and SQL Server databases) to disk the backup sits at zero bytes before reporting a network error. If I look on the remote server I see the service has died and there's a crash error on the console
I have uninstalled the agent, checked the registry for stray entries, rebooted and re-installed. This has not resolved the issue.
I have run BEREMOTE with -debug and the log is as follows (I have cut the middle bit out but this is the start and end of the log):
11/08/06 23:04:57 Opening debug log C:\Program Files\VERITAS\Backup Exec\RAWS\EARTH-beremote24.log
11/08/06 23:04:57 CleanupOrphanedSnapshots(). Lauching cleanup thread..
11/08/06 23:04:57 CleanupOrphanedSnapshots(). Cleanup thread lauched. Exiting.
11/08/06 23:04:57 Process Windows Firewall is zero; no processing done.
11/08/06 23:04:57 VssSnapshotVolume::CleanupOrphanedSnapshots(). No orphaned snaphots found
11/08/06 23:04:57 FS_InitFileSys
11/08/06 23:04:57 loaded bedsnt5.dll
11/08/06 23:04:57 loaded bedssql2.dll
11/08/06 23:04:57 bedsxchg.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsxese.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsmbox.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 loaded bedspush.dll
11/08/06 23:04:57 bedsnote.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsmdoc.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedssps2.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 loaded bedsupfs.dll
11/08/06 23:04:57 loaded bedsshadow.dll
11/08/06 23:04:57 bedsoffhost.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsdpm.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 loaded bedscps.dll
11/08/06 23:04:57 bedsvx.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsorcl.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsagnt.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 loaded bedssms.dll
11/08/06 23:04:57 loaded bedssmsp.dll
11/08/06 23:04:57 bedsra.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 Initializing FSs
� 11/08/06 23:04:57 Informational: BeDiskFind library 'BEDiskFind.dll' initialized in SHADOW::InitBeDiskFindHelperApis
11/08/06 23:04:57 Informational: Initializing the BeDisk library 'BeDisk.dll' in SHADOW::InitBeDiskHelperApis
11/08/06 23:04:57 Informational: BeDisk library 'BeDisk.dll' initialized in SHADOW::InitBeDiskHelperApis
11/08/06 23:04:57 Status Uknown (0x00000002) opening Cps registry key 'SOFTWARE\Wow6432Node\VERITAS\Backup Exec CPS' in CPS::InitCpsHelperApis:399
11/08/06 23:04:57 Informational: Initializing the Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:430
11/08/06 23:04:57 Status Uknown (0x0000007E) loading Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:437
11/08/06 23:04:57 Status Uknown (0x0000007E) initializing Cps library in CPS::InitFsys:103
11/08/06 23:04:57 Listening on port 10000
SQL2_ThawDatabaseThread: Database Rhetorik1_SITE metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread on Sharepoint.
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database ReportServices metadata transferred.
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database STS_TITAN_1227796762 metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread on SPS01_Config_db.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database RhetorikInternal metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database SPS01_Config_db metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database Sharepoint metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:11
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:11 Database ePanelII thawed.
11/08/06 23:08:11
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:11 Database master thawed.
11/08/06 23:08:11 Database model thawed.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12 Database msdb thawed.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12 Database NetFinder thawed.
11/08/06 23:08:12 Database PRODUCTION_NORDICS thawed.
11/08/06 23:08:12 Database PRODUCTION_NORDICS_CPR thawed.
11/08/06 23:08:12 Database ReportServer thawed.
11/08/06 23:08:12 Database ReportServerTempDB thawed.
11/08/06 23:08:12 Database ReportServices thawed.
11/08/06 23:08:12 Database ReportServicesTempDB thawed.
11/08/06 23:08:12 Database Rhetorik1_PROF thawed.
11/08/06 23:08:12 Database Rhetorik1_SERV thawed.
11/08/06 23:08:12 Database Rhetorik1_SITE thawed.
11/08/06 23:08:12 Database RhetorikInternal thawed.
11/08/06 23:08:12 Database Sharepoint thawed.
11/08/06 23:08:12 Database SPS01_Config_db thawed.
11/08/06 23:08:12 Database STS_TITAN_1227796762 thawed.
Media Server: Windows Server 2003 Std SP1 (32-bit) Backup Exec: 10.1.5629
Remote Server: Windows Server 2003 Std SP1 (x64) w/ SQL server 2005 x64 standard non-cluster BEREMOTE.EXE v10.1.5629.34. BE installed with AOFO option.
Both servers fully-up-to-date with Windows Updates except IE7.
Symtoms:
When backing up the SQL Server (System State, some files and SQL Server databases) to disk the backup sits at zero bytes before reporting a network error. If I look on the remote server I see the service has died and there's a crash error on the console
I have uninstalled the agent, checked the registry for stray entries, rebooted and re-installed. This has not resolved the issue.
I have run BEREMOTE with -debug and the log is as follows (I have cut the middle bit out but this is the start and end of the log):
11/08/06 23:04:57 Opening debug log C:\Program Files\VERITAS\Backup Exec\RAWS\EARTH-beremote24.log
11/08/06 23:04:57 CleanupOrphanedSnapshots(). Lauching cleanup thread..
11/08/06 23:04:57 CleanupOrphanedSnapshots(). Cleanup thread lauched. Exiting.
11/08/06 23:04:57 Process Windows Firewall is zero; no processing done.
11/08/06 23:04:57 VssSnapshotVolume::CleanupOrphanedSnapshots(). No orphaned snaphots found
11/08/06 23:04:57 FS_InitFileSys
11/08/06 23:04:57 loaded bedsnt5.dll
11/08/06 23:04:57 loaded bedssql2.dll
11/08/06 23:04:57 bedsxchg.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsxese.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsmbox.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 loaded bedspush.dll
11/08/06 23:04:57 bedsnote.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsmdoc.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedssps2.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 loaded bedsupfs.dll
11/08/06 23:04:57 loaded bedsshadow.dll
11/08/06 23:04:57 bedsoffhost.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsdpm.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 loaded bedscps.dll
11/08/06 23:04:57 bedsvx.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsorcl.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 bedsagnt.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 loaded bedssms.dll
11/08/06 23:04:57 loaded bedssmsp.dll
11/08/06 23:04:57 bedsra.dll could not be loaded: The specified module could not be found.
11/08/06 23:04:57 Initializing FSs
� 11/08/06 23:04:57 Informational: BeDiskFind library 'BEDiskFind.dll' initialized in SHADOW::InitBeDiskFindHelperApis
11/08/06 23:04:57 Informational: Initializing the BeDisk library 'BeDisk.dll' in SHADOW::InitBeDiskHelperApis
11/08/06 23:04:57 Informational: BeDisk library 'BeDisk.dll' initialized in SHADOW::InitBeDiskHelperApis
11/08/06 23:04:57 Status Uknown (0x00000002) opening Cps registry key 'SOFTWARE\Wow6432Node\VERITAS\Backup Exec CPS' in CPS::InitCpsHelperApis:399
11/08/06 23:04:57 Informational: Initializing the Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:430
11/08/06 23:04:57 Status Uknown (0x0000007E) loading Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:437
11/08/06 23:04:57 Status Uknown (0x0000007E) initializing Cps library in CPS::InitFsys:103
11/08/06 23:04:57 Listening on port 10000
SQL2_ThawDatabaseThread: Database Rhetorik1_SITE metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread on Sharepoint.
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database ReportServices metadata transferred.
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database STS_TITAN_1227796762 metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread on SPS01_Config_db.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database RhetorikInternal metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database SPS01_Config_db metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread: Database Sharepoint metadata transferred.
11/08/06 23:08:11 SQL2_WaitOnSnapThread: waiting
11/08/06 23:08:11
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:11
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:11 Database ePanelII thawed.
11/08/06 23:08:11
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:11 Database master thawed.
11/08/06 23:08:11 Database model thawed.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12 Database msdb thawed.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12
SQL2_ThawDatabaseThread command executed successfully.
11/08/06 23:08:12 Database NetFinder thawed.
11/08/06 23:08:12 Database PRODUCTION_NORDICS thawed.
11/08/06 23:08:12 Database PRODUCTION_NORDICS_CPR thawed.
11/08/06 23:08:12 Database ReportServer thawed.
11/08/06 23:08:12 Database ReportServerTempDB thawed.
11/08/06 23:08:12 Database ReportServices thawed.
11/08/06 23:08:12 Database ReportServicesTempDB thawed.
11/08/06 23:08:12 Database Rhetorik1_PROF thawed.
11/08/06 23:08:12 Database Rhetorik1_SERV thawed.
11/08/06 23:08:12 Database Rhetorik1_SITE thawed.
11/08/06 23:08:12 Database RhetorikInternal thawed.
11/08/06 23:08:12 Database Sharepoint thawed.
11/08/06 23:08:12 Database SPS01_Config_db thawed.
11/08/06 23:08:12 Database STS_TITAN_1227796762 thawed.
Labels:
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2006 08:13 AM
I have spent yet another day trying to diagnose this and have discovered that with AOFO switched-off completely then the backup completes ok and the agent doesn't die.
I backup the SQL server once to disk per day and once to tape. Unfortunately the backup to tape includes lots of other servers and needs to have AOFO switched on to capture our line-of-business applications correctly.
It's worth noting all of our backup jobs worked fine a couple of months ago without being changed. Thus I suspect it's either a Veritas patch or an MS update which has caused this and other issues we're experiencing.
The agent crashing is by far the biggest issue we are currently experiencing though.
I backup the SQL server once to disk per day and once to tape. Unfortunately the backup to tape includes lots of other servers and needs to have AOFO switched on to capture our line-of-business applications correctly.
It's worth noting all of our backup jobs worked fine a couple of months ago without being changed. Thus I suspect it's either a Veritas patch or an MS update which has caused this and other issues we're experiencing.
The agent crashing is by far the biggest issue we are currently experiencing though.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2006 06:42 AM
This is still occurring. I've switched off all of the AOFO which has helped a bit - but this still occurs.
I guess no one from Symantec monitors these now as I've noticed the amount of staff hanging around on the v11d forum!
Time to save up for a competitors product I think? Anyone have any suggestions?
I guess no one from Symantec monitors these now as I've noticed the amount of staff hanging around on the v11d forum!
Time to save up for a competitors product I think? Anyone have any suggestions?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2007 02:34 AM
Joel
we are having exactly the same issue. What we did was exclude the largest database from the set we backup and this has resolved the issue (i.e. all other DBs do backup successfully without the agent crashing). Prior to this issue we were successfully backing up all DBs. The database in question grew beyond 180GB (approx I'm not sure exactly which point it started causing crashes of BEREMOTE). Therefore, I suspect your issue may be the same.
We are attempting to troubleshoot our issue now. We've tried moving the DB to a single 2003 x64 server (it was failing on a cluster for us) and the same results are obtained. If you managed to resolve this issue I'd be interested to hear.
Hope that helps. Excerpt from our own LOG appended here for reference (this is a job that only attemptts to backup the single, large DB):
=============================================
01/17/07 17:08:17 Opening debug log C:\Program Files\VERITAS\Backup Exec\RAWS\LON-MEM-UAT-001-beremote00.log
01/17/07 17:08:17 CleanupOrphanedSnapshots(). Lauching cleanup thread..
01/17/07 17:08:17 CleanupOrphanedSnapshots(). Cleanup thread lauched. Exiting.
01/17/07 17:08:17 Process Windows Firewall is zero; no processing done.
01/17/07 17:08:17 OS Version: 5.2.3790 (Service Pack 1)
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - Using backup type VSS_BT_FULL
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::InitializeForBackup
01/17/07 17:08:17 FS_InitFileSys
01/17/07 17:08:17 loaded bedsnt5.dll
01/17/07 17:08:17 loaded bedssql2.dll
01/17/07 17:08:17 bedsxchg.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsxese.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsmbox.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 loaded bedspush.dll
01/17/07 17:08:17 bedsnote.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsmdoc.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedssps2.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 loaded bedsupfs.dll
01/17/07 17:08:17 loaded bedsshadow.dll
01/17/07 17:08:17 bedsoffhost.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsdpm.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 loaded bedscps.dll
01/17/07 17:08:17 bedsvx.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsorcl.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsagnt.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 loaded bedssms.dll
01/17/07 17:08:17 loaded bedssmsp.dll
01/17/07 17:08:17 bedsra.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 Initializing FSs
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::SetBackupState with backup type 1
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::SetContext with context: 0
� 01/17/07 17:08:17 Informational: BeDiskFind library 'BEDiskFind.dll' initialized in SHADOW::InitBeDiskFindHelperApis
01/17/07 17:08:17 Informational: Initializing the BeDisk library 'BeDisk.dll' in SHADOW::InitBeDiskHelperApis
01/17/07 17:08:17 Informational: BeDisk library 'BeDisk.dll' initialized in SHADOW::InitBeDiskHelperApis
01/17/07 17:08:17 Status Uknown (0x00000002) opening Cps registry key 'SOFTWARE\Wow6432Node\VERITAS\Backup Exec CPS' in CPS::InitCpsHelperApis:399
01/17/07 17:08:17 Informational: Initializing the Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:430
01/17/07 17:08:17 Status Uknown (0x0000007E) loading Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:437
01/17/07 17:08:17 Status Uknown (0x0000007E) initializing Cps library in CPS::InitFsys:103
01/17/07 17:08:17 Listening on port 10000
01/17/07 17:08:17 Agent browser advertisement cycle complete. Advertisement interval is 60 minutes.
01/17/07 17:08:17 Provider GUID = {00000000-0000-0000-0000-000000000000}
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - calling StartSnapshotSet()
01/17/07 17:08:17 VSS snapstarted. SnapshotSetID = {19350a15-8e5f-4b8c-afb6-0d2dca05c3cc}
01/17/07 17:08:17 Orphaned VSS snapshot set cleaned up successfully. SnapshotSetID = {7dccf3d4-65f9-40cf-8ed6-821caa76a1db}
01/17/07 17:08:18 Running... 'Q' to stop
01/17/07 17:08:30 ndmpRun: Control Connection Accepted : connection established between IP 10.216.8.33, port 10000 and IP 10.216.8.26, port 1581
01/17/07 17:08:31 Successfully impersonated DBLCAPITAL\crowley-admin
01/17/07 17:08:31 WhoAmI( ) reports: DBLCAPITAL\crowley-admin
01/17/07 17:08:31 DS_OpenSelectionService
01/17/07 17:08:31
SMSAPIShim: Using BESMDR.DLL.
01/17/07 17:08:31 SQL2_FindDrives - a default SQL Service is installed on LON-MEM-UAT-001.
01/17/07 17:08:31 Opened CurrentVersion registry key.
01/17/07 17:08:31 Retrieved CurrentVersion data.
01/17/07 17:08:31 SQL2_FindDrives - the default SQL Service appears to be SQL 2000.
01/17/07 17:08:31 Found MSSQL.1 in the registry for MSSQLServer
01/17/07 17:08:31 isClusterOK returning 1
01/17/07 17:08:31 SQL2_CreateDLE - creating LON-MEM-UAT-001.
01/17/07 17:08:31 Device Shadow?Copy?Components Dle platform 2 major version 5 minor version 2 build 3790
01/17/07 17:08:31 DeviceIOControl() Failed with error: 21
01/17/07 17:08:31 Utility Partition/Partition's found on this system.
01/17/07 17:08:31 Informational: Cps root device creation using default Cps library mechanism when creating device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:705
01/17/07 17:08:31 Informational: Cps library not available. Not creating Cps root device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:709
01/17/07 17:08:31 FS_ResolveDevName
01/17/07 17:08:31 FS_CreateTempDLE
01/17/07 17:08:31 0 = 1
01/17/07 17:08:31 1 = 1
01/17/07 17:08:31 2 = 1
01/17/07 17:08:31 3 = 1
01/17/07 17:08:31 4 = 1
01/17/07 17:08:31 5 = 1
01/17/07 17:08:31 6 = 1
01/17/07 17:08:31 7 = 0
01/17/07 17:08:31 Error 0 opening cluster on \\LON-MEM-UAT-001
01/17/07 17:08:31 Error 0 on NetShareEnum of \\LON-MEM-UAT-001, level 1
01/17/07 17:08:31 NTFS_SurrogateCalling: LON-MEM-UAT-001
01/17/07 17:08:31 Error opening cluster on LON-MEM-UAT-001:
01/17/07 17:08:31 Enumerating local drives
01/17/07 17:08:31 Creating DLEs:
01/17/07 17:08:31 \\LON-MEM-UAT-001\C:
01/17/07 17:08:31 \\LON-MEM-UAT-001\D:
01/17/07 17:08:31 \\LON-MEM-UAT-001\E:
01/17/07 17:08:31 \\LON-MEM-UAT-001\F:
01/17/07 17:08:31 \\LON-MEM-UAT-001\G:
01/17/07 17:08:31 \\LON-MEM-UAT-001\S:
01/17/07 17:08:31 \\LON-MEM-UAT-001\T:
01/17/07 17:08:31 SQL2_SurrogateCalling - the default SQL Service is running on LON-MEM-UAT-001.
01/17/07 17:08:31 Opened CurrentVersion registry key.
01/17/07 17:08:31 Retrieved CurrentVersion data.
01/17/07 17:08:31 Found MSSQL.1 in the registry for MSSQLServer
01/17/07 17:08:31 isClusterOK returning 1
01/17/07 17:08:31 SQL2_CreateDLE - creating LON-MEM-UAT-001.
01/17/07 17:08:31 Device Shadow?Copy?Components Dle platform 2 major version 5 minor version 2 build 3790
01/17/07 17:08:31 DeviceIOControl() Failed with error: 21
01/17/07 17:08:31 Utility Partition/Partition's found on this system.
01/17/07 17:08:31 Informational: Cps root device creation using default Cps library mechanism when creating device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:705
01/17/07 17:08:31 Informational: Cps library not available. Not creating Cps root device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:709
01/17/07 17:08:31
01/17/07 17:08:31
01/17/07 17:08:32 FS_ResolveDevName
01/17/07 17:08:32
01/17/07 17:08:32 GetUtilityPartitionObjectName: Could not load the engine resource dll. Using the default settings
01/17/07 17:08:32
01/17/07 17:08:32 FS_ResolveDevName
01/17/07 17:08:32 SQL2_Connect worked.
01/17/07 17:08:32
01/17/07 17:08:32 Returning QAI
01/17/07 17:08:32 Returning msdb
01/17/07 17:08:32 Returning model
01/17/07 17:08:32 Returning master
01/17/07 17:08:32 Returning msdb
01/17/07 17:08:32 Returning QAI
01/17/07 17:08:32
01/17/07 17:08:32 SQL DBClose
01/17/07 17:08:32 SQL2_CleanUpSnapInfoList called.
01/17/07 17:08:37 DS_CloseSelectionService
01/17/07 17:09:05 ndmpRun: Control Connection Accepted : connection established between IP 10.216.8.33, port 10000 and IP 10.216.8.26, port 1583
01/17/07 17:09:05 Successfully impersonated DBLCAPITAL\crowley-admin
01/17/07 17:09:05 WhoAmI( ) reports: DBLCAPITAL\crowley-admin
01/17/07 17:09:05 SQL2_FindDrives - a default SQL Service is installed on LON-MEM-UAT-001.
01/17/07 17:09:05 Opened CurrentVersion registry key.
01/17/07 17:09:05 Retrieved CurrentVersion data.
01/17/07 17:09:05 SQL2_FindDrives - the default SQL Service appears to be SQL 2000.
01/17/07 17:09:05 Found MSSQL.1 in the registry for MSSQLServer
01/17/07 17:09:05 isClusterOK returning 1
01/17/07 17:09:05 SQL2_CreateDLE - creating LON-MEM-UAT-001.
01/17/07 17:09:05 Device Shadow?Copy?Components Dle platform 2 major version 5 minor version 2 build 3790
01/17/07 17:09:05 DeviceIOControl() Failed with error: 21
01/17/07 17:09:05 No utility partitions found on any of the disks
01/17/07 17:09:05 Informational: Cps root device creation using default Cps library mechanism when creating device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:705
01/17/07 17:09:05 Informational: Cps library not available. Not creating Cps root device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:709
01/17/07 17:09:05 ndmpdSnapshotPrepare2: Calling DLE_FindByName for device: LON-MEM-UAT-001
01/17/07 17:09:05 dir =
01/17/07 17:09:05 file = QAI
01/17/07 17:09:05 oper = Include
01/17/07 17:09:05 subs = False
01/17/07 17:09:05 wild = False
01/17/07 17:09:05 Attempting VSS Provider
01/17/07 17:09:05 Snapshot factory, using VSS as the snapshot provider.
01/17/07 17:09:05 OS Version: 5.2.3790 (Service Pack 1)
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - Using backup type VSS_BT_FULL
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::InitializeForBackup
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::SetBackupState with backup type 1
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::SetContext with context: 0
01/17/07 17:09:05 -------Begin Provider property dump------
01/17/07 17:09:05 ==> VSS Provider properties:
01/17/07 17:09:05 Provider Name = Microsoft Software Shadow Copy provider 1.0
01/17/07 17:09:05 Provider ID = {b5946137-7b9f-4925-af80-51abd60b20d5}
01/17/07 17:09:05 Provider Type = System
01/17/07 17:09:05 Provider Version = 1.0.0.7
01/17/07 17:09:05 Provider Version ID = {00000001-0000-0000-0007-000000000001}
01/17/07 17:09:05 Component Class ID = {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a}
01/17/07 17:09:05 -------End of Provider property dump------
01/17/07 17:09:05 Provider GUID = {00000000-0000-0000-0000-000000000000}
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - calling StartSnapshotSet()
01/17/07 17:09:05 VSS snapstarted. SnapshotSetID = {e459e694-75bb-4282-8bdb-1d3c65d2039a}
01/17/07 17:09:05 VssSnapshotVolume::GetWriterMetaData() - calling IVssBackupComponents::GatherWriterMetadata.
01/17/07 17:09:05 VssSnapshotVolume::GetWriterMetaData() - waiting for IVssBackupComponents::GatherWriterMetadata to complete.
01/17/07 17:09:06 VssSnapshotVolume::GetWriterMetaData() - IVssBackupComponents::GatherWriterMetadata complete.
01/17/07 17:09:06 Initialized VSS Snapshot Provider
01/17/07 17:09:06 SQL2_Connect worked.
01/17/07 17:09:06
01/17/07 17:09:06 Returning QAI
01/17/07 17:09:06 Returning msdb
01/17/07 17:09:06 Returning model
01/17/07 17:09:06 Returning master
01/17/07 17:09:06 Returning msdb
01/17/07 17:09:06 Returning QAI
01/17/07 17:09:06 SnapshotBackupEngine::scan_file_system() : Volume List size (before prune): 1
01/17/07 17:09:06 SnapshotBackupEngine::scan_file_system(): Volume List size (after prune): 1
01/17/07 17:09:06 Adding volume: T:
01/17/07 17:09:06 SnapshotBackupEngine::snap_file_systems. Start...
01/17/07 17:09:06 MakeValidVolumeName:
01/17/07 17:09:06 volume= and vol_name=
01/17/07 17:09:06 VssSnashotVolume::PrepareToSnapVolumeSet() - done. LastError_: 0
01/17/07 17:09:06 SQL2_PrepareForFreeze: Starting on database QAI.
01/17/07 17:09:06 SQL Agent VDI Check.
01/17/07 17:09:06 SQL Agent VDI Check: Latest DLL registered.
01/17/07 17:09:06 SQL2_StartCommand = BACKUP DATABASE TO VIRTUAL_DEVICE='BE_SQLAgent-QAI__6866fab2_93fb_4ef8_913e_afbe525034f3_' WITH SNAPSHOT
01/17/07 17:09:08
SQL2_PrepareForFreeze: Performing metadata transfer...
01/17/07 17:09:09 *** VDC_PrepareToFreeze ***
01/17/07 17:09:09 Database QAI prepared for freezing.
01/17/07 17:09:09 SQL2_FreezeDatabase: QAI.
01/17/07 17:09:09 *** VDC_Snapshot ***
01/17/07 17:09:09 Database QAI frozen.
01/17/07 17:09:09 VssSnashotVolume::SnapVolumeSet() - calling DoSnapshotSet.
01/17/07 17:09:09 VssSnashotVolume::SnapVolumeSet() - waiting for snap to complete...
01/17/07 17:09:10 VssSnashotVolume::SnapVolumeSet() - snap complete with hr1: 0
01/17/07 17:09:10 Entering VssSnapshotVolume::RegisterWithOrphanage(). SnapshotSetID_ = {e459e694-75bb-4282-8bdb-1d3c65d2039a}
01/17/07 17:09:10 VssSnashotVolume::SnapVolumeSet() - done. LastError_: 0
01/17/07 17:09:10
Database Freeze lasted 1453 milliSeconds.
01/17/07 17:09:10
SQL2_ThawDatabaseThread on QAI.
01/17/07 17:09:10
SQL2_ThawDatabaseThread: Database QAI metadata transferred.
01/17/07 17:09:10 SQL2_WaitOnSnapThread: waiting
01/17/07 17:09:11
SQL2_ThawDatabaseThread command executed successfully.
01/17/07 17:09:11 Database QAI thawed.
========================================================
Regards
Steve
we are having exactly the same issue. What we did was exclude the largest database from the set we backup and this has resolved the issue (i.e. all other DBs do backup successfully without the agent crashing). Prior to this issue we were successfully backing up all DBs. The database in question grew beyond 180GB (approx I'm not sure exactly which point it started causing crashes of BEREMOTE). Therefore, I suspect your issue may be the same.
We are attempting to troubleshoot our issue now. We've tried moving the DB to a single 2003 x64 server (it was failing on a cluster for us) and the same results are obtained. If you managed to resolve this issue I'd be interested to hear.
Hope that helps. Excerpt from our own LOG appended here for reference (this is a job that only attemptts to backup the single, large DB):
=============================================
01/17/07 17:08:17 Opening debug log C:\Program Files\VERITAS\Backup Exec\RAWS\LON-MEM-UAT-001-beremote00.log
01/17/07 17:08:17 CleanupOrphanedSnapshots(). Lauching cleanup thread..
01/17/07 17:08:17 CleanupOrphanedSnapshots(). Cleanup thread lauched. Exiting.
01/17/07 17:08:17 Process Windows Firewall is zero; no processing done.
01/17/07 17:08:17 OS Version: 5.2.3790 (Service Pack 1)
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - Using backup type VSS_BT_FULL
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::InitializeForBackup
01/17/07 17:08:17 FS_InitFileSys
01/17/07 17:08:17 loaded bedsnt5.dll
01/17/07 17:08:17 loaded bedssql2.dll
01/17/07 17:08:17 bedsxchg.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsxese.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsmbox.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 loaded bedspush.dll
01/17/07 17:08:17 bedsnote.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsmdoc.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedssps2.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 loaded bedsupfs.dll
01/17/07 17:08:17 loaded bedsshadow.dll
01/17/07 17:08:17 bedsoffhost.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsdpm.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 loaded bedscps.dll
01/17/07 17:08:17 bedsvx.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsorcl.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 bedsagnt.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 loaded bedssms.dll
01/17/07 17:08:17 loaded bedssmsp.dll
01/17/07 17:08:17 bedsra.dll could not be loaded: The specified module could not be found.
01/17/07 17:08:17 Initializing FSs
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::SetBackupState with backup type 1
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::SetContext with context: 0
� 01/17/07 17:08:17 Informational: BeDiskFind library 'BEDiskFind.dll' initialized in SHADOW::InitBeDiskFindHelperApis
01/17/07 17:08:17 Informational: Initializing the BeDisk library 'BeDisk.dll' in SHADOW::InitBeDiskHelperApis
01/17/07 17:08:17 Informational: BeDisk library 'BeDisk.dll' initialized in SHADOW::InitBeDiskHelperApis
01/17/07 17:08:17 Status Uknown (0x00000002) opening Cps registry key 'SOFTWARE\Wow6432Node\VERITAS\Backup Exec CPS' in CPS::InitCpsHelperApis:399
01/17/07 17:08:17 Informational: Initializing the Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:430
01/17/07 17:08:17 Status Uknown (0x0000007E) loading Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:437
01/17/07 17:08:17 Status Uknown (0x0000007E) initializing Cps library in CPS::InitFsys:103
01/17/07 17:08:17 Listening on port 10000
01/17/07 17:08:17 Agent browser advertisement cycle complete. Advertisement interval is 60 minutes.
01/17/07 17:08:17 Provider GUID = {00000000-0000-0000-0000-000000000000}
01/17/07 17:08:17 VssSnapshotVolume::Initialize() - calling StartSnapshotSet()
01/17/07 17:08:17 VSS snapstarted. SnapshotSetID = {19350a15-8e5f-4b8c-afb6-0d2dca05c3cc}
01/17/07 17:08:17 Orphaned VSS snapshot set cleaned up successfully. SnapshotSetID = {7dccf3d4-65f9-40cf-8ed6-821caa76a1db}
01/17/07 17:08:18 Running... 'Q' to stop
01/17/07 17:08:30 ndmpRun: Control Connection Accepted : connection established between IP 10.216.8.33, port 10000 and IP 10.216.8.26, port 1581
01/17/07 17:08:31 Successfully impersonated DBLCAPITAL\crowley-admin
01/17/07 17:08:31 WhoAmI( ) reports: DBLCAPITAL\crowley-admin
01/17/07 17:08:31 DS_OpenSelectionService
01/17/07 17:08:31
SMSAPIShim: Using BESMDR.DLL.
01/17/07 17:08:31 SQL2_FindDrives - a default SQL Service is installed on LON-MEM-UAT-001.
01/17/07 17:08:31 Opened CurrentVersion registry key.
01/17/07 17:08:31 Retrieved CurrentVersion data.
01/17/07 17:08:31 SQL2_FindDrives - the default SQL Service appears to be SQL 2000.
01/17/07 17:08:31 Found MSSQL.1 in the registry for MSSQLServer
01/17/07 17:08:31 isClusterOK returning 1
01/17/07 17:08:31 SQL2_CreateDLE - creating LON-MEM-UAT-001.
01/17/07 17:08:31 Device Shadow?Copy?Components Dle platform 2 major version 5 minor version 2 build 3790
01/17/07 17:08:31 DeviceIOControl() Failed with error: 21
01/17/07 17:08:31 Utility Partition/Partition's found on this system.
01/17/07 17:08:31 Informational: Cps root device creation using default Cps library mechanism when creating device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:705
01/17/07 17:08:31 Informational: Cps library not available. Not creating Cps root device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:709
01/17/07 17:08:31 FS_ResolveDevName
01/17/07 17:08:31 FS_CreateTempDLE
01/17/07 17:08:31 0 = 1
01/17/07 17:08:31 1 = 1
01/17/07 17:08:31 2 = 1
01/17/07 17:08:31 3 = 1
01/17/07 17:08:31 4 = 1
01/17/07 17:08:31 5 = 1
01/17/07 17:08:31 6 = 1
01/17/07 17:08:31 7 = 0
01/17/07 17:08:31 Error 0 opening cluster on \\LON-MEM-UAT-001
01/17/07 17:08:31 Error 0 on NetShareEnum of \\LON-MEM-UAT-001, level 1
01/17/07 17:08:31 NTFS_SurrogateCalling: LON-MEM-UAT-001
01/17/07 17:08:31 Error opening cluster on LON-MEM-UAT-001:
01/17/07 17:08:31 Enumerating local drives
01/17/07 17:08:31 Creating DLEs:
01/17/07 17:08:31 \\LON-MEM-UAT-001\C:
01/17/07 17:08:31 \\LON-MEM-UAT-001\D:
01/17/07 17:08:31 \\LON-MEM-UAT-001\E:
01/17/07 17:08:31 \\LON-MEM-UAT-001\F:
01/17/07 17:08:31 \\LON-MEM-UAT-001\G:
01/17/07 17:08:31 \\LON-MEM-UAT-001\S:
01/17/07 17:08:31 \\LON-MEM-UAT-001\T:
01/17/07 17:08:31 SQL2_SurrogateCalling - the default SQL Service is running on LON-MEM-UAT-001.
01/17/07 17:08:31 Opened CurrentVersion registry key.
01/17/07 17:08:31 Retrieved CurrentVersion data.
01/17/07 17:08:31 Found MSSQL.1 in the registry for MSSQLServer
01/17/07 17:08:31 isClusterOK returning 1
01/17/07 17:08:31 SQL2_CreateDLE - creating LON-MEM-UAT-001.
01/17/07 17:08:31 Device Shadow?Copy?Components Dle platform 2 major version 5 minor version 2 build 3790
01/17/07 17:08:31 DeviceIOControl() Failed with error: 21
01/17/07 17:08:31 Utility Partition/Partition's found on this system.
01/17/07 17:08:31 Informational: Cps root device creation using default Cps library mechanism when creating device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:705
01/17/07 17:08:31 Informational: Cps library not available. Not creating Cps root device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:709
01/17/07 17:08:31
01/17/07 17:08:31
01/17/07 17:08:32 FS_ResolveDevName
01/17/07 17:08:32
01/17/07 17:08:32 GetUtilityPartitionObjectName: Could not load the engine resource dll. Using the default settings
01/17/07 17:08:32
01/17/07 17:08:32 FS_ResolveDevName
01/17/07 17:08:32 SQL2_Connect worked.
01/17/07 17:08:32
01/17/07 17:08:32 Returning QAI
01/17/07 17:08:32 Returning msdb
01/17/07 17:08:32 Returning model
01/17/07 17:08:32 Returning master
01/17/07 17:08:32 Returning msdb
01/17/07 17:08:32 Returning QAI
01/17/07 17:08:32
01/17/07 17:08:32 SQL DBClose
01/17/07 17:08:32 SQL2_CleanUpSnapInfoList called.
01/17/07 17:08:37 DS_CloseSelectionService
01/17/07 17:09:05 ndmpRun: Control Connection Accepted : connection established between IP 10.216.8.33, port 10000 and IP 10.216.8.26, port 1583
01/17/07 17:09:05 Successfully impersonated DBLCAPITAL\crowley-admin
01/17/07 17:09:05 WhoAmI( ) reports: DBLCAPITAL\crowley-admin
01/17/07 17:09:05 SQL2_FindDrives - a default SQL Service is installed on LON-MEM-UAT-001.
01/17/07 17:09:05 Opened CurrentVersion registry key.
01/17/07 17:09:05 Retrieved CurrentVersion data.
01/17/07 17:09:05 SQL2_FindDrives - the default SQL Service appears to be SQL 2000.
01/17/07 17:09:05 Found MSSQL.1 in the registry for MSSQLServer
01/17/07 17:09:05 isClusterOK returning 1
01/17/07 17:09:05 SQL2_CreateDLE - creating LON-MEM-UAT-001.
01/17/07 17:09:05 Device Shadow?Copy?Components Dle platform 2 major version 5 minor version 2 build 3790
01/17/07 17:09:05 DeviceIOControl() Failed with error: 21
01/17/07 17:09:05 No utility partitions found on any of the disks
01/17/07 17:09:05 Informational: Cps root device creation using default Cps library mechanism when creating device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:705
01/17/07 17:09:05 Informational: Cps library not available. Not creating Cps root device 'Cont?Prot?Srv' in CPS::DetermineRootCpsComponent:709
01/17/07 17:09:05 ndmpdSnapshotPrepare2: Calling DLE_FindByName for device: LON-MEM-UAT-001
01/17/07 17:09:05 dir =
01/17/07 17:09:05 file = QAI
01/17/07 17:09:05 oper = Include
01/17/07 17:09:05 subs = False
01/17/07 17:09:05 wild = False
01/17/07 17:09:05 Attempting VSS Provider
01/17/07 17:09:05 Snapshot factory, using VSS as the snapshot provider.
01/17/07 17:09:05 OS Version: 5.2.3790 (Service Pack 1)
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - Using backup type VSS_BT_FULL
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::InitializeForBackup
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::SetBackupState with backup type 1
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - calling IVssBackupComponents::SetContext with context: 0
01/17/07 17:09:05 -------Begin Provider property dump------
01/17/07 17:09:05 ==> VSS Provider properties:
01/17/07 17:09:05 Provider Name = Microsoft Software Shadow Copy provider 1.0
01/17/07 17:09:05 Provider ID = {b5946137-7b9f-4925-af80-51abd60b20d5}
01/17/07 17:09:05 Provider Type = System
01/17/07 17:09:05 Provider Version = 1.0.0.7
01/17/07 17:09:05 Provider Version ID = {00000001-0000-0000-0007-000000000001}
01/17/07 17:09:05 Component Class ID = {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a}
01/17/07 17:09:05 -------End of Provider property dump------
01/17/07 17:09:05 Provider GUID = {00000000-0000-0000-0000-000000000000}
01/17/07 17:09:05 VssSnapshotVolume::Initialize() - calling StartSnapshotSet()
01/17/07 17:09:05 VSS snapstarted. SnapshotSetID = {e459e694-75bb-4282-8bdb-1d3c65d2039a}
01/17/07 17:09:05 VssSnapshotVolume::GetWriterMetaData() - calling IVssBackupComponents::GatherWriterMetadata.
01/17/07 17:09:05 VssSnapshotVolume::GetWriterMetaData() - waiting for IVssBackupComponents::GatherWriterMetadata to complete.
01/17/07 17:09:06 VssSnapshotVolume::GetWriterMetaData() - IVssBackupComponents::GatherWriterMetadata complete.
01/17/07 17:09:06 Initialized VSS Snapshot Provider
01/17/07 17:09:06 SQL2_Connect worked.
01/17/07 17:09:06
01/17/07 17:09:06 Returning QAI
01/17/07 17:09:06 Returning msdb
01/17/07 17:09:06 Returning model
01/17/07 17:09:06 Returning master
01/17/07 17:09:06 Returning msdb
01/17/07 17:09:06 Returning QAI
01/17/07 17:09:06 SnapshotBackupEngine::scan_file_system() : Volume List size (before prune): 1
01/17/07 17:09:06 SnapshotBackupEngine::scan_file_system(): Volume List size (after prune): 1
01/17/07 17:09:06 Adding volume: T:
01/17/07 17:09:06 SnapshotBackupEngine::snap_file_systems. Start...
01/17/07 17:09:06 MakeValidVolumeName:
01/17/07 17:09:06 volume= and vol_name=
01/17/07 17:09:06 VssSnashotVolume::PrepareToSnapVolumeSet() - done. LastError_: 0
01/17/07 17:09:06 SQL2_PrepareForFreeze: Starting on database QAI.
01/17/07 17:09:06 SQL Agent VDI Check.
01/17/07 17:09:06 SQL Agent VDI Check: Latest DLL registered.
01/17/07 17:09:06 SQL2_StartCommand = BACKUP DATABASE TO VIRTUAL_DEVICE='BE_SQLAgent-QAI__6866fab2_93fb_4ef8_913e_afbe525034f3_' WITH SNAPSHOT
01/17/07 17:09:08
SQL2_PrepareForFreeze: Performing metadata transfer...
01/17/07 17:09:09 *** VDC_PrepareToFreeze ***
01/17/07 17:09:09 Database QAI prepared for freezing.
01/17/07 17:09:09 SQL2_FreezeDatabase: QAI.
01/17/07 17:09:09 *** VDC_Snapshot ***
01/17/07 17:09:09 Database QAI frozen.
01/17/07 17:09:09 VssSnashotVolume::SnapVolumeSet() - calling DoSnapshotSet.
01/17/07 17:09:09 VssSnashotVolume::SnapVolumeSet() - waiting for snap to complete...
01/17/07 17:09:10 VssSnashotVolume::SnapVolumeSet() - snap complete with hr1: 0
01/17/07 17:09:10 Entering VssSnapshotVolume::RegisterWithOrphanage(). SnapshotSetID_ = {e459e694-75bb-4282-8bdb-1d3c65d2039a}
01/17/07 17:09:10 VssSnashotVolume::SnapVolumeSet() - done. LastError_: 0
01/17/07 17:09:10
Database Freeze lasted 1453 milliSeconds.
01/17/07 17:09:10
SQL2_ThawDatabaseThread on QAI.
01/17/07 17:09:10
SQL2_ThawDatabaseThread: Database QAI metadata transferred.
01/17/07 17:09:10 SQL2_WaitOnSnapThread: waiting
01/17/07 17:09:11
SQL2_ThawDatabaseThread command executed successfully.
01/17/07 17:09:11 Database QAI thawed.
========================================================
Regards
Steve
Related Content
- Backup Exec 2015 - Oracle 12 backup linux - OCI_ERROR: ORA-24300: bad value for mode in Backup Exec
- Sharepoint Server Farms FS_NO_MORE Error in Backup Exec
- Job hangs in the backup - There is no error found in Backup Exec
- Error E000FED1 after trying to backup Hyper-V-Machine in Backup Exec
- remote backup failing in Backup Exec
