mgennacc
2 Bronze

Re: Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

Hello

I noticed initially it was stated that the SQL host is running 

NetWorker Client 8.0 and NMM 2.4.0.375 

Please NOTE:

NetWorker Client 8.0 and NMM 2.4.0, 2.4.1  are no longer supported. 

NetWorker Client 8.1 and NMM 3.0 , 3.0 SP1 are no longer supported. 

See Main NetWorker support page for PRODUCT SERVICE LIFE

https://support.emc.com/products/1095_NetWorker

Best ACTION:

You are running a current SQL 2012  or higher 

therefore,   best action is to remove NMM 2.4 and reboot

then remove the 8.0 client

Once removed,  Then remove or rename the old Networker Client installation path,

Then download the most current 8.2.4.x  NetWorker Client and NMM

Cumulative Product Downloads

CLIENT

ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/8.2/8.2.4.6/

NMM

ftp://ftp.legato.com/pub/NetWorker/NMM/Cumulative_Hotfixes/8.2.4/8.2.4.6/

8.x product is similar to the 2.4  will allow you to run backups with a current 8.x product

before planning to move the MOST current product 9.1.1.x   

(There are some major differences in 9.x versus 8.x which is why first recommend upgrading to 8.x)

** If you are still having problems with the 8.2.4.x (Client and NMM)

then please open a service request ticket for support. 

Dell EMC Support

0 Kudos
zwoodcock
2 Bronze

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

Wallace

Followed the instructions, and my "vssadmin list shadowstorage" is now working correctly and displaying the shadow storage information for each drive... however, the backup is still failing with the same error message.

I just deleted the shadowcopy I had to create as part of the linked guide, and I'm running the backup again. I'll update when I see how that goes.

0 Kudos
wlee4
3 Argentum

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

Hope you create sufficient space for the shadow copies.  Check the nmm.raw for details on what happens during the backup.  Does the SQL backups also fail as well?

To simplify the matter, as well as to address @Mauro's concerns about compatibility, you should consider upgrading to a supported n/w version.  Since the n/w server is still 8.0, I would personally not upgrade higher than v8.2.2.6.  At least, after upgrading NMM, you only use it to backup SQL.  The file system backups are backed up using the default save.exe.

The NetWorker 8.2.2.6 client and NMM install kits can be downloaded from:


     ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/8.2/8.2.2.6/nw822_win_x64.zip

     ftp://ftp.legato.com/pub/NetWorker/NMM/Cumulative_Hotfixes/8.2.2/8.2.2.6/nmm822_win_x64.zip

If you installed GLR (Granularity Level Recovery) option when you installed NMM, then you need to reboot during the NMM uninstall.  Installing with GLR will also require a reboot as well.

To determine if you select the GLR option, on the SQL server, open a command line in admin mode, and run:

     driverquery  | find /i "dos"

If it shows an eldos driver, then you will need to reboot during the uninstall and install process.

0 Kudos
zwoodcock
2 Bronze

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

Wallace

No need to update; I've got it working.

Looks like I just needed to delete the manually-created shadow-copies for each drive. Both Filesystem and SQL are working perfectly now.

Thanks so much for the help!

0 Kudos
ElanC
3 Silver

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

SQL backups are performed based on SQL VDI technology.  Hence, checking VSS related errors are not going to help.

What is exact error reported in NSRSQLSV.RAW?  Make sure, you have not selected "Snapshot" for the group properties.  Hope you aware that, SQL VDI does not support snapshot method. 

Hope this helps!!

Thanks,

Elango C

0 Kudos
wlee4
3 Argentum

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

zwoodcock has already told us that he is using VSS...   please look at the screenshots.

The title of this discussion is incorrect.

0 Kudos
ElanC
3 Silver

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

Just checked the attached screeshot.  I think NMM is trying to create a snapshot of Drive B:\.  Generally, A:\ and B:\ are assigned to Floppy drive.  Can you check whether B:\ drive is available or not?  Also, check the SQL Server writer components are listing B:\

You can, run a VSSToolBox v2 application (https://inside.dell.com/community/active/networker-support/blog/2016/09/29/vss-troubleshooting-appli...) and select the "SQL Server Writer" to see / check whether the drive mapping for the SQL components are good.

Thanks,

Elango C

0 Kudos
ble1
7 Thorium

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

I am getting old and I need glasses, but where do you see this B drive?

EDIT: Ah ok, now I see it... I missed that until now... strange indeed...

0 Kudos
zwoodcock
2 Bronze

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

Wallace

Hrvoje Crvelin

ElanC

You mentioned the B:\ Drive: We do - in fact - have a B:\ Drive on this server (God help me; managing servers that someone else imaged and configured is a damned nightmare), but it is labeled as "System Reserved". Older savesets show successful backups of this drive, so I don't know why that would suddenly become a problem.

0 Kudos
mgennacc
2 Bronze

Re: SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Jump to solution

Replying to original question:

Hello

I noticed initially it was stated that the SQL host is running

NetWorker Client 8.0 and NMM 2.4.0.375

Please NOTE:

NetWorker Client 8.0 and NMM 2.4.0, 2.4.1  are no longer supported.

NetWorker Client 8.1 and NMM 3.0 , 3.0 SP1 are no longer supported.

See Main NetWorker support page for PRODUCT SERVICE LIFE

https://support.emc.com/products/1095_NetWorker

Best ACTION:

You are running a current SQL 2012  or higher

therefore,   best action is to remove NMM 2.4 and reboot

then remove the 8.0 client

Once removed,  Then remove or rename the old Networker Client installation path,

Then download the most current 8.2.4.x  NetWorker Client and NMM

Cumulative Product Downloads

CLIENT

ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/8.2/8.2.4.6/

NMM

ftp://ftp.legato.com/pub/NetWorker/NMM/Cumulative_Hotfixes/8.2.4/8.2.4.6/

8.x product is similar to the 2.4  will allow you to run backups with a current 8.x product

before planning to move the MOST current product 9.1.1.x  

(There are some major differences in 9.x versus 8.x which is why first recommend upgrading to 8.x)

** If you are still having problems with the 8.2.4.x (Client and NMM)

then please open a service request ticket for support.

Dell EMC Support

0 Kudos