Unsolved

This post is more than 5 years old

11 Posts

2010

June 3rd, 2016 07:00

Help needed with backup group failure

Networker.JPG.jpg

I am struggling to troubleshoot a group backup failure where the output status in the failed window shows as succeeded - see above. The client's daemon.raw gives no clues but I have noticed that the E:\ volume is not being backed up, i.e. there is no mention of it in the output windows or the daemon.raw file. Can anybody help or have any suggestions? My knowledge of Networker is somewhat limited and I'm picking this up in someone's absence.

2.4K Posts

June 4th, 2016 09:00

I do not see a failure as mentioned in the title. If so please state the details.

A missing disk/directory in the report without an error usually points to the fact, that it has been excluded from the backup by an appropriate directive. So we would need to know then client's entries

  save set

  directive

Do not forget that mount points must be manually added if the save set entry has not been defined to 'All'.

June 6th, 2016 02:00

Thanks bingo, I will take a look at the directives. As stated, I am a bit of Networker novice so please bear with me.

The screenshot is the output from the group failure window for the client listed. Agree, there is no mention of a failure so why then is this in the NMC's failure window?

June 6th, 2016 02:00

The save is All.

There is no directive but it looks like E: isn't being backed up.

ccgsccm01.JPG.jpgccgsccm01_2.JPG.jpg

2.4K Posts

June 6th, 2016 04:00

o.k - the other possibility is a "local directive" (a "nsr.dir" file on E:\ which might also skip the whole drive).

You will not see it here as it is maintained locally (at the client).

If you cannot find such file, please run the following command:

     savegrp -v -l full -c -G        like

     savegrp -v -l full -c ccgsccm01.####  -G CCG-Daily

and evaluate the output. It will scan the client's file systems and should tell you more.

45 Posts

June 6th, 2016 09:00

Most likely in this case E: isn't a local drive.  If it's not local, it's not saved under a saveset of "All".  An NFS mount point, for example, should be backed up at source rather than across the network to each and every machine it's mounted on and then across the network again to the storage node.

4 Posts

June 6th, 2016 13:00

Did you try to backup E:\ exclusively?

and at the sametime as a matter of test , you can use save set All-NTFS so that it will backup All local drives excluding System state \ Disaster recovery.

43 Posts

June 7th, 2016 01:00

Hello,

1) Make sure that you don't have a local directive that skip the whole drive backup.

- Open Remote Desktop to the Client -> go to E:\ -> check if you have nsr.dir text file inside the drive or no.

- Open the networker client and perform client-initiated backup for the E:\ drive exclusively.

- You can use the same via CLI and check the output message.

2) go to the client properties -> change the save set from ALL to E:\ and then run the following command on the networker server (check the output message):

savegrp -v -l full -c ccgsccm01.####.####  -G CCG-Daily

June 7th, 2016 02:00

Thank you all for the replies. The backup is now running successfully. The issue was due to snapshot management...the client is a VMware guest and deleting an old snapshot has resulted in successful backups. Thanks again. I picked up some useful tips and really appreciate the help.

1 Rookie

 • 

84 Posts

June 7th, 2016 18:00

Hi, this is interesting since I might have the same problem. Can you tell more about deleting the old snapshot?

June 9th, 2016 01:00

Hi Iman2011, my colleague undertook this aspect of work and I've just been advised that it was a snapshot issue. I guess if you are using snapshots make sure they are cleaned up and maintained.

No Events found!

Top