Restore of a SQL database to a SQL instance with the default data and log paths are stored on different volumes completes successfully but the database is left in a restoring status.

Article:TECH213431  |  Created: 2013-12-18  |  Updated: 2014-06-18  |  Article URL http://www.symantec.com/docs/TECH213431
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



When attempting to restore a SQL database to a SQL server instance that has the default data and log paths set to different volumes will complete the restore successfully but the database is not usable and or left in a restoring status.


Error



Debug output from the SQL Server:

[fsys\sql2]          - SQL attach called
[fsys\sql2]          -
[fsys\sql2]          -  >>>> The SQL Agent was passed NT Credentials for user name: 'USERNAME'
[fsys\sql2]          -  >>>> the agent will ignore these credentials.  NT credentials
[fsys\sql2]          -  >>>> need to be applied at the parent server level instead.
[fsys\sql2]          -  >>>> Only SQL credentials should be applied to the SQL resource.
[fsys\sql2]          -
[fsys\sql2]          - Attempting attach with inherited credentials
[fsys\sql2]          - SQL2_Connect worked.
[fsys\sql2]          - SQL Agent: Version String { 10.50.4000.0 }
[fsys\sql2]          - SQL edition returned: Standard Edition (64-bit)
[fsys\shared]        - FS_FshGen: Failure to create debug trace object at line number 132
[fsys\sql2]          - attach restore dbcc
[fsys\shared]        - Attach to SQL_INSTANCE
[fsys\sql2]          - Returning Database DB_NAME - Log backup supported
[fsys\sql2]          - PrePost Proc called.
[fsys\sql2]          - Check for active snapshot restore process left hanging to complete
[fsys\sql2]          - Checking for active snapshot SQL_INSTANCE\DB_NAME
[fsys\sql2]          - Found active snapshot SQL_INSTANCE\DB_NAME, starting recovery
[fsys\sql2]          - Calling SQL to complete snapshot restore
[fsys\sql2]          - Snapshot Restore Cmd: RESTORE DATABASE [DB_NAME] FROM VIRTUAL_DEVICE='VDI_NAME' WITH SNAPSHOT, NORECOVERY, MOVE 'DB_Data' TO 'DATA_PATH', MOVE 'DB_Log' TO 'LOG_PATH'
[fsys\sql2]          - SQL2_StartCommand = RESTORE DATABASE [DB_NAME] FROM VIRTUAL_DEVICE='VDI_NAME' WITH SNAPSHOT, NORECOVERY, MOVE 'DB_Data' TO 'DATA_PATH', MOVE 'DB_Log' TO 'LOG_PATH'
[fsys\sql2]          - metadata transfer in progress
[fsys\sql2]          - *** VDC_MountSnapshot ***
[fsys\sql2]          - metadata transfer complete
[fsys\sql2]          - SQL2_WaitOnSnapThread: waiting
[fsys\sql2]          - SQL Error GUID: 636f980
[fsys\sql2]          - SQL Error Source: Microsoft OLE DB Provider for SQL Server
[fsys\sql2]          - SQL Error Description: RESTORE DATABASE is terminating abnormally.
[fsys\sql2]          - SQL Error State: 42000
[fsys\sql2]          - SQL Error Number: 3013
[fsys\sql2]          - SQL Error GUID: 636f980
[fsys\sql2]          - SQL Error Source: Microsoft OLE DB Provider for SQL Server
[fsys\sql2]          - SQL Error Description: The file "DB_LOG" failed to initialize correctly. Examine the error logs for more details.
[fsys\sql2]          - SQL Error State: 42000
[fsys\sql2]          - SQL Error Number: 3283
[fsys\sql2]          - SQL2_WaitOnSnapThread: thread exit code != SUCCESS: 0
[fsys\sql2]          -
SQL2_FinishSnapshotRestore command failed.
[fsys\sql2]          - Delete snapshot object DB_NAME
[fsys\sql2]          - returning Context directory PATH
[fsys\sql2]          - SQL2: Attempted to recover database DB_NAME that wasn't loading.
[fsys\shared]        - Detach from SQL_INSTANCE
[fsys\sql2]          - detach called
[fsys\sql2]          - SQL DBClose
[fsys\sql2]          - SQL2_CleanUpSnapInfoList called.


Solution



This issue is resolved in Backup Exec 2014 or later versions. 

To resolve this issue and receive the new Backup Exec improvements please upgrade to the current version of Backup Exec
NOTE:   Symantec continues to focus on the current release and future releases, there are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see  http://www.symantec.com

Supplemental Materials

SourceETrack
Value3396253
Description

SQL: Restore of a database with data and log files on different drives does not place the ldf in the correct path.



Article URL http://www.symantec.com/docs/TECH213431


Terms of use for this information are found in Legal Notices