Hi,

welcome to the forum.

Like access to normal files the access to files checkpoints isnt tracked on the Celerra - it would mean way too much work and logs.

Theoretically you could enable auditing and set audit ACLs on all files - but the sheer amount of data then in the event wouldnt be very helpfull IMHO.

If your users are primarily using SCSF (previous versions tab) you can check with Microsoft if there is some logging there on the client that can be enabled via registry.

Maybe a 3rd party product like Varonis that also looks at the network could help.

Otherwise I would suggest to ask the users.

regards

Rainer

Hi Guys,

Thank you for your help.  I could of course ask the users as suggested, I just thought it'd be easier to track it and get the actual data since user can sometimes be unreliable data sources .

I assumed there'd be a log that would track when users access a .ckpt to restore a file.  That's too bad that there isn't, it sure would be helpful in making sure my checkpoint strategy was the most useful for my users.

I think I'm going to try the inverse of my initial strategy.  I'm going to only keep a few days worth of checkpoints available to users and if users need data further back I'll pull it from my backups (I use CIFS backup via retrospect too) and then I'll be able to track how often I need to get data from backups.  If it's too frequent I can do less checkpionts per day and keep the data available to the users for a longer period.

Eventually I'll find the best middle-ground for everyone.

technically checkpoints are extra (virtual) file systems - so its possible that we keep the same stats that we do for a regular fs

I cant access a system right now - so I cant check

you can get an overview of file system ops with server_stats per file system though - I dont remember if that also prints out checkpoints

or try Celerra Monitor

Rainer

Rainer,

How would it report reading from PFS vs reading from the savVol ?

This e-mail message (including any attachments) is for the sole use of

the intended recipient(s) and may contain confidential and privileged

information. If the reader of this message is not the intended

recipient, you are hereby notified that any dissemination, distribution

or copying of this message (including any attachments) is strictly

prohibited.

If you have received this message in error, please contact

the sender by reply e-mail message and destroy all copies of the

original message (including attachments).