Trying to restore and got this failures any help

Thank you for your support Hrvoje

Opet ticket with support. Depending on SQL version, you can also try NMM 8.2SP1.

I always used savetime since the beginning. Last time I used sscreate cause I saw it's different, but, as shown, it didn't work,

I registered on support page e found the following known issue on NMM3.0 SP1 Release Notes (https://support.emc.com/docu50593_NetWorker_Module_for_Microsoft_3.0_SP1_Release_Notes.pdf?language=en_US )

----------------------

Error message displayed when recovering SQL VDI backup data (NW121054)

During point-in-time recovery of SQL VDI backup, the following error message appears in the recovery logs:

51281:(pid 5580):nsrsqlrc.c(7399): Could not get saveset record from mmdb; error: 0x00013884

savetime -1 not in media db

80282:(pid 5580):nsrsqlrc.c(4002): Error getting backup endtime from media Database.

However, the restore completes successfully.

----------------------

My problem is that my restore hangs, it's not the same scenario, but clearly there are some problems with NMM code.

Hi rochettapochetta

One last suggestion:

Please run the following command to open NMSQL GUI in "Template" mode:

"C:\Program Files\EMC NetWorker\nsr\bin\nwmssql.exe" -t

Please change the installation path accordingly.

Once the NMSQL GUI opens, please configure the restore exactly as you would like to do it and then click "Restore".

No restore will actually start but instead you will get the exact command to be ran.

Copy the command, and please run it from command line (With Admin rights) but add debug flags at the beginning of the command, for example:

nsrsqlrc.exe -D5vvv ............

Just add -D5vvv right after the .exe and run the command.

Then you can share with us the output of the logs both networkr.raw and nsrsqlrc.raw files.

Also please the daemon.raw file from the client.

You would like also to check the Application event logs to see if there is any useful event.

Thank you,

Carlos

Hi Carlos,

    thanks for your answer.

Nwmssql.exe never uses and returns -z switch, that I need to use because my backup chain starts with a full backup that overlapped with a log backup.

If I simply use the command returned by nwmssql.exe, I get the following error at the first "restore log":

Error: The log in this backup set terminates at LSNxxxxx, which is too early to

apply to the database. A more recent log backup that includes LSN 2011000000355900001 can be restored..

... because it tries to restore the overlapped backup log, and not the subsequent.

So I added both -D5vvv and -z switches to string returnet by nwmssql -t, and executed it to restore the first valid backup log:

C:\Program Files\EMC NetWorker\nsr\bin\nsrsqlrc.exe" -D5vvv -s " " -c " " -f -S norecovery -d "MSSQL:CopyOf " -C " ' '=' ', '=' '" -z -t "Wed Jan 21 13:47:05 2015" "MSSQL: "

69893:(pid 5848):Invalid debug level specified.  This option will be ignored.

43708:(pid 5848):Start time: Fri Feb 06 17:59:35 2015

43621:(pid 5848):Computer Name: User Name:

                  NSR_CLIENT: ;

                  NSR_SERVER:

>;

37725:(pid 5848):Recovering database ' ' into 'CopyOf ' ...

51281:(pid 5848):nsr/db_apps/bsmsql/nsrsqlrc.c(7638): Could not get saveset record from mmdb; error: 0x00014054

savetime -1 not in media db

80282:(pid 5848):nsr/db_apps/bsmsql/nsrsqlrc.c(4161): Error getting backup endtime from media Database.

4690:(pid 5848):RESTORE log [CopyOf ] FROM virtual_device='Legato#a5567427-5336-4c80-a028-a03af88ab833'  WITH norecovery

35866:(pid 5848):The restore of database ' ' completed successfully.

29310:(pid 5848):

Received  264 KB  1 item(s)  from NSR server (size information for snapshot(s) is not available).

43709:(pid 5848):Stop time: Fri Feb 06 18:01:01 2015

As you can see it does not recognize the debug flag, are you sure about that (I didn't find any docs with debug switches)?.

By the way it returns always the same error, but this time restore didn't hang and finished correctly.

Thank you Carlos