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
When we restart the Group, the index backup of partly successful clients also gets backed up fully.
This is not a defect. This is by design.
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).
but why..what is the importance during browse and recoveries?
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.
working as designed
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'.
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.
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 :
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