NetWorker

Last reply by 11-28-2022 Solved
Start a Discussion
2 Bronze
2 Bronze
444

index 6895:save: retention time `Sat Nov 19 23:59:00 GMT+0100 2022' not in future

Hi guys,
very old configuration with networker 7.6, once a week i receive this message:

NetWorker savegroup: (alert) *group_name completed, Total 1 client(s), 1 Failed. Please see group completion details for more information.

Failed: *client_name

Start time: Sat Nov 19 23:25:00 2022
End time: Sun Nov 20 04:07:54 2022

--- Unsuccessful Save Sets ---

* client_name:index 6895:save: retention time `Sat Nov 19 23:59:00 GMT+0100 2022' not in future

--- Successful Save Sets ---
CUT save sets.


I have this issue only when the job exceed midnight and finish a next day.
I think that backup is successfully and the problem is only on the index file, correct?
Any suggest to prevent this failed?
Thanks a lot

Solution (1)

Accepted Solutions
3 Argentum
439

so you actually backup the index at the end of each and every single group being run?

Instead of running the index backups like that and even have the group fail, if anything happens to the index backup part, in the past we disabled the index backup part for each group and had separate groups setup for index backups, adding an x-amount of clients to each such group to ONLY make index backups for attached clients. This was setup in larger environments. If yours is smaller, than one group to perform index backups might be good enough.

Means however that for every client you introduce, you have to make sure it is assigned to one of these index-backup-only groups. That is something you can check with nsradmin to see if there is at least one client instance that has been assigned to such an index-only backups group.

You then can run these index-backups-only groups during office hours instead of the in the middle of the backup window. Thus you also have separated the success of the index backup from that of the actual backup. Depending on how tickets might be created or backup failures are dealt with, for us it was a no-brainer to separate them from each other at the time so that a backup failure could be handled by the team actually responsible for the data in the backup, so for example the OS or DB team, as most of the backup failures were due to issues on client end, not on backup server end...

not saying this will address any issue, but at least you don't have the issue of backups starting before 12AM and ending after, as you'd have separated the index backup altogether from the backup.

You can use the option "savegroup -O" also to run them from CLI. We had that in place also for some time, from crontab on our Unix backup servers when NW didn't offer to do this from the GUI yet.

–O Saves only each client’s index (the bootstrap is also saved).

from the nw7.6.3 manual:

Backing up only client file indexes and the bootstrap
You can set up a backup group to backup only the client file index information for
those NetWorker clients that belong to the backup group. The bootstrap will also be backed up.
To backup only the client file indexes and the bootstrap:
1. Set up a backup group as described in“Task 2: Set up a group for backup clients” on page 57
2. In the backup group properties Advanced tab, select Index only from the Options attribute.
3. Click OK.

-----------------------------------------------------------------------------------------------------------------
Not a Dell employee. Just doing this to try to help out others. Sharing with the community.
-----------------------------------------------------------------------------------------------------------------

View solution in original post

Replies (2)
3 Argentum
440

so you actually backup the index at the end of each and every single group being run?

Instead of running the index backups like that and even have the group fail, if anything happens to the index backup part, in the past we disabled the index backup part for each group and had separate groups setup for index backups, adding an x-amount of clients to each such group to ONLY make index backups for attached clients. This was setup in larger environments. If yours is smaller, than one group to perform index backups might be good enough.

Means however that for every client you introduce, you have to make sure it is assigned to one of these index-backup-only groups. That is something you can check with nsradmin to see if there is at least one client instance that has been assigned to such an index-only backups group.

You then can run these index-backups-only groups during office hours instead of the in the middle of the backup window. Thus you also have separated the success of the index backup from that of the actual backup. Depending on how tickets might be created or backup failures are dealt with, for us it was a no-brainer to separate them from each other at the time so that a backup failure could be handled by the team actually responsible for the data in the backup, so for example the OS or DB team, as most of the backup failures were due to issues on client end, not on backup server end...

not saying this will address any issue, but at least you don't have the issue of backups starting before 12AM and ending after, as you'd have separated the index backup altogether from the backup.

You can use the option "savegroup -O" also to run them from CLI. We had that in place also for some time, from crontab on our Unix backup servers when NW didn't offer to do this from the GUI yet.

–O Saves only each client’s index (the bootstrap is also saved).

from the nw7.6.3 manual:

Backing up only client file indexes and the bootstrap
You can set up a backup group to backup only the client file index information for
those NetWorker clients that belong to the backup group. The bootstrap will also be backed up.
To backup only the client file indexes and the bootstrap:
1. Set up a backup group as described in“Task 2: Set up a group for backup clients” on page 57
2. In the backup group properties Advanced tab, select Index only from the Options attribute.
3. Click OK.

-----------------------------------------------------------------------------------------------------------------
Not a Dell employee. Just doing this to try to help out others. Sharing with the community.
-----------------------------------------------------------------------------------------------------------------
377

Thanks, I'll try to follow your advice!

Best regards

Latest Solutions
Top Contributor