I added the VOLUMES=auto:detect option, but that didn't help
The errors about failed to get host instances are old errors and not applicable anymore, and i am able to ping the xen-gda01 server from the agent host.
When i modify the configuration and change the IP addresses to the hostname the following errors show up in the logging:
[2014-04-30 07:28:15,919] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:08 2014) Performing discover operation in xen plug-in
[2014-04-30 07:28:15,919] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:08 2014) Creating executor for the filer na-gda00-xen
[2014-04-30 07:28:15,919] DEBUG: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:08 2014) Parsing NTAP_USERS - filer: na-gda00-xen user: scfadmin
[2014-04-30 07:28:15,919] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:12 2014) Creating executor for the filer na-mdt00-sv-gda
[2014-04-30 07:28:15,919] DEBUG: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:12 2014) Parsing NTAP_USERS - filer: na-mdt00-sv-gda user: scfadmin
[2014-04-30 07:28:15,920] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) Creating executor for the filer na-gda00-xen.its.centric.lan
[2014-04-30 07:28:15,920] DEBUG: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) Parsing NTAP_USERS - filer: na-gda00-xen.its.centric.lan user: scfadmin
[2014-04-30 07:28:15,920] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) Performing volume discover operation for HOST : xen-gda01
[2014-04-30 07:28:15,920] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) Creating XEN RPC session on host : xen-gda01
[2014-04-30 07:28:15,920] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) Getting the host instance and record information from host xen-gda01
[2014-04-30 07:28:15,920] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) Found host with address 10.15.3.10
[2014-04-30 07:28:15,920] INFO: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) Found host with address 10.15.3.11
[2014-04-30 07:28:15,920] ERROR: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) [xen-00003] Failed to get host instance with address xen-gda01
[2014-04-30 07:28:15,921] ERROR: [ap-gda01-nascf.its.centric.lan:9090 (4.1.1.1)] (Wed Apr 30 07:28:13 2014) [xen-00055] Volume discover operation failed for the host : xen-gda01
[2014-04-30 07:28:15,921] ERROR: [ap-gda01-nascf.its.centric.lan:9090(4.1.1.1)] SCF-00028: Auto Discovery for plug-in [xen] failed with error [validation failed] and exit code [1], Exiting!
[2014-04-30 07:28:15,924] DEBUG: Workflow : backup_OnFailure started with workflow id : 1022
Even though the manual states that plink.exe is used in Fiber environments i installed it in C:\windows\system32 (so it's in the path), but that also didn't change anything.
For Fibre Channel in a Storage Area Network (SAN) environment, the plink.exe tool must be
installed on a host where the Snap Creator agent is installed, and the plink.exe path must be
added to the system environment variable