Forcing 0 day retentions to maintain 1 copy

[theravager]

Anyone know a registry tweak to prevent having two copies of a synthentic full on mag libraries with 0 retention set.

I know the system is designed to prevent aging of the last two sythentic fulls when retention is 0 but this seems pretty stupid to have for maglibs as well. It just basically wastes twice the space for no advantage, with tapes there is small chance that the last syth could be fault and it give you a extra copy to work with.

 

[birky]

Hi

I think the 0 retention rule only applies if you also have a synchronous aux copy completed.

The idea is that you would retain only one on disk and one on tape.



Birky
CommVault Certified Engineer

 

[Frbutler]

I have exchange DB backups going to disk then aux to tape with a 0 retention time (0days, 1 cycle) but Exchange db backups are full daily so it works out.

 

[theravager]

Situation I have is i backup using sythetic fulls to disk with a copy written to tape.

Disk is utilised for fast restores and because the previous syth is used for the next weeks copy without having to read from tape.

Unfortunately the system always keeps two copies of a sites syths with the second copy aged off after the current one is done, so effectively at one point in time you have 3 syths during the actual writing of the current one. Because of the ridiculous amount of data involved this uses a ton of disk space.

There is a article on the maint-ad site that states this is coded into the system as normal behaviour and i would like to know if there is some way to disable it via a reg hack or something.