No, I have never seen so far such configuration and can't figure out what would made do the things like that either I believe your customer doesn't really understand purpose of pools - I mean why would they have 1 pool per day!? With setup as he has it's much better to replace tape with disk.
Anyway, are you sure that all his backups are full? I would suggest to use mminfo to inspect level and retention for savesets. If you have: client1:file_system1:full:1st_day:taken_on_Monday client1:file_system1:full:2nd_day:taken_on_Tuesday client1:file_system1:full:3rd_day:taken_on_Wednesday
then on Wed morning 1st backup should expire. It is not clear yet if your issue is with tape expiring or ssid expiring. Volume won't get eligible for recycling unless it is full. So, back to our example above, if on 1st day he wrote 135GB and tape has more space to write to - ssid will expire, but tape won't be eligible for recycling. This is expected.
I never tried this against with minutes, but it always works with savetime. mminfo can show you exact time if you expand lenght of reported field (check mminfo manual). Last backup cycle of certain ssid (first if only) will never expire by design (check nsrim manual for more).
To force expiration outside scheduled 24 hour check you can call nsrim.
Hi, Hrvoje .You´re right. with nsrim -X the database is updated (the nsrim document explain that is necessary to use cron with this command or use it manually if is scheduled a group with a period of time less than 23 hours). But this simulated file device didn´t help me to understand what happens with one costumer: - There´s one pool for each day of the week; - He uses a full backup per day schedule ( files, exchange, SQL) and wants to use one tape per day; - His tape is 100/200 GB LTO2 ( his backup uses 135GB ); - He uses a 1 day police for Browse and retention ( test purpose only, he will use in the future the 7 day or 14 day browse and retention). But after 2 days the volume is still appendable What I´m trying to do there is a way that after one or seven days the volume became eligible for recycle, NW get the tape and apply a new label configured for this pool ( e.g: from sunday.001 to sunday.002 ). This configuration works on NetWorker? Have you ever seen a configuration like that?
ble1
4 Operator
•
14.4K Posts
0
July 18th, 2006 17:00
Anyway, are you sure that all his backups are full? I would suggest to use mminfo to inspect level and retention for savesets. If you have:
client1:file_system1:full:1st_day:taken_on_Monday
client1:file_system1:full:2nd_day:taken_on_Tuesday
client1:file_system1:full:3rd_day:taken_on_Wednesday
then on Wed morning 1st backup should expire. It is not clear yet if your issue is with tape expiring or ssid expiring. Volume won't get eligible for recycling unless it is full. So, back to our example above, if on 1st day he wrote 135GB and tape has more space to write to - ssid will expire, but tape won't be eligible for recycling. This is expected.
ble1
4 Operator
•
14.4K Posts
0
July 16th, 2006 15:00
To force expiration outside scheduled 24 hour check you can call nsrim.
jonatas1
65 Posts
0
July 18th, 2006 17:00
But this simulated file device didn´t help me to understand what happens with one costumer:
- There´s one pool for each day of the week;
- He uses a full backup per day schedule ( files, exchange, SQL) and wants to use one tape per day;
- His tape is 100/200 GB LTO2 ( his backup uses 135GB );
- He uses a 1 day police for Browse and retention ( test purpose only, he will use in the future the 7 day or 14 day browse and retention).
But after 2 days the volume is still appendable
What I´m trying to do there is a way that after one or seven days the volume became eligible for recycle, NW get the tape and apply a new label configured for this pool ( e.g: from sunday.001 to sunday.002 ).
This configuration works on NetWorker? Have you ever seen a configuration like that?