Start a Conversation

Unsolved

This post is more than 5 years old

979

November 13th, 2012 19:00

Index Backup during group restart

Hi All

Curious why index are backed up again for successful save sets when you restart a group to backup the failed save sets?

If that happens there will be two indexes where the first is most relveant to the backup and the second is nothing since it's couple or hours or dates ahead?

What design EMC talkling abt? Adios

ID: esg122456
Use Count: 2
Date Created: 06/20/2011
Date Modified: 10/19/2012
Product(s): NetWorker Server for Linux,NetWorker Server for Unix,NetWorker Server for Windows
Category(ies): Documentation
Status: Approved
Related Bugs:
SOLUTION

Symptoms

When we restart the Group, the index backup of partly successful clients also gets backed up fully.

Cause

This is not a defect. This is by design.

Resolution

FULL BACKUP: When we restart a group, the index of the successful clients (during restart) will always have full backups.

LEVEL BACKUP: When we restart a group, the index of the successful clients (during restart) will have same level backup (not full).

8 Posts

November 13th, 2012 19:00

but why..what is the importance during browse and recoveries?

Symptoms

When a savegrp is restarted to retry the backups of the clients that failed in the group, Networker backups all the clients indexes in the savegrp, even if the backup of the client's data and its index was done successfully during the first run.

Restarting a group causes all indexes to backup.

Cause

working as designed

Resolution

Networker is working as designed. When a savegrp runs, the index of a client is backed up after the backup of the client completes. If the backup of the client fails, the index still gets backed up. When a savegrp is restarted, the indexes of all the clients are backed up, even if the client and its index was successfully backedup during the first run, however the backup will likely will occur at a level 9, unless the backup level for the group is at level 'full'.

14.3K Posts

November 14th, 2012 10:00

If you don't won't this, restart it with no index save option. Index and bootstrap is managed differently and it is not owned by client, but rather backup server and therefore you can't apply same logic to its behavior as you would to failed backup client data.

544 Posts

November 15th, 2012 19:00

Hi JoJR,

You can send to EMC a Request for Enhancement regarding this , by describing the problem and what you recommend to be done technically, providing them your point of view and the target for this option to be to looks better, You can submit your RFE from Powerlink by navigating to :

Home > Support > Request Support > Request a Product Enhancement

Thanks,

Ahmed Bahaa

8 Posts

November 20th, 2012 02:00

Halo Ahmed Bahaa

is tis related to enhancement?...is the backup of index for success ss something is not needed but netweker doing it currently?

8 Posts

November 20th, 2012 02:00

HI Hrvoje

still need the index for those failed and when restart for failed ss, backup the index but not for already successful ones

47 Posts

November 20th, 2012 03:00

NW works as described although you may argue aout the technical necessity for a successful finished backup.

A fair workaround is what we are using - just restart the group for the client(s) from the command line:

     savegrp -c client_1 [-c client_x] -R group

No Events found!

Top