Unsolved
This post is more than 5 years old
1 Rookie
•
116 Posts
0
1825
March 10th, 2016 06:00
disable data/mediadb/index expiration
Hello,
Is there any way to completly disable all data expiration in NetWorker?
We are working on a DR process documentation and we plan to keep all backups in case of a site failover (at least for a few days/weeks).
I planned to mark datadomain volumes as 'scan needed' so the data won't be erased, but as I know the mediadb/client index entries will be removed when the expiration time arrives - so we have to scan the volumes if we want to recover. Is it true? Can we disable expiration?
Thank you in advance,
Istvan
No Events found!
bingo.1
2.4K Posts
0
March 10th, 2016 07:00
The bootstrap, which is created at least once per day contains the backup of the media db. So there is no need to rebuild each single save set/volume entry.
The 'scan needed' bit is set to make sure that you later can re-add the missing save set information (those which have been created since the last bootstrap and which media db entries have not been backed up yet).
Once you have retrieved their media db information you can then recover the file index from their appropriate backups.
AFAIK there is no option to stop save set/volume aging - the only method I can think of is to rename the nsrim binary.
StuartWhitby
45 Posts
0
March 10th, 2016 10:00
You can archive the data rather than backing it up, but I don't think this fits your needs for what you're looking to do above.
The simplest solution is to identify the savesets that you want to retain for longer than their standard retention and change the retention (and browse?) times on them.
mminfo -q "savetime>2 weeks ago" -c -r ssid
will give you a list of ssids for a specific client taken within the last 2 weeks (or identify the timeout you choose for this).
nsrmm -S <-w browsetime> -e -y
will update the and retention settings for these savesets to your choice of time in the future.
ble1
4 Operator
•
14.3K Posts
0
March 11th, 2016 00:00
You can disable by touching /nsr/mm/nsrim.prv - this file is checked by NW every 23 hours and if timestamps is older them nsrim kicks in which changes flags on ssids and based on these flags cleanup is made. By eliminating that, even if ssid passed the date, flags is not set so you have everything as it was. That would be the quickest way to disable expiration process (bare in mind that if you restart NW then it won't save you most likely - in that case changing expiration dates would be your best bet).
ble1
4 Operator
•
14.3K Posts
0
March 11th, 2016 03:00
Be aware that you must touch it every 22 hours at latest (well, 22:59:59).
oldhercules
1 Rookie
•
116 Posts
0
March 11th, 2016 03:00
Thanks for the replies.
I think the best trick is touching /nsr/mm/nsrim.prv. (retention change would take too much time because of the huge amount of the savesets).
Best regards,
Istvan
oldhercules
1 Rookie
•
116 Posts
0
March 11th, 2016 04:00
OK, thanks. This 'workaround' is to be used as an extra possibility in the design, generally ss retention should be OK - or it can be changed when there will be enough time work on it in case of a real DR situation
masonb
445 Posts
0
March 11th, 2016 11:00
All,
As nsrim runs every 23 hrs if you want to stop it running altogether its best to set up 2 jobs to run from cron to scheduled task every 12 hrs – then you don’t have to work around different times every day. Many Customers do this as a matter of course and set up another job to run the housekeeping at the same time every day during a quiet period outside of the normal backup window.
Regards
Bill Mason