Okay, so your implementation is going to depend a lot on your overall back design and strategy. Things like what backup software you are running. What time you are going to backup. How long its going to take to backup. How you want to restore and the frequency. Do you need incremental backup, whats you backup cycles and tape rotation like. Are there any specific application requirements like databases or Exchange. What level of data integrity do you need, crash consistant, file system level or application level. I think you will want to have a very good understanding and breakdown of all of this across your systems and applications to then start looking at the technologies to solve it.
If you are only interested in dumping all the data to tape, have you considered using VCB or some 3rd part tools that can work at the VMFS level (vRangerPro for example).
To do SAN snaps you need to work through how you are going to quiesce the data at the right level and sync it up on all the VMs who have data stored on that LUN. The answer to this could go as deep as how you actually configure your storage.
For some ideas one simple way to do it see the thread . This is a way of creating file system consistent snaps of the disks on a LUN so it can then be presented for backup. And remember that something will need to understand VMFS.
Sorry to rave on about the background. But how to do backup really can be a detailed thing and I would hate to just say, go and do this, without just raising the issue of it really having to fit into and be driven by the bigger picture. Most things that go wrong don't cause you to loose your job. Screwing up the backup, and hence loss of data, is one of those few that can indeed cause you to loose your job or cause a business significant costs and downtime.
Considering awarding points if this is of use
Rodos
{size:10px}{color:gray}Consider the use of the helpful or correct buttons to award points.
Blog: http://rodos.haywood.org/{color}{size}
