agent and storage node on same machine
I have the Agent for ESX(i) for Windows installed on a windows system. Testing how to do LAN Free backups. I also have a Storage node on the same machine. It seems this combination is causing problems trying to access the storage node and I'm not sure why. When I go to take a look at a vault on that node, it just sits there spinning
Anyone else having issues with this setup? Should it even be done?

- Anmelden, um Kommentare verfassen zu können

hmm, bummer. I've had problems with personal vaults. But maybe if I store the data to the local machine instead of a network share, that may go away. Also, that means that to do LAN Free, I can't use deduplication then (should I choose to do so) as that's a feature on a storage node.
So, If I want to do it a different way, I could set up the ESX Agent (Virtual Appliance) on an ESX Server and backup from one iSCSI Device (our main storage where the VMs are located) to another iSCSI Storage (the backup servers). But my understanding of that is there is no cataloguing capability when you do things that way.
- Anmelden, um Kommentare verfassen zu können

Do you add the Agent for ESX(i) for Windows to the AMS? I'm wondering if that's why my AMS suddenly can't see the storage nodes and access the vaults I currently have.
- Anmelden, um Kommentare verfassen zu können

Hello Carl Constantine,
Thank you for your reply. I am happy to to answer your additional questions.
While using personal vault there is no deduplication available. This feature needs a centralized managed vault and an Acronis Storage Node.
When using the virtual appliance for backing up, you can do this in the way you described. The catalog data are also available when using the virtual appliance.
In order to back up the virtual machines, you need to add the Agent for ESX(i) for Windows or the Virtual Appliance to the Acronis Management Server. To use a personal vault with the Agent for ESX(i) for Windows, you need to connect directly to this agent, not to the Acronis Management Server.
The Acronis Management Server component can have access to centralized vaults only. It does not see any personal vault.
If there is anything else, we can do for you, please let me know.
Thank you.
- Anmelden, um Kommentare verfassen zu können

So if I create a personal vault(s) on the agent machine, does that not mean I have to create the backup plan on those machines also as you mentioned the AMS will not see the personal vaults.
- Anmelden, um Kommentare verfassen zu können

PS: The information about the ESX(i) Agent for windows and using personal vaults instead of storage nodes, etc that you mention here is NOT in any documentation at all. A very cursory overview of things, no detail. That needs to be improved.
- Anmelden, um Kommentare verfassen zu können

Hello Carl Constantine,
Thank you for your quick reply.
You are right. I will forward your comments to our management team.
When using this configuration, you need to create the backup plan on the local Agent, not in Acronis Management Server.
If there is anything else, we can do for you, please let me know.
Thank you.
- Anmelden, um Kommentare verfassen zu können

