I have been using a magnetic library for some of my backups, they do seem to definitly run faster. My question is that Why doesn't it prune off the expired data? I have to go in and delete off old jobs because it keeps filling up the drive. My jobs seem to prune off fine on my tapes, it just the disk to disks that don't get removed. Is this a common thing or do I have it mis-configured?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Magnetic Library Question
- Thread starter w33mhz
- Start date
rodneysmith
MIS
If your retention is set correctly,
*Remember it adds one: (N +1) ie 1 cycle will hold 2 copies of the full
the other factor could be that you have ticked "managed disk space" which tells cv hold them for longer if you can until disk space gets to a predefined limit you have set
hope this helps
rgds rod
*Remember it adds one: (N +1) ie 1 cycle will hold 2 copies of the full
the other factor could be that you have ticked "managed disk space" which tells cv hold them for longer if you can until disk space gets to a predefined limit you have set
hope this helps
rgds rod
are you also doing auxilliary copies with the read copy being from disk?
If so then the data will stay on the disk until you have aux copied the data...so if you have a 12 month retention on an aux copy that is configured to read from the copy on disk then it will stay there for 12 months
Always better to have your shortest retention reading from disk copy & then create other aux copies with longer retention that read from a tape copy.
Birky
CommVault Certified Engineer
If so then the data will stay on the disk until you have aux copied the data...so if you have a 12 month retention on an aux copy that is configured to read from the copy on disk then it will stay there for 12 months
Always better to have your shortest retention reading from disk copy & then create other aux copies with longer retention that read from a tape copy.
Birky
CommVault Certified Engineer
Birky,
Are you saying that if I want data kept on Mag for 3 days but I have an Aux copy that copies the data from mag to tape and that Aux Copy is retained for 1 year, that the data will be kept on Mag for 1 year also?
The way I would like to do my Mag to tape setup is:
Backup - Data is backed up to Mag over night and retention on Mag is 3 days.
Copy 1 - Each morning the previous night's backup is Aux Copied to tape which will be kept in the library. Retention on this tape is 30 days.
Copy 2 - Each Saturday Copy 1 above runs, but an additional copy to tape is also made with a 120 day retention and this copy is sent offsite.
Copy 3 - First Saturday of each month Copy 1 above runs, but an additional copy tape is also made with a 365 day retention and that is sent offsite as well.
If I understand your post above, given my 1 year retention on Copy 3, if that copy is made by reading off of the Mag, the data will also be kept on the Mag for 1 year where if I build copies 2 and 3 by reading off of copy 1 then data on Mag will be kept on Mag for 30 days, which is still 27 days longer than I would like.
Is that correct?
Are you saying that if I want data kept on Mag for 3 days but I have an Aux copy that copies the data from mag to tape and that Aux Copy is retained for 1 year, that the data will be kept on Mag for 1 year also?
The way I would like to do my Mag to tape setup is:
Backup - Data is backed up to Mag over night and retention on Mag is 3 days.
Copy 1 - Each morning the previous night's backup is Aux Copied to tape which will be kept in the library. Retention on this tape is 30 days.
Copy 2 - Each Saturday Copy 1 above runs, but an additional copy to tape is also made with a 120 day retention and this copy is sent offsite.
Copy 3 - First Saturday of each month Copy 1 above runs, but an additional copy tape is also made with a 365 day retention and that is sent offsite as well.
If I understand your post above, given my 1 year retention on Copy 3, if that copy is made by reading off of the Mag, the data will also be kept on the Mag for 1 year where if I build copies 2 and 3 by reading off of copy 1 then data on Mag will be kept on Mag for 30 days, which is still 27 days longer than I would like.
Is that correct?
no....the data will stay on the maglib until it has been copied by the last auxcopy - in your case the monthly
in your situation I would setup as...
Backup 1 = Maglib - 3 days retention - copied each day to tape
Aux Copy 2 = Weekly - read from aux copy 1 above
Aux Copy 3 = Monthly - read from either aux copy 1 or 2
If aux copy 3 reads from maglib then maglib data couldn't be pruned until aux copy 3 has completed
Birky
CommVault Certified Engineer
in your situation I would setup as...
Backup 1 = Maglib - 3 days retention - copied each day to tape
Aux Copy 2 = Weekly - read from aux copy 1 above
Aux Copy 3 = Monthly - read from either aux copy 1 or 2
If aux copy 3 reads from maglib then maglib data couldn't be pruned until aux copy 3 has completed
Birky
CommVault Certified Engineer
- Status
Similar threads
- Locked
- Question