48 Posts
0
3258
Set retention for nsrclone from CLI in v18.1
Hello together,
I need to clone some save sets from the CLI. I am running NetWorker v18.1 on a Windows Server 2012 R2. The cloning target is a LTO8 IBM tape. Source would be a Data Domain.
I use the syntax:
nsrclone -v -s -y ‘7 Days’ -b CLONE -S -f saveset_clone_list_01.txt
I get the message:
Invalid retention time: '7 Days'
Beforehand I created a Time Policy which is called '7 Days'. When I use the options "-y" and "-w" I get the message:
Invalid browse retention time: '7 Days'
As since NetWorker v9 there is only a retention policy which is no longer splited in retention and browse policy. I also renamed the Time Policy to something without numbers and a space between. Did also fail.
How can I give a manually nsrclone command a different retention time?
Cheers,
Beacon
bingo.1
2.4K Posts
0
December 13th, 2018 07:00
You do not need to configure a resource if you use the -y option. Resources are necessary for automatic operation.
However, in your case, you specify the retention along with the command anyway.
... -y "7days" ... should do the job as well as
... -y "12/20/2018" ...
jayjay982
48 Posts
0
December 13th, 2018 09:00
I see.
The problem here is that my nsrclones run from a script every night. The retention of the clones shall be 7 days. So I need to work with something like "-y "7 Days"" or so. I don't want to edit my script every day and adjust the retention date.
In NW8 it was no problem to set the retention via "-y month" and "-w month".
bingo.1
2.4K Posts
0
December 13th, 2018 10:00
You can either use absolute dates or relative periods (they will be automatically converted into absolute dates in the background anyway ;-) .
I discovered that relative periods will also be accepted a while ago and tested that with NW 9.2.1.3 .
The only difference: I used the nsrmm command which you can also use to extend the retention date
At that time I used this example:
nsrmm -y -e "+7months" -S
So may I suggest that you copy and modify your command appropriately.
jayjay982
48 Posts
0
December 13th, 2018 12:00
I don't see any difference to what I did.
Clone the Saveset xyz to tape and give it the retention of 7 days.
The primary backup copy resides on a Data Domain which has a retention of 30 days. The clone on the tape can be shorter than that? I see no reason why not.
I want to keep the backup for 30 days on the DD and the clone for 7 days on a tape.
bingo.1
2.4K Posts
0
December 13th, 2018 13:00
It is the '+' which makes the difference.
Here is an example:
C:\>mminfo -avot -r "ssid,volume,ssretent,clretent"
ssid volume retent clretent
4262643662 DEFAULT.001 13.01.2019 13.01.2019
C:\>
C:\>nsrclone -b "Default Clone" -y "+7days" -S 4262643662
180169:nsrclone: Step (1 of 16): NSRCLONE_INIT_PHASE_ONE: nsrclone has been started on host '16-nw2018.eval.local', with command 'nsrclone -b Default Clone -y +7days -S 4262643662 '.
180170:nsrclone: Step (2 of 16): NSRCLONE_INIT_PHASE_TWO: Obtaining nsrclone options.
180172:nsrclone: Step (3 of 16): NSRCLONE_INIT_PHASE_THREE: Performing Recover Pipe to Save disabled cloning.
180173:nsrclone: Step (4 of 16): NSRCLONE_INIT_PHASE_FOUR: Validating the command line arguments.
180179:nsrclone: Updating the total number of steps from 16 to 5 for the non VM save sets workflow.
180596:nsrclone: Step (5 of 5): NSRCLONE_PROCESSING_PHASE_ONE: No additional breakthrough logging steps are logged for the Recover Pipe to Save disabled workflow unless disabled VM save sets exist.
80470:nsrclone: Following volumes are needed for cloning
80471:nsrclone: DEFAULT.001 (Regular)
180598:nsrclone: The nsrclone verification did not detect failures.
12/13/18 22:02:17.834656 Cloned save set list: : 4262643662/1544734670
C:\>
C:\>mminfo -avot -r "ssid,volume,ssretent,clretent"
ssid volume retent clretent
4262643662 CLONE.001 13.01.2019 20.12.2018
4262643662 DEFAULT.001 13.01.2019 13.01.2019
C:\>
It is the clone retention time which matters (clretent).
From the mminfo manpage:
"The clone retention time is the time limit that the clone instance will remain recoverable in the media database."
Unfortunately, you will most likely go for 'ssretent'.