checkpoint for new shares

Could you explain what your intention is for these checkpoints?  Probably just me, but I am not understanding why you would consider: "create a checkpoint when there's no information populated".  Remember these are points-in-time that you can use to restore a filesystem, individual files, or use in replication (nas_copy) sessions for delta purposes.  But yeah, checkpoints to preserve that PIT when blocks are reused or filesystems with dedupe enabled use SavVol.

Chris,

we had a couple of discussions here regarding strategies of migrating data from a windows box to a file systems with existing checkpoints and dedupe or enabling dedupe on existing file systems with checkpints and how dedupe will affect SavVol utilization.

Chris,

The reason i termed it  "create a checkpoint when there's no information populated"  is because its a new share and there 'll be files in place soon. So just wanted to make sure whether i can configure the checkpoints prior to this   and this creation  would not take up the SavVolume space as soon as files are populated.It 'll be set to backed up daily .And these CKPT will be backed up by NDMP.

I 'll be keeping HWM 90% ..so 20% of celerra FS will be for the SavVol ,moreover its auto extendable  ,so should not create a problem.This share will be used as NAS online library..

Thanks for your suggestion.

checkpoints are per file system and not per share

it is best-practice to configure checkpoints after the data migration

whether or not copying files to a checkpointed file system is using savvol space depends on the age and free space of the

In any case proper planning and sizing of savols would be a good idea