Backing up SQL databases

[kythri]

So, in my learning how to backup a SQL database, I've discovered that a SQL module needs to be installed on the server that is being backed-up.

I've installed said module on the SQL server, and started a backup to test (saveset of "MSSQL:" defined), and get the following:

Unsuccessful savesets:
* msa-ptracker:MSSQL: 5 retries attempted
* msa-ptracker:MSSQL: save: using 'MSSQL:\' for 'MSSQL:'
* msa-ptracker:MSSQL: save: cannot stat MSSQL:\: Invalid argument
* msa-ptracker:MSSQL: save: RPC error: RPC cannot encode arguments
* msa-ptracker:MSSQL: save: save of MSSQL: to nbacknt.mmc-sil.com failed

So, fun. Just for kicks, I defined the saveset as "MSSQL:\" this time. I got:

Unsuccessful savesets:
* msa-ptracker:MSSQL:\ 5 retries attempted
* msa-ptracker:MSSQL:\ save: using 'MSSQL:\' for 'MSSQL:\'
* msa-ptracker:MSSQL:\ save: cannot stat MSSQL:\: Invalid argument
* msa-ptracker:MSSQL:\ save: RPC error: RPC cannot encode arguments
* msa-ptracker:MSSQL:\ save: save of MSSQL:\ to nbacknt.mmc-sil.com failed

Is there something I've forgotten to install, either on the NetWorker server, or on the SQL server? I don't have the SQL module in my registration section, no temporary enabler code. Is this something I need to do? Our Legato SE said no, but, I find that I get correct answers from non-Legato sources, so…

Thanks for the help!!

 

[Chapter11]

I can't imagine why your SE told you you didn't need a license. At the very least, you need to put in the temporary enabler.

You will also need to change the backup command for that client definition to "nsrsqlsv"

 

[kythri]

Yeah, heh, we're not too thrilled with answers we get from Legato.

It seems that you need to have the ability to say three phrases to get a job for sales/SE's:

"I'll get back to you."
"You'll need to call Professional Services."
"You should purchase AlphaStor."

My SE is getting me an enabler code now, thankfully.

 

[wallace88]

Did you create a client instance that specifically backs up
SQL?

You need to create a new client instance:

name: msa-ptracker
saveset: MSSQL:
backup command: nsrsqlsv

 

[eskolnik]

Try



Ed,

Check the version of the sqlvdi.dll file as instructed below and then follow the instructins to register it. If you are still having problems then please send the nsrsqlsv.log from the SQL client and the messages file from the backup server.

1-PRODUCT SIZE MOD DATE CAB/IEXPRESS RELATIVE PATH
Small Business Server 2000 45,133 8/6/2000 \cd2\sql2000\x86\binn
SQL Server 2000 Developer Edition 45,133 8/6/2000 \x86\binn
SQL Server 2000 Enterprise Edition 45,133 8/6/2000 \x86\binn
SQL Server 2000 Personal Edition 45,133 8/6/2000 \x86\binn
SQL Server 2000 Standard Edition 45,133 8/6/2000 \x86\binn

For above SQL product ,sqlvdi.dll file version should be . 2000.80.194.0

2-PRODUCT SIZE MOD DATE CAB/IEXPRESS RELATIVE PATH
SQL Server 7.0 SP2 98,304 2/8/2000 \binn

For above SQL product,sqlvdi.dll file version should be . 2000.2.8.0

3-PRODUCT SIZE MOD DATE CAB/IEXPRESS RELATIVE PATH
SQL Server 7.0 SP1 94,208 4/12/1999 \x86\x86\binn
For above SQL product,sqlvdi.dll file version should be . 1999.4.12.0

4-PRODUCT SIZE MOD DATE CAB/IEXPRESS RELATIVE PATH
Office 2000 SR1 90,112 11/13/1998 \premium\retail\cd3\sql\x86\binn
SQL Server 7.0 90,112 11/12/1998 \x86\binn
SQL Server included with BackOffice 4.5 90,112 11/13/1998 \x86\binn
For above SQL product,sqlvdi.dll file version should be . 1998.11.13.0

Solution #1
If sqlvdi.dll version is wrong, need to contact microsoft for right sqlvdi.dll

Solution#2
If sqlvdi.dll version is right and getting error above mention error message.
Need to re-register sqlvdi.dll

Septs to register sqlvdi.dll
1. Click the start button, and then click Run
2. In the Open box, type the following:
3. Regsvr32 (path to sqlvdi.dll) where (path to sqlvdi.dll) is the actual path to the SP2 version of the dll

Ed Skolnik