This post is more than 5 years old
1 Rookie
•
61 Posts
0
755
August 27th, 2008 05:00
Checkpoints for Windows Shadow Copy
Hi,
I am creating checkpoints of PFSs and have few questions regarding this.
I want to have checkpoints for 3 weeks just so we have it like windows shadow copy. I created a schedule for it to run 2 times a day for 5 days a week. I want it to keep 30 checkpoints. Everything seems to run fine so far. My questions are
1. Will it over write the first checkpoint after 30 checkpoints are created?
2. How can i disable autoextend on savvol. Do i have to limit the size for each checkpoint? I dont see the size limit in schedules but i see it in properties of each check point.
3. Is there a diffrent savvol created for each PFS
4. When i go to \\myserver\c$ i see each checkpoint as a mounted file system and it is same size as my PFS. Can someone clarify this for me.
Thanks
I am creating checkpoints of PFSs and have few questions regarding this.
I want to have checkpoints for 3 weeks just so we have it like windows shadow copy. I created a schedule for it to run 2 times a day for 5 days a week. I want it to keep 30 checkpoints. Everything seems to run fine so far. My questions are
1. Will it over write the first checkpoint after 30 checkpoints are created?
2. How can i disable autoextend on savvol. Do i have to limit the size for each checkpoint? I dont see the size limit in schedules but i see it in properties of each check point.
3. Is there a diffrent savvol created for each PFS
4. When i go to \\myserver\c$ i see each checkpoint as a mounted file system and it is same size as my PFS. Can someone clarify this for me.
Thanks
No Events found!


Rainer_EMC
6 Operator
•
8.6K Posts
0
August 27th, 2008 07:00
kind of. technically speaking it wil refresh the oldest checkpoint, which in effect is like deleting and creating a new one
depends if you are running DART 5.5 or 5.6
In 5.5 you can only disable auto-extension, in 5.6 you can also specify a max size
You can also disable auto-extend and get an alert that triggers an EMail before a savvol gets full. Then (if you are quick enough) you can extend it manually
size limit in schedules but i see it in properties of each check point.
no, there is only one savvol per file system that is shared by all checkpoints on that file system
yes
PFS. Can someone clarify this for me.
that is just the logical size. dont worry - its not taking any extra disk space besides the savvol
The way it works is that in order to be accessible a checkpoint gets mounted through a logical ckptfs and the .ckpt directories kind of link to that checkpoint mount
nandas
6 Operator
•
1.5K Posts
0
August 27th, 2008 07:00
Thanks Rainer for your excellent answers as always and hope this satisfies "technicolor" as well.
Cheers,
Sandip
Peter_EMC
674 Posts
0
August 27th, 2008 22:00
In 5.5 you can only disable auto-extension, in 5.6 you can also specify a max >>size
But be careful. If you disable autoextend on savvols, and a savvols needs extension, the older checkpoint data (and of course the corresponding checkpoints) will be lost, depending on how much space is needed.
So this needs a special monitoring ...