BE 2012 and Hyper-V backup best practices
I am having issues, more into how best to do it... Here's how my environment is setup:
- I have 2 sites, one primary and the other secondary and ofcourse for fail over
- The site hosts a hyper-v environment
- The hardware comprises of IBM HS22V blades as hosts and the VM's boot from a V7000 storage device (both sites)
- The VM's are distributed among the blade farm
- OS - 2008 R2 Data centre (VM hosts), 2008 Enterprise R2 for the VM's
In this environment hosts for the following VM's;
- Exchange 2010 DAG
- SQL 2008 cluster
- System center 2012 with VMM, SCOM, SCCM
- File and Print
- Forefront threat manageent gateway
- Symantec (BE2012, EV10, SEP 12)
...all totalling 60 servers. Using BE2012, what will be the best backup method to use...? I have all Symantec BE agents available; hyper-v, win servers, apps, dedup, etc. I am backing up the into free space from the same V7000 where im hosting the VM's...thats what the client wanted.
- Im told the V7000 is enterprise class storage and there are very little or no performance issues into booting from and backing up into the device...how true? with my little knowledge, even the smallest read write will make a difference
- For now i am backing up the DAG only (but will be adding other servers soon), which spans a whooping 1.6TB. Without using dedup option, the backup takes welll over 48hrs...is this normal? Thought the B2D would be quicker...
- The dedup is now on day 3 and the size is slightly above 1.45TB, thought it would be smaller with a bit of compression
- I have heard of backing up CSV's and also the VSS option. Are they likely to add any value in my backup, in terms of speed, recoverability, space efficiency, etc
My solution is to have the best backups that would increase levels of recoverability.
Any advise is highly appreciated