Re[2]: Collocation and Disaster Recovery
1998-06-15 03:26:00
> Author: John Dawson <jdawson AT TKG DOT COM>)
> To pick a simple, but reasonable, case, let's say you have 100 nodes
> being backed up; each node's data can fit on one tape; and the
> nightly backup traffic will fit on three tapes.
> How many tapes do you take offsite, each day, if your copy pool ...
> A) is not collocated: three (3)
> B) is collocated: one hundred (100)
How about limiting the number of scratch tapes that your copypool can have?
From what I understand, ADSM will co-locate up to the limit of the number
of scratches allowed and then go back and add extra nodes to existing
tapes.
If you limit the pool to just a few tapes more than the total capacity
required you should end up with a "few" nodes on a single tape rather than
data everywhere.
I haven't tried this though. ;) I'm in the middle of the nightmare of
creating a copypool when we already have 35 tapes full of data. :(
Carl.
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Collocation and Disaster Recovery, John Dawson
- Re: Collocation and Disaster Recovery, James SPORER
- Re: Collocation and Disaster Recovery, Kelly J. Lipp
- Re: Collocation and Disaster Recovery, Dan Curtis
- Re: Collocation and Disaster Recovery, Dan Curtis
- Re: Collocation and Disaster Recovery, John Dawson
- Re[2]: Collocation and Disaster Recovery,
Carl Makin <=
- Re[2]: Collocation and Disaster Recovery, Carl Makin
- Re: Re[2]: Collocation and Disaster Recovery, Kelly J. Lipp
- Re: Collocation and Disaster Recovery, Kelly J. Lipp
- Re: Collocation and Disaster Recovery, John Tarella
- Re: Collocation and Disaster Recovery, Dan Giles
- Re: Collocation and Disaster Recovery, James SPORER [SMTP:james.sporer
- Re[2]: Collocation and Disaster Recovery, Carl Makin [SMTP:Carl.Makin
- Re: Collocation and Disaster Recovery, John Dawson [SMTP:jdawson
|
|
|