Status: 25 "Cannot connect to socket"

[John_England]

I am trying to restore a sql database using the NBU sql agent
and I get the following error

Status:25 "Cannot connect to socket"

Backups and restores work fine for the OS and
backups work fine for SQL but for some reason
the SQL restores are timing out.

I have modified several tcp parameters to try and fix
the problem but that didn't work.

Any ideas on this would be greatly appreciated.

John

[Matthew_Tietje]

Possibly the easiest may be to host file the master/media/client to reference each other just to make sure there isn't a lookup somewhere that's coming in incorrect.

[TempoVisitor]

Status 25 is the NBU dump error code for ... "Sorry, I don't know what's going wrong"

So, don't try to check any connectivity problem. That can come from anywhere.

Maybe a memory problem ... Access to the database ..

For a restore, do you try to restore your database to a different machine ? Source is not the Destination ?

If so, for SQL, you must use the ALTERNATE client restore.

On the master server, under :
/usr/openv/netbackup/db/altnames
x:\VERITAS\NetBackup\db\Altnames\
Create an ascii file named as the SOURCE machine. As the only line in it, write the name of the DESTINATION machine.

Any DATABASE restore is considered a USER restore, therefore can be done by default only from and to the SOURCE machine.

Kerkael