At the University of Michigan - ITS, we currently use TSM to backup some of our volumes. TSM uses snapdiff and can either create it's own snapshots, or it can use existing ones. We're in the process of transition some of the volumes to use existing snapshots, but right now we have it creating it's own snapshots along with snapshot schedules. All of the ones created by TSM are named TSM_<something>, compared to the standard <type>.timestamp - so at least with TSM mixing them isn't a problem.
-- Mike Garrison
On Fri, Dec 13, 2013 at 10:13 AM, Ray Van Dolson rvandolson@esri.com wrote:
Greetings;
We're using CommVault and have begun making broader use of their NetApp FlexClone integrated "SnapProtect" to do backups of our VMware environments (as opposed to CommVault using VMware snapshots for taking backups).
We also have our NetApps taking two daily snapshots of most VM volumes for a quicker recovery option in some cases.
CommVault is recommending that we let it manage all snapshot creation and removal duties and not to mix what they do with NetApp's snapshot scheduling. So far, I'm not understanding why the two can't co-exist. They use different naming conventions on their snapshots, CommVault's snapshots are FlexClone snapshots rather than regular snapshots, and their method offers much less flexibility.
What do those of you who have their backup software talking to your filers for snapshot-creation do?
Thanks, Ray _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters