2.4K Posts

May 5th, 2017 07:00

I assume you locally export your SQL data to a file and backup these files - correct?

If so - the restore is nothing else but a directed file recovery which you can of course run from GUI or the command line.

Of course you must do the administrative SQL cleanups later.

2 Posts

May 8th, 2017 04:00

Thanks for the reply!

We perform networker backups of Sql databases, i.e. via a cmdline script:

Call "C:\Program Files\EMC NetWorker\nsr\bin\nsrsqlsv.exe" -c "SqlInstance" -s "NWInstance" -b "NWSaveSet" -S 3 -k -l full -N "Description" MSSQL:"SqlDatabase"

We want to restore via cmdline to a DR instance that has different volumes for the SqlData and SqlLog files.

For traditional native restores, we would restore and redirect i.e.

Restore Database SqlDatabase From Disk = ‘bakPath’ With Move ‘LogicalFilename1’ to ‘X:\SqlData\LogicalFilename1.ndf’, Move ‘LogicalFilename2’ to ‘X:\SqlData\LogicalFilename2.ndf’…

I see where the Networker cmdline restore includes file move commands, but can we retrieve a list of logical filenames from Networker in order to populate?

Christopher.

4 Operator

 • 

14.4K Posts

May 19th, 2017 06:00

No... well almost no... you can see logical names via nsrinfo, but then you need to get nsavetime via mminfo and feed it to nsrinfo and be sure you extract right thing.

No Events found!

Top