Using DDBoost (3.5) on SQL Svr 2016 to Backup/Restore Avamar

Question

I'm using DDBoost (3.5) on SQL Server 2016SP2-CU2-GDR to Backup/Restore to Avamar.  My backups appear to work correctly, but everytime I attempt to restore, I get the following.  This happens in both the DD Boost plugin for SSMS and from TSQL: Start time: Fri Oct 12 14:45:54 2018 Computer name: XXXXXXX User name: SQLServiceAccount Check the detailed logs that are located at 'C:\Program Files\DPSAPPS\MSAPPAGENT\logs\ddbmsqlrc.log'. The 'Skip client resolution' option is set to true. Client name XXXXXXX' will be used for recovery. Version information for C:\Program Files\DPSAPPS\MSAPPAGENT\bin\ddbmsqlrc.exe: Original file name: ddbmsqlrc.exe Version: 3.5.0.0.Build.113 Comments: Supporting EMC Data Domain Boost for Microsoft Applications 52701:(pid 2156): Command line: C:\Program Files\DPSAPPS\MSAPPAGENT\bin\ddbmsqlrc.exe -a NSR_DFA_SI_DD_HOST=apsdd01.na.ha.honda.com -a NSR_DFA_SI_DD_USER=ddboost -a NSR_DFA_SI_DEVICE_PATH=/SQL-DDboost -a NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox -c XXXXXXX -a SKIP_CLIENT_RESOLUTION=TRUE -C 'DBA'='C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\DBA_Test.mdf', 'DBA_log'='C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\DBA_Test_log.ldf' -f -t 10/12/2018 12:30:07 AM -S normal -d MSSQL:DBA_Test MSSQL:DBA DD_SERVER : YYYYYYYY . Recovering database 'DBA' into 'DBA_Test' ... 158891:(pid 2156): Instant file initialization is not enabled, please enable this feature for improved restore performance. RESTORE database [DBA_Test] FROM virtual_device='EMC#413ca25e-a787-48b4-9592-3ecd60be9521' WITH move 'DBA' to 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\DBA_Test.mdf', move 'DBA_log' to 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\DBA_Test_log.ldf', replace, maxtransfersize = 4194304 Successfully established the direct file retrieval session for save set ID '1539318607' with 'Data Domain' device path '/SQL-DDboost'. 153887:(pid 2156): Microsoft SQL server documentation provides details about the following SQL Server Provider error: 38008:(pid 2156): Processed 2808 pages for database 'DBA_Test', file 'DBA' on file 1. 153416:(pid 2156): (Error: 4035) 35867:(pid 2156): Error processing SQL database 'DBA'. unknown XBSA error 1359 (0x54f) Stop time: Fri Oct 12 14:46:03 2018 Msg 50000, Level 16, State 1, Line 9 Fail! The database apprears partially restored, but is in 'recovering' state and is inaccessible. I cannot seem to find a solution in searching for this problem. Thanks, Terry

Marcos469 · Answer

We have searched alot about this issue. But after applying alot of method still facing the same issue. Going to consult with the support team of the dell. If they shared any type of tips so I will definitely tell you.

Data Protection Solutions

Was this post helpful?