By my experience about snapcreator, I always install scServer and scAgent in difference server. if the application is at same server with scSever, scAgent is unnecessary. only scServer is OK. am I right?
When I try to deploy a VM + Application consistent mode, ( the application MaxDB is in a VM, I also install scServer in same server), I was request twice times to enter Agent.
the first time is for VC (I guess, because it's before enter application setting). I could skip it. but 2nd time, it said the Agent IP is required.
then I have to re-install the SC to include the Agent. but unfortunately the scAgent service could not be startup normally. (how to troubleshoot? I did not find any logs except windows event). I plan to manually remove the Agent setting from the conf file. Does it make-sense?
Did I misunderstand anything? how should I use the configuration: maxdb_restore? It will be called by Q81 or I should directly use it to do restore? when I try to use the configuration maxdb_restore to do restore operation. but it reported "unable retrieve snapshot list".
Yes. I tested master config, it will give a prompt volume restore or SFSR. because my scenario is to use dedicate volume/lun/datastore for this VM. so master config should work too.
I did not test maxdb_restore yet. according my testing before, to use VIBE plug to do single VM restore for SAN will trigger a VMware copy file operation, it's a little slow but safe for shared datastore. I will test when free and reply you.
BTW, To use VIBE plug to restore a VM at VMFS datastore will do
1) clone a lun
2) ESX connect the cloned lun as datastore
3) VC start a copy file to copy related file from cloned datastore to real datastore.
I found at least during the file copying, even the original vmdk is thin-provision, but it will still occupy claimed size capacity. so my restore is failed because real datastore has no enough space. is it make-sense? any advice and idea about that?