One last thing along this same thread. So I did a test of LAN Free backups with the ESX(i) Agent for windows on a Windows 2008 Server box which has a direct connection to our storage. I did configure the agent to see our vSphere server. I then created a backup plan to backup the virtual machine that we have on iSCSI Storage. It backed up successfully, and seemed quite fast (though it was just doing one machine, etc etc).
My question relates to the email I received upon successful backup which is below. I'm not sure what a couple of the errors mean:
-- VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = -2146885628
-- VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
also, why is detecting Grub 2 an issue when backing up a VM This way vs the other way we do it where it seems to work fine?
--- email message below ---
1 Information 04/12/2012 11:28:54 AM Command 'Backing up' is running.
2 Information 04/12/2012 11:28:55 AM Backing up VM 'vm://host-97722/420b4d12-2355-c6e2-0b7b-8cd472d7aba6?type%3dvmwesx'.
3 Information 04/12/2012 11:29:13 AM Creating snapshot 'Tue Dec 04 11:29:04 2012
'...
4 Information 04/12/2012 11:29:16 AM Loading virtual machine 'vm://host-97722/420b4d12-2355-c6e2-0b7b-8cd472d7aba6?type%3dvmwesx' into the disk subsystem.
5 Information 04/12/2012 11:29:17 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = -2146885628
6 Information 04/12/2012 11:29:17 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = -2146885628
7 Information 04/12/2012 11:29:17 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = 0
8 Information 04/12/2012 11:29:17 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
9 Information 04/12/2012 11:29:17 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
10 Information 04/12/2012 11:29:17 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
11 Information 04/12/2012 11:29:18 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = -2146885628
12 Information 04/12/2012 11:29:18 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = -2146885628
13 Information 04/12/2012 11:29:18 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = 0
14 Information 04/12/2012 11:29:18 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
15 Information 04/12/2012 11:29:18 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
16 Information 04/12/2012 11:29:18 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
17 Information 04/12/2012 11:29:19 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = -2146885628
18 Information 04/12/2012 11:29:19 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = -2146885628
19 Information 04/12/2012 11:29:19 AM VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = 0
20 Information 04/12/2012 11:29:19 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
21 Information 04/12/2012 11:29:19 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
22 Information 04/12/2012 11:29:19 AM VMware_VDDK: SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
23 Information 04/12/2012 11:29:20 AM Analyzing partition '1-0'...
24 Information 04/12/2012 11:29:20 AM Analyzing partition '1-1'...
25 Information 04/12/2012 11:29:20 AM Analyzing partition 'C:'...
26 Information 04/12/2012 11:29:20 AM Failed to detect GRUB loader.
Additional info:
--------------------
Error code: 7
Module: 57
LineInfo: 5186ab5c3563a7e0
Fields: $module : disk_bundle_vs
Message: Failed to detect GRUB loader.
--------------------
Error code: 7
Module: 57
LineInfo: 4243b2625e25b47f
Fields: $module : disk_bundle_vs
Message: Failed to process GRUB 2 on disk '\comp_emu(vm://host-97722/420b4d12-2355-c6e2-0b7b-8cd472d7aba6?type%3dvmwesx)\hd_emu(1)'.
--------------------
Error code: 7
Module: 57
LineInfo: 4243b2625e25b47b
Fields: $module : disk_bundle_vs
Message: The mode of the detected GRUB 2 loader is unsupported.
--------------------
27 Information 04/12/2012 11:29:20 AM Failed to detect GRUB loader.
Additional info:
--------------------
Error code: 7
Module: 57
LineInfo: 5186ab5c3563a7e0
Fields: $module : disk_bundle_vs
Message: Failed to detect GRUB loader.
--------------------
Error code: 7
Module: 57
LineInfo: 4243b2625e25b47f
Fields: $module : disk_bundle_vs
Message: Failed to process GRUB 2 on disk '\comp_emu(vm://host-97722/420b4d12-2355-c6e2-0b7b-8cd472d7aba6?type%3dvmwesx)\hd_emu(1)'.
--------------------
Error code: 7
Module: 57
LineInfo: 4243b2625e25b47b
Fields: $module : disk_bundle_vs
Message: The mode of the detected GRUB 2 loader is unsupported.
--------------------
28 Information 04/12/2012 11:29:21 AM Pending operation 151 started: 'Creating partition image'.
29 Information 04/12/2012 11:29:21 AM Pending operation 151 started: 'Creating partition image'.
30 Information 04/12/2012 11:29:21 AM Create Full Backup
From: Disk '1'
To file: "file:E:\offsite\iSCSITest\vmwesx_storage2_2012_12_04_11_29_01_231D.TIB"
Compression: Normal
Exclude: Files matching mask
Match criterion: *\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752}; ...
Description:
"storage2"
31 Information 04/12/2012 11:32:12 AM Pending operation 148 started: 'Saving partition structure'.
32 Information 04/12/2012 11:32:12 AM Remove snapshot (snapshot-100423).
33 Information 04/12/2012 11:32:22 AM Command 'Backing up' has completed successfully.
34 Information 04/12/2012 11:32:25 AM Command 'Replicating backups/cleaning up archives (1st location)' is running.
35 Information 04/12/2012 11:32:26 AM Command 'Replicating backups/cleaning up archives (1st location)' has completed successfully.
Task 'Monthly backup' has succeeded on machine 'somemachine.somewhere.com'.
--- end email message ---
Help is muchly appreciated.
I did take a look at the backup and the catelog and everything seems fine, but errors concern me when I think they shouldn't be there.
Thanks in advance.
Carl
- Anmelden, um Kommentare verfassen zu können

Maybe on other machines it doesn't detect some sequence of bytes that makes it think that GRUB 2 should be there. But once it thinks it should, it throws an error if it's not there. What OS is inside this VM ?
"SSLVerifyIsEnabled: failed to open the product registry key" seems to be not Acronis-specific error. I didn't bother to search more, but there might be some solutions.
- Anmelden, um Kommentare verfassen zu können

Hello Carl Constantine,
Thank you for your reply.
I want to thank dev-anon for supporting you.
The warning: VMware_VDDK: SSLVerifyIsEnabled: is an VMware error that belongs to the relation of vCenter and ESX(i) server itself. I recommend contacting VMware Support solving this message.
Let me know if you need additional help please.
Thank you.
- Anmelden, um Kommentare verfassen zu können

@Dev-anon: It is Linux VM that's being backed up in this test, so Grub 2 is and should be there.
- Anmelden, um Kommentare verfassen zu können

Hi,
i'm having this issue how did yo fix it ?
Thanks
VMware_VDDK: SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = 0
- Anmelden, um Kommentare verfassen zu können

Sorry to bump this up but were you able to find a work around here instead Goksenin?
- Anmelden, um Kommentare verfassen zu können

It is fixed one year ago. Please, update to the latest build.
- Anmelden, um Kommentare verfassen zu können