Error E8617

Failed to end restore. (DBNAME=object name, EC=error message/code)

Module

Agent

Reason:

The agent failed to recover the database after a restore job. An internal error occurred in either the agent or the database server.

Action:

Check the agent log file for details and see one of the following sections for more information:

• If you received a Remote Procedure Call Failed error, see the following section Remote Procedure Call Failed.
• If you are restoring to a Microsoft SQL Server and a SQL Server error 3242 occurs, see the following section SQL Server Error: Backward Compatibility Protocol Mismatch.
• If you are restoring to a Microsoft SQL Server and a SQL Server error 3268 is specified, see the following section SQL Server Error: VDI Format Mismatch.
• If you are restoring a large database to Microsoft SQL Server and SQL server reports either that it cannot create files or that the restore operation is terminating abnormally, see the following section File Creation VDI Timeout.
• Failed to perform point-in-time restore and recovery of the Lotus Domino database. Need log file to perform recovery.
• The Lotus Domino database is not the latest copy.
• Backup was later than the specified recovery point in time.

Remote Procedure Call Failed

Module

Agent

Reason:

This error message indicates one of the following conditions:

• The Agent RPC Server service was reset during the restore operation.
• The target database resides on a virtual Windows server in a cluster, and the Windows quorum failed over to a different machine in the cluster during the restore operation.

Action:

To resolve this error, perform the following steps:

1. Check the status of the database or tablespace being restored on the target database server and verify that the restore job completed successfully. In addition, check the agent log for error messages that may not have been posted to the Arcserve Backup activity log.
2. If other jobs are running, wait for them to finish.
3. Restart the Agent RPC Server service on the machine to which the data was restored. If the target database server is on a cluster, restart the Agent RPC Server service on all nodes of the cluster.

SQL Server Error: Backward Compatibility Protocol Mismatch

Module

Agent

Reason:

A restore of a backup created with BrightStor ARCserve 2000 for Windows, and which utilized the Named Pipes protocol, was attempted using a version of BrightStor ARCserve Backup prior to r12 or BrightStor Enterprise Backup Agent for Microsoft SQL Server.

Action:

Perform the following steps on the computer running the BrightStor ARCserve Backup Server:

1. Open the Registry Editor, and find and select the key HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Common\DBAgentsSettings.
2. In the Edit menu, select the New submenu, and from there select DWORD value. Set the name of this value to SQLProtocol, and its value to 0.
3. Resubmit the Restore job.
4. After all restores are completed for Named Pipe backups from previous versions of BrightStor ARCserve Backup, return to the Registry Editor, and delete the "SQLProtocol" value.

SQL Server Error: VDI Format Mismatch

Module

Agent

Reason:

A restore of a tape created with BrightStor ARCserve 2000 or BrightStor Enterprise Backup 10.0 using a different block size or number of stripes than the current default was attempted using a version of BrightStor ARCserve Backup prior to r12 or BrightStor Enterprise Backup 10.5 Agent for Microsoft SQL Server.

Action:

On the computer running the Agent for Microsoft SQL Server, open the Agent for Microsoft SQL Server Configuration. If you have manually changed the VDI Block Size value at any time, change this value to match the value you used when the backup was made. If the backup was made using the BrightStor ARCserve 2000 for Windows Backup Agent for Microsoft SQL Server or earlier, change the value to 512. Stop and restart the Backup Agent Remote Service, and resubmit the restore job.

SQL Server Error: File Creation VDI Timeout

Module

Agent

Reason:

A restore of a Microsoft SQL Server database with large data files was attempted, and the VDI timeout is too short for Microsoft SQL Server to initialize the files.

Action:

In the Agent for Microsoft SQL Server Configuration utility, increase the maximum VDI wait time for creating files in restore. The default value is 2 1/2 hours or 9,000,000 milliseconds.

Other reasons

Module

Agent

Action:

Restore the required transaction log file first, and then perform point-in-time recovery again.

The database file DBIID is changed. A point-in-time recovery is not possible with this error. A full backup job should be scheduled immediately whenever the DBIID is changed.

Verify that the specified point-in-time date and time is set correctly. This restore option is displayed in the Agent for Lotus Domino Restore Options dialog. To access this dialog, select the Lotus Domino server, right-click, and select Agent Option.