UNSOLVED
R
RogerLBenson
1 Rookie
•
10 Posts
0
853
September 4th, 2009 06:00
Replicator & Checkpoint Savvol
My experience has been that there is one savvol per filesystem and both SnapSure & Replicator use it. Has this changed? I see options (which may have been there all along) with fs_ckpt and fs_replicate to limit the savvol's size. If I specify a limit of 10GB for Snapsure and 10GB for Replicator (v2 for argument's sake), does this create a single 20GB savvol or are they competing for the same space.
I am hoping for a 20GB savvol with partitioned space; 10 for SnapSure and 10 for repv2.
I am hoping for a 20GB savvol with partitioned space; 10 for SnapSure and 10 for repv2.
Rainer_EMC
6 Operator
•
8645 Posts
142
0
Posted September 4th, 2009 08:00
no - it doesnt matter
RepV2 uses regular checkpoints that share the same savvol as user-created checkpoints
The choices where to put it have to be done when you create the *first* checkpoint are:
- specify nothing specific - then you get the default size in the same pools as the fs
- specify pool and sizes
- specify a meta - but then you dont get automatic extensionRogerLBenson
1 Rookie
•
10 Posts
142
0
Posted September 4th, 2009 08:00
Would using the savvol= option partition the space within or would it just default to the larger space?
I'm trying to predict free space utilization for a client so I can give them a ceiling on headroom needed in the storage pool. I know the max defaults to 20% of the pool space, but I'd like to fine tune it.
Peter_EMC
674 Posts
142
0
Posted September 4th, 2009 07:00
The replication checkpoints are using the same savvol as the "normal" customer checkpoints (snapsure), only one savvol per FS for them