incr backups with varying mgm (2nd)
2015-10-04 17:38:06
>Thanks for your response so far...
>
>I will try to explain what we want to do and what we expected from ADSM to
>do:
>May there be a file, which changes every day, so every backup will lead to
a
>new active version of that file. Although we need to hold some inactive
>versions of that file for 1 year, we do not want to hold all 365 versions
>(we do not have the storage capacity for that...).
>
>If we do backups without versioning (i.e. nolimit) for example on weekdays
>with a retention period of 7 days, at Sunday with a retention period of 30
>days and at every 28th with a retention period of 365 days we expect, that
>the different bindings of the inactive files (-> 7, 30 or 365 days ret.
>per.) will never change, independent from the varying binding of the active
>file.
>
>I hope I could figure it out a little bit...
>
>TIA for any response
>
>R. Masa
>masa.ralf AT combibloc DOT com
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- incr backups with varying mgm (2nd), Masa, Ralf
- Re: incr backups with varying mgm (2nd), Richard C. Dempsey
- Re: incr backups with varying mgm (2nd), Leo Humar
- Re: incr backups with varying mgm (2nd), Nick Cassimatis
- Re: incr backups with varying mgm (2nd), Kelly J. Lipp
- Re: incr backups with varying mgm (2nd), Allen S. Rout
- Re: incr backups with varying mgm (2nd), Steve Harris
- Re: incr backups with varying mgm (2nd), Leo Humar
- incr backups with varying mgm (2nd),
Masa , Ralf <=
- incr backups with varying mgm (2nd), ADSM : Dist Stor Manager [mailto:ADSM-L
- Re: incr backups with varying mgm (2nd), Steve Harris
|
|
|