Restore of DB says success but the db doesn't exist!?

[frdba]

I'm using Arcserve9 Build 2020. I have a production backup that I'm trying to test a restore on. I am trying to restore it to a different server because there is not enough space for 2 dbs on the production server. The db is about 350gb, backed up with BAB9, restoring to a BAB9 server

I could not restore to a test server1 because of the following errors:

E8562 Failed to receive data from the database agent. (ADDRESS=\\Server1, EC=10060
and

E8617 Failed to end restore. (DBNAME=DB1, EC=Server1:[SQL Server] szSqlState = 37000,fNativeError = 3156, errMsg = [Microsoft][ODBC SQL Server Driver][SQL Server]File 'DB1_Data' cannot be restored to 'E:\Microsoft SQL Server\MSSQL\Data\DB1_data.mdf'. Use WITH MOVE to identify a valid location for the"?wDB1

All confusing, because I renamed the datafiles which should satisfy the WITH MOVE part. There is plenty of room. The versions of Arcserve are the same across the board, so E8562 doesn't make sense to me.

So I am now trying to restore to test server2. I kicked off the job, it ran for 2.5 hours and reported that the restore was successful. However, the job only reported 256k processed, the datafiles do not exist in the target directory, therefore the database appears to not exist. No errors anywhere.

Anyone have any ideas on what could be wrong? I'm baffled.

TIA

 

[davidmichel]

Based off the log entry it seems you are trying to restore some version of MS SQL.

Enable debug and check the logs.
HKEY_LOCAL_MACHINE \ SOFTWARE \ ComputerAssociates \ BrightStor ARCserve Backup \ DSAgent \ CurrentVersion \ agent \ dbasql

Value name: Debug
Data type: REG_DWORD
Data: 1

Other acceptable data values = 2, 3 (higher value generating the most detail in the log)

Result: in the Agent directory you will find:

dbasql.log
dbasql.trc

 

[frdba]

I ended up creating an empty db, then forced the restore over it. It appears to have restored the db successfully, even though it ended with a crash. I seem to be able to pull any data I need, and the mb processed matched up to the size of the db. I figured it crashed writing to the arcserve db, but I haven't had time to check out that theory.


When I find some time, I'll run the debug and see if it will tell me exactly what the deal is.
Thanks!