Hi Jerry,
I have tried my best to answer your questions below:
1. The VMware VIBE plugin is only supported on Windows through use of the SC Agent. Do I install VIBE on the vCenter server with the SC Agent?
You can do this or you can install scServer somewhere else and scAgent on virtual center, all that is required is scAgent can talk to virtual center, so even that doesnt technically need to be on virtual center system.
Requirements are a windows server that can access virtual center
2. Should I use SMVI to backup the VMs and use Snap Creator to backup the DBs separately (I would prefer to have a coordinated quiesced VM and DB)?
I would keep it spearate if possible and use SMVI for VMs and SC for DBs. Coordinating certainly adds a lot of complexity however it is possible. I would only coordinate however if DB is not installed in RDMs or NFS.
In this case you have two options:
1) Use SMVI and pre/post scripts to call SC to do quiesce/unquiesce of DB
2) Use SC VIBE plugin and DB2 plugin. This requires creating a VM + App consistent backup. I would use GUI wizzard. Make sure you enable SC_AGENT_WATCHDOG=Y it isnt set by default you need to edit config file manually (will be default in 3.5). What SC does is build 4 configs.
You get 2 configs to do quiesce/unquiesce of VMware and DB2
You get a master config which runs the two plugin configs and takes snapshots
You get a restore config for restoring the VM
Regards,
Keith
3. Is the VIBE plugin required? When creating the configuration for the profile selecting the 'VMware vSphere' plugin its not clear how it interacts with VIBE during the initial configuration, was not sure if it is absolutely required.
The VIBE plugin is built into SC so if in SC you choose VMware then you are using VIBE plugin. Also make sure you are using SC 3.4.0 NOT 3.4p1 (there is a bug introduced in 3.4p1 which breaks vibe). A 3.4p2 release will be out in another week so you can use that or 3.4.0.
4. I also get the following error during the initial configuration: [gui-0022] No Datastores found!
- was not sure if this was due to the fact I have not done anything with VIBE yet as I was not sure where I should install VIBE given my configuration...
SC 3.4.0 has a bug that can cause this. If you have two datacenters in vcenter and one datacenter has no datastores. Could that be case? If so fix is coming in 3.4p2