Unsolved
1 Rookie
•
11 Posts
0
380
April 27th, 2023 07:00
cloned savesets are not inheriting retention lock option between datadomains
Hello
we have retenton lock enbeld on different wokflows in a datadomain and i can see that the data is locked as the exapmle below :
mtree retention-lock report generate retention-details mtree /data/col1/emcvib50
/data/col1/emcvib50/boost_lzg/99/62/0216eae1-00000006-9a41936e-6441936e-23695000-96709656 governance 2096 Mon Jul 17 23:59:59 2023
/data/col1/emcvib50/boost_lzg/99/62/e463699f-00000006-79482d04-64482d04-338a5000-96709656 governance 2096 Sat Jul 22 23:59:59 2023
/data/col1/emcvib50/boost_lzg/99/52/notes/15f61348-00000006-74419670-64419670-238f5000-96709656 governance 3172 Mon Jul 17 23:59:59 2023
/data/col1/emcvib50/boost_lzg/99/52/15f61348-00000006-74419670-64419670-238f5000-96709656 governance 2096 Mon Jul 17 23:59:59 2023
/data/col1/emcvib50/boost_lzg/99/82/notes/4c984835-00000006-9446d777-6446d777-2e6f5000-96709656 governance 3580 Mon May 15 23:59:59 2023
/data/col1/emcvib50/boost_lzg/99/82/4c984835-00000006-9446d777-6446d777-2e6f5000-96709656 governance 12488 Mon May 15 23:59:59 2023
This data (from different workflows with different retention and retention lock periods ) is replicated to a destination datadomain via a seperate workflow (networker based ) .
Report from clone destination datadomain :
mtree retention-lock report generate retention-details mtrees /data/col1/emcvib50
Report generated on: Thu Apr 27 16:07:24 2023
Report for mtree: /data/col1/emcvib50
File Path Mode Size(Bytes) Expiration Date
Total files: 0
Please check the screenshot below :
How can i ensure the cloned save sets to be cloned with retention lock enabled (each with its specefic retention lock perioed)
How can i solve this issue ?
barry_beckers
393 Posts
0
May 4th, 2023 13:00
What is the current NW version you are using? In case newer versions might add that functionality? But haven't yet seen nor found a documentation that even states the limitation as mentioned in your pop-up?
what is now set? only to keep the retention the same as the original backups, while having retention lock (RL) disabled? As I assume it would set and use RL when you would not select that option to keep retention the same?
So that does work I assume, even though it is not what you would want as you don't want the same RL time applied to all data to be cloned?
You can setup multiple workflows, each using its own selection of savesets to clone applying the required RL time.
I however don't like needing to change/update/alter the selection query whenever new backups are to be taken into account. Wrg to cloning we switched towards pool based cloning. Anything in a pool would be cloned. Data not needing to be cloned, would be located in another pool. So regardless of what you throw into the pool that requires all data in it to be cloned, hence the clone query selection only states the pool, not workflows, clients, actions or whatever. Only the pool.
I don't know your environment but as datadomain would make it easy to create more devices and pools, you could have a pool based on the RL time, for example RLoneMonth:. Then you could have one clone workflow picking up all data from that pool RLoneMonth and apply one month RL to all that data.
I'll give you that it seems less flexible wrg to cloning to use RL as with backup one can have a retention that differs from the RL time. For example having a backup with 2 weeks retention, but having 1 week RL applied to it. You would want a similar option also wrg to cloning RL data, but that seems not (yet?) possible. Something to keep in mind ourselves if we also want to clone RL data, as now with cloning we often use to keep retention the same, or when it is supposed to be different it will be neatly applied to all data from the source pool, not using different retentions.