Fout met Veritas Backup Exec 9

[anoniem]

Hallo Ik heb het volgende: Windows 2003 server Active directory SQL server Enterprise 2000 en Veritas Backup Exec 9 Als ik een backup wil maken met Veritas van de bestanden en een SQL database gemaakt door Exact Globe 2000 dan geeft hij de volgende fout aan na het backuppen: Completed status: Failed Expand AllCollapse All Job Information Job server: BK001 Job name: Backup 0002 Job started: dinsdag 4 januari 2005 at 18:00:12 Job type: Backup Job Log: BEX00014.xml Device and Media Information Drive Name: Dinsdag Media Label: B2D000009 Media GUID: {4D749F2E-87D1-4169-9F06-FD324B635757} Overwrite Protected Until: 31-12-9999 0:00:00 Appendable Until: 31-12-9999 0:00:00 Targeted Media Set Name: Media Set 1 Job Operation - Backup Backup Options Media operation - overwrite. Hardware compression enabled. Server - \\BK001 Set Information - D: OVERIGE Backup Set Information Family Name: "Media created 4-1-2005 18:00:14" Backup of "D: OVERIGE" Backup set #1 on storage media #1 Backup set description: "Backup 0002" Backup Type: FULL - Back Up Files - Reset Archive Bit Backup started on 4-1-2005 at 18:01:30. Backup Set Detail Information Drive Name: Dinsdag Media Label: B2D000010 Media GUID: {EE7D8032-1096-4BF1-8970-5010BB150F63} Overwrite Protected Until: 31-12-9999 0:00:00 Appendable Until: 31-12-9999 0:00:00 Targeted Media Set Name: Media Set 1 Backup set #1 on storage media #2 Backup completed on 4-1-2005 at 18:38:45. Backup Set Summary Backed up 4081 files in 306 directories. Processed 1.940.101.519 bytes in 36 minutes and 49 seconds. Throughput rate: 50.3 MB/min Set Information - BK001 Backup Set Information Family Name: "Media created 4-1-2005 18:00:14" Backup of "BK001 " Backup set #2 on storage media #2 Backup set description: "Backup 0002" Backup Type: DATABASE - Back Up Entire Database Microsoft SQL Server Agent: Started Backup started on 4-1-2005 at 18:38:54. Backup Set Detail Information An error occurred on a query to database 001. A SQL Server virtual device access denied error occurred. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml The item BK001\001 in use - skipped. Backup completed on 4-1-2005 at 18:38:57. Backup Set Summary 1 item was skipped. Processed 0 bytes in 3 seconds. Throughput rate: 0.000 MB/min This backup set may not contain any data. Job Operation - Verify Drive Name: Dinsdag Media Label: B2D000009 Media GUID: {4D749F2E-87D1-4169-9F06-FD324B635757} Overwrite Protected Until: 31-12-9999 0:00:00 Appendable Until: 31-12-9999 0:00:00 Targeted Media Set Name: Media Set 1 Set Information - D: OVERIGE Verify Set Information Verify of "D: OVERIGE" Backup set #1 on storage media #1 Backup set description: "Backup 0002" Verify started on 4-1-2005 at 18:39:00. Verify Set Detail Information Drive Name: Dinsdag Media Label: B2D000010 Media GUID: {EE7D8032-1096-4BF1-8970-5010BB150F63} Overwrite Protected Until: 31-12-9999 0:00:00 Appendable Until: 31-12-9999 0:00:00 Targeted Media Set Name: Media Set 1 Verify completed on 4-1-2005 at 19:14:40. Verify Set Summary Verified 4081 files in 306 directories. 0 files were different. Processed 1.940.101.519 bytes in 35 minutes and 38 seconds. Throughput rate: 51.9 MB/min Set Information - BK001 Verify Set Information Verify of "BK001 " Backup set #2 on storage media #2 Backup set description: "Backup 0002" Verify started on 4-1-2005 at 19:14:41. Verify completed on 4-1-2005 at 19:14:41. Verify Set Summary Processed 0 bytes in 1 second. Throughput rate: 0.000 MB/min Job Completion Status Job ended: dinsdag 4 januari 2005 at 19:14:41 Completed status: Failed Final error: 0xa0008492 - Database Query Failure - see job log for details. Final error category: Resource Errors Errors Click an error below to locate it in the job log Backup - BK001 An error occurred on a query to database 001. A SQL Server virtual device access denied error occurred. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml Exceptions Click an exception below to locate it in the job log Backup - BK001 The item BK001\001 in use - skipped. Iemand enig idee? MVG

[anoniem]

support.veritas.com al geprobeerd? mogelijk een permission probleem. account wat de backup maakt heeft mogelijk geen rechten op de data die je wil backuppen.

[anoniem]

Google: Cause: The error message is a result of a Virtual Device Interface (VDI) failure on the SQL machine. Backup Exec 10.x will only use VDI for backups of Microsoft SQL. There are still registry keys regarding Named Pipes in Backup Exec 10.0, however, they can only be used for restoring from a backup made with Named Pipes (backed up with a previous version of Backup Exec). The keys are still visible but they are disabled for backups. They are still valid for restore purposes. HKLM\Software\VERITAS\Backup Exec\Engine\SQL Server\MaxPipeWaitTime HKLM\Software\VERITAS\Backup Exec\Engine\SQL Server\Force Named Pipes Backup/Restore HKLM\Software\VERITAS\Backup Exec\Engine\SQL Server\NumRestorePipes Microsoft Knowledge Base: According to the Microsoft article 280759, when SQL 2000 and 7.0 are installed on the same machine and the backup fails, this is caused by a mismatch between Sqlvdi.dll and Sqlresld.dll. 1. When SQL 2000 is installed, it registers the SQL VDI COM Server (MSSQL-VDI-Server) to point to the Sqlvdi.dll of SQL 2000 (generally installed on \Program Files\Microsoft SQL Server\MSSQL\COM\80). So this VDI COM object uses this DLL for SQL 7.0 and SQL 2000. 2. The initialization of the VDI COM depends on the loading of Sqlresld.dll 3. Normally, different versions of Sqlresld.dll can co-exist. Infact they are loaded by each SQL server process (the 7.0 version of Sqlresld.dll into the SQL Server 7.0 server process, and the 2000 version of Sqlresld.dll into the SQL Server 2000 server process). 4. The failure happens when the 7.0 - Sqlresld.dll has been loaded (as a result of using Enterprise Manager or some other operation or DLL) and the 2000 Sqlvdi.dll looks for routines owned by the 2000 - Sqlresld.dll and not by the 7.0 - Sqlresld.dll. Workaround 1. In the SQL 7.0 installation path (by default \Mssql7\Binn) rename the DLL's Sqlresld.dll and Sqlvdi.dll to Sqlresld7.old and Sqlvdi7.old 2. Copy from the SQL 2000 installation path (by default \Program Files\Microsoft SQL Server\80\COM) the DLL's Sqlresld.dll and Sqlvdi.dll into the SQL 7.0 installation path (by default \Mssql7\Binn) 3. According to the Microsoft article, it is also recommended to place the Sqlunirl.dll and Sqlsvc.dll (into \Mssql7\Binn) due to the DLL's dependencies. Further details can be found at http://support.microsoft.com/default.aspx?scid=kb;en-us;280759