Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

9765

May 30th, 2017 06:00

SQL Backup Configured as NSRSQLSV suddenly failing - error attached

Good day;

Beginning roughly two days ago, the backup for one of our SQL Servers started failing out of the blue - no configuration changes, no server-side changes, nothing.

The only errors I'm getting are:

  1. Unsupported File System

          a. No change to the File System; don't know how this could be an issue

    2. Write-Protected Disc

          b. Nope; no changes made to disk permissions

    3. No space on Disc

          c. Plenty of space on all Drives on the server in question

    4. Drive not found

          d. No changes to Drive Naming, no drives added/removed.

I've been attempting to modify and troubleshoot the configuration for the past couple of days, but no dice. Any assistance is appreciated.

I have attached the full error text.

2017-05-30 09_44_31-NMM_Error.txt - Notepad.png

Thank you!

13 Posts

June 5th, 2017 08:00

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

June 6th, 2017 06:00

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.

263 Posts

June 6th, 2017 07:00

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.

June 6th, 2017 12:00

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!

No Events found!

Top