answering my own question..
After a period of time, maybe a day or so later, OSSV created the necessary snapvault relationship. Just figured it would be faster.
The 2nd question, I am giong to setup at least 2 jobs. I think the load on the VM's is high, but not pegged like the initial backup. Seems to be ok so far.
steve klise wrote:
Current setup: Windows 2003 clients with OSSV agent 2.6.1 and host agent 2.7: V31xx series Filer all licenses needed
Doing some testing with OSSV. I have the policy backup from primary to backup and keep for 30 days via Snapvault... I then snapmirror the volume over to a FAS3170. Pretty basic stuff.
Question 1: I backup the guest. It takes about 1 hour, and PEGS the CPU of all VM's tested so far. I am not backing up the vmdk option, just the file system walk. No biggie to be honest. Here is the kicker. If I add a hard drive after I have done my initial backup/basline, the protection manager does not create a new SV relationship and protect the new resouce. I then go into NMC, Host tab, OSSV, select my test host, click ok the paths tab at the bottom, and it see the new drive, and SHOWS IT AS PROTECTED. Wrong!! I take a backup to see if a relationship is created, but is not. Very bad design. I would expect to see the resouce as unprotected, or give me some sort of alert. Maybe I am wrong. Am I missing something here?
I legacy backup client would automatically pick up the new drive. Maybe I need to check something that is not obvious.
Question 2: I have about 80 windows servers to backup. The thought was to put all the clients in 1 volume. I am expecting around 1 to 1.5TB of data. Maybe 30 of them will be VM's. I am concerned that although the 1st backup is the most intensive, will this impact if I kick off 30 VM's and the CPU's hit the roof. Not good I would guess, but anyone have any thoughts, opinions, I would love them. So far I have ~ 10 windows boxes. Seeing 25% dedupe. Love it. Sorry for being so verbose.
Any help is appreciated.