UNSOLVED
K
KrisJTurn1
19 Posts
0
3070
November 20th, 2012 08:00
Error Code 10007 On all VM Guest Backups
On all of our VM Guest backups we are getting Error Code 10007. Here is the copy of part of the log:
Errors and Exceptions
2012-11-19 23:45:09 avvcbimage Error <14618>: Problem logging into URL 'https://SERVERNAME:443/sdk' with user DOMAIN\svc-servicer' (Log #1)
2012-11-19 23:45:09 avvcbimage Error <9759>: createSnapshot: snapshot creation failed (Log #1)
Detail: get host by name failed in tcp_connect() 2012-11-19 23:45:09 avvcbimage Error <14618>: Problem logging into URL 'https://SERVERNAME:443/sdk' with user DOMAIN\Serviceaccount' 2012-11-19 23:45:09 avvcbimage Error <9759>: createSnapshot: snapshot creation failed 2012-11-19 23:45:09 avvcbimage Info <14696>: snapshot created:false NOMC:false ChangeBlTrackingAvail:true UsingChBl:true, FullBackup=true 2012-11-19 23:45:09 avvcbimage Info <9666>: Available transport modes are file:san:hotadd:nbdssl:nbd 2012-11-19 23:45:09 avvcbimage Info <9667>: Calling ConnectEx with servername=SERVERNAME:443 vmxspec=moref=vm-397 on port 0 snapshot() 2012-11-19 23:45:09 avvcbimage Info <9668>: virtual machine will be connected readonly 2012-11-19 23:45:09 avvcbimage Info <9669>: VixDiskLib_ConnectEx returned VIX_OK 2012-11-19 23:45:09 avvcbimage Info <9672>: Disconnected from VM 2012-11-19 23:45:09 avvcbimage Info <16038>: Final summary, cancelled/aborted 0, snapview 2, exitcode 0: success
rob_steele
1 Rookie
•
120 Posts
662
0
Posted November 20th, 2012 09:00
Kris, the seperate vcenter setup is so that you can have a hybrid of image and file based backups. Also as a best practice moving forward, I would use FQDN's for everything.
KrisJTurn1
19 Posts
662
0
Posted November 20th, 2012 09:00
Found the issue. When I added the Vcenter Client I didn't put the FQDN. I did this and now the VM Guest are backing up.
I don't like how it creates it's own (Group) Domain under the root. I would like to have all my Virtural Centers all under one managed Domain (Group).
Doh!
ionthegeek
2 Intern
•
2049 Posts
662
0
Posted November 20th, 2012 09:00
This sounds like a reasonable enhancement. I would recommend submitting a request for enhancement through PowerLink so the product managers can review it.
KrisJTurn1
19 Posts
662
0
Posted November 20th, 2012 09:00
I understand the seperate vcenter I just wish we could nest them in another group instead on the root.
/--
/---Physical Servers
/------Etc Etc
/---Workstations
/---Virtual Servers
/------Vcenter01
/-------Vcenter02
ionthegeek
2 Intern
•
2049 Posts
662
0
Posted November 20th, 2012 08:00
Assuming SERVERNAME is the vCenter server, it looks like the account being used for vCenter login does not have the required permissions to take snapshots, etc..