B&R10 11345 Virtual Edition, ESX Agent Bug
I believe I have found a bug, unsure if it is known or unknown. I have an VMWare ESX enviroment. I configured a server within the virtual environment to be my Acronis AMS and ALS combo server. I backed up and restored that server to external hardware that I dedicated to Acronis backups. After I restored the server (see post 7967: B&R10 11345, Restore VM to Physical), I went into the console to look at the virtual servers. It showed the 'physical' server (esx host) as offline. So I just removed the server and tried to add it back. I type in the host IP to connect and I get an error that it can't connect. Very odd, that's my ESX host, it's working fine. Next I tried to deploy the esx agent from within the console. It deploys successfully and I see it in the acronis console just fine and the VM's show up. But since the acronis esx agent grabbed a DHCP address, I wanted a static, so I changed it. Now the console can't see it again. Anything I tried to get it to see the agent didn't work, refresh, syncronize, add it (physical machine), etc.- nothing. Importing the ovf file and try to connect didn't work either, still errors with 'can't connect' message. If I remove the static address and change it back to the DHCP is was originally given, it sees it again. This tells me that agent reboots or temporary network interruptions won't (or shouldn't) cause any harm.
My workaround:
Have the VMWare ESX console open. Deploy the esx agent from within the Acronis console. Once the agent is deployed and starting up, I stopped the 'power on' process within the VMWare console. I edit the settings of the esx agent in VMWare telling the agent to NOT connect to the network on power on. Then I power it on, change the IP address to a static address, and shut it down. Once off, I edit the agent VM settings (back to the original settings) to connect to the network on power on. Last, 'power on' the ESX agent, it talks with the AMS\ALS server I have (that is external to the virtual environment) and all seems well.
I'm not sure if this is specific to me or why, but given the fact that the agent loses communication when the IP address changes, maybe Acronis should have the agent settings configurable for the deployment process, because having it be automatically set to DHCP can be an issue. Especially if the agent is rebooted and grabs a new address.
I hope this helps someone.
jeff
I'm not sure how any of your request above helps you.
All of my VM's are servers, and thus, have static IP addresses - and yes, I can ping them just fine - otherwise, my network would not run properly and I would be out of a job. The agent successfully pinged as well, whether it was static or dynamic, currently static. No disrespect intended, but I think you completely misunderstood my post. Maybe the developers need to try to duplicate what I explained above. Also, I'm not sure how a screenshot of the agent settings helps you, it's basic stuff, but it's attached in 2 files as I had to scroll down in the VM console so you could see everything.
I look forward to hear about your findings.
Jeff
HI I am having the same issue as you. Have you reached any resolution?
I have not heard anything and probably won't for a while. While the product does a descent job, support can be very weak. Try the workaround I listed above.
bump
Please read the manual carefully before writing to the forum.
1. "Physical machines" group of the AMS is the place where all _Acronis_Agents_ are placed.
2. "Acronis Agent" is the program that actually makes backups of physical or virtual machines. It is installed to the appropriate platform - physical or virtual.
3. "Acronis Agent" can be: a) Windows or Linux Agents, installed on physical or virtual PC; b) ESX(i) Virtual Appliance (VA), installed to the ESX(i); c) Hyper-V add-on to the Windows Agent, installed to the Hyper-V platform.
4. When VA is started first you are asked for: a) Login and password (you must define them yourself) that will be used to controll VA (Acronis Agent placed in VA); b) Login and password of ESX(i) or vCenter, controlling that ESX(i).
5. To controll VA from AMS you need to have it in "Physical machines" group. Yes, VA must be added here, _not_ ESX! VA is treated as _physical_machine_ in this context.
6. If you don't want to use DHCP for VA you can manully change IP to the desired in VA, remove "old" VA from AMS and add the VA using the new IP and credentials you've set in "phase 4, a)"
That's all.
Steven, you sound very arrogant and your post has nothing to do with my issue. I've been using Acronis for some time now and it is a bug as I mentioned. I know and understand everything you posted, and again, it has no relevance to the bug.
To make it more clear for you, when the agent is deployed from the console, it is automatically started and communicating with the AMS with the DHCP address it is given. IF YOU CHANGE IT TO A STATIC ADDRESS IT NO LONGER COMMUNICATES WITH AMS DESPITE ANY ATTEMPTS TO RECTIFY THE ISSUE. So in order to fix that I had to perform the workaround I stated earlier.
"Please read the manual carefully before writing to the forum." - and how about you "Please read the post before responding inappropriately."
That's all.
Be calm, Jeff! I just try to help.
You may assume you are right and i am wrong, ok.
But anyway please try this solution:
Please change IPs to yours.
I appreciate the help, but I still don't think you understand. What I'm telling you is, I've done that. And in my "workaround" in the first post, I say how to fix it.
When I use the "deploy esx agent" option in AMS, it adds the agent, which is a Linux virtual machine, and powers it on. Once powered on, the agent communicates with AMS, if I try to change the IP address it breaks. That's why in my workaround, I have to stop the ESX agent from starting and talking with the AMS. Then I make my changes to the IP address and, THEN, power it on. Then it talks to the AMS with the IP address I gave it and it's ok.
I'm very familiar with Acronis, and trust me, it's a bug - at least for me, and I'm doing things by the book.
Hello Jeff Yates,
Thank you for posting here. I would also like to assist you with this as well, as I mentioned in my other post.
Would you be kind to clarify 2 things please:
1. You wrote - "since the acronis esx agent grabbed a DHCP address, I wanted a static, so I changed it" - please clarify that you changed the IP address both in virtual machine options and in Agent options
2. "Now the console can't see it again" - please clarify if you tried to re-add the ESX agent to AMS or connect to the ESX Agent directly?
I would really appreciate if you could respond, this way we will be able to determine if this is an issue with our software.
Thank you very much for your patience and your assistance.
#1) Yes. The only place to change the IP address is under Agent Options - see attached pic. The 10.10.1.15 address is my VMWare Host server, the 10.10.1.4 is the Acronis ESX Agent that gets deployed. Originally, the 10.10.1.4 address was DHCP 10.10.1.X. After the deployment, I changed it to 10.10.1.4, but since the AMS already saw it as 10.10.1.X, any attempts to get AMS to "see it" as 10.10.1.4 failed.
So #2) = Yes. I tried to connect directly, but it showed offline, tried synchronize, etc...Nothing worked. The second pic shows it (now working from the workaround). Under Virtual Machines, what now shows (correctly) as 10.10.1.4 would show as 10.10.1.X(dhcp) and would not change even though I changed it on the agent.
I see you don't understand me, so I'll try to clarify my point of view.
Please read carefully and ask what you understood and what is not clear.
1. Acronis ESX Agent is deployed to ESX as Virtual Aplliance (VA). To understand what is VA one can read http://en.wikipedia.org/wiki/Virtual_appliance
2. Acronis ESX Agent can be remotely managed either directly, using Acronis Management Console (AMC) and making direct connection to Agent, or in centralized manner, by adding Acronis ESX Agent to Acronis Management Server (AMS).
3. Acronis ESX Agent can be deployed to ESX either manually, using .ovf import from ESX Client or automatically from AMS.
4. When one makes automatic deploy VA is transferred to ESX, starts here and connects to AMS. So Acronis ESX Agent appears in AMS and you can backup Virtual Machines from ESX.
5. Automatic deploy always uses DHCP to take IP address for Acronis ESX Agent.
6. If one wants to have static IP address for Acronis ESX Agent one must set it manually derectly on Acronis ESX Agent using ESX Client to connect to VA. I see you can change IP address youself.
7. After you've changed IP on Acronis ESX Agent it disappers from AMS, because AMS can't indentify Acronis ESX Agent using "old" DHCP address (you've just changed it) and doesn't know how to find new IP.
8. That is the case you had. But you went wrong way from here. Why?
9. You mixed up VMware ESX and Acronis Virtual Appliance, hosting Acronis ESX Agent. That "something" named "10.10.1.15-VA" on your picture and situated in "All physical machines" group of AMS is NOT "ESX VMware HOST Server" as you depicted. It is Acronis Virtual Appliance, hosting Acronis ESX Agent. Yes, it is what i've said and nothing else. "10.10.1.15" part of the name is IP of VMware ESX Server which hosts VA, and "VA" letters mean "Virtual Appliance". IP of the ESX Server in the name of Acronis ESX Agent doesn't mean it is ESX Server itself. If you see "-VA" ending in the name - it is VA, hosting Acronis ESX Agent. Is it clear?
10. Moreover, that "something" named "10.10.1.4" in "Virtual machines" group of AMS is NOT "Acronis ESX Appliance (agent)" as you depicted in the same screenshot. It is VIRTUAL Dynamic group on AMS, hosting all Virtual Machines from the ESX Server where your VA is deployed. I'll repeat - it is VIRTUAL Dynamic group, made for comfort only. You may have tens of VAs on AMS and this must help to filter the needed Virtual Machines from the concrete ESX Server. This Dynamic group is created automatically and can't be deleted or edited somewhow. It disappears automatically ofter Acronis ESX Agent is removed from AMS.
11. Now i'll tell you RIGHT way to fiz the problem we have from point 7 of this story. Yes, your way workaround too, i understand. But you must also understand that barbaric way you power of VA when it is starting can lead to internal data corruption - any modern OS, Linux or Windows can be damaged this way. So here is solution: a) delete Acronis ESX Agent entry from AMS by deleting "10.10.1.X(dhcp)-VA" from "All physical machines" group of AMS. This way you tell AMS to "forget" about Acronis ESX Agent; b) add Acronis ESX Agent using it's new IP address (10.10.1.4) to "All physical machines" group of AMS using "Credentials for connection to the agent" depicted on the first scrrenshot (you've already set them on VA using ESX Client).
12. That's all - you have WORKING Acronis ESX Agent without dangerous power-offs and playings with virtual networking on ESX.
I really believe this will make help, as i've spent plenty of time trying my best to make you understand me. Thank for reading all this stuff :)
Thank you for taking the time to respond, I appreciate it. I’ll try to go thru these one at a time so we can understand each other, and the issue, and will mark my reply with “R:”.
1. Acronis ESX Agent is deployed to ESX as Virtual Aplliance (VA). To understand what is VA one can readhttp://en.wikipedia.org/wiki/Virtual_appliance
R: I'm not sure I completely understand (but I do some) and my ESX environment consists of a Linux host server (10.10.1.15) and an iSCSI SAN.
2. Acronis ESX Agent can be remotely managed either directly, using Acronis Management Console (AMC) and making direct connection to Agent, or in centralized manner, by adding Acronis ESX Agent to Acronis Management Server (AMS).
R: I understand.
3. Acronis ESX Agent can be deployed to ESX either manually, using .ovf import from ESX Client or automatically from AMS.
R: I understand I think - this is my 10.10.1.4. In my VMWare console it shows as "AcronisESXAppliance(10.10.1.15)" listed like the other servers. I've deployed it both ways at various times in testing. If I import the .ovf, I can't get the AMS to see it at all. The only way for me to get the AMS to see it is to automatically deploy from AMS.
4. When one makes automatic deploy VA is transferred to ESX, starts here and connects to AMS. So Acronis ESX Agent appears in AMS and you can backup Virtual Machines from ESX.
R: I understand and is what I did.
5. Automatic deploy always uses DHCP to take IP address for Acronis ESX Agent.
R: I understand - at this point I want a static address.
6. If one wants to have static IP address for Acronis ESX Agent one must set it manually derectly on Acronis ESX Agent using ESX Client to connect to VA. I see you can change IP address youself.
R: I did this changing from the DHCP address to 10.10.1.4 as shown in the previous pic.
7. After you've changed IP on Acronis ESX Agent it disappers from AMS, because AMS can't indentify Acronis ESX Agent using "old" DHCP address (you've just changed it) and doesn't know how to find new IP.
R: It didn't disappear from AMS, only that it was offline or unavailable.
8. That is the case you had. But you went wrong way from here. Why?
R: Why? This is what I want to know. At this point, since AMS no longer sees the DHCP Acronis ESX agent, I try (using AMS) to connect, synchronize, etc - all fail.
9. You mixed up VMware ESX and Acronis Virtual Appliance, hosting Acronis ESX Agent. That "something" named "10.10.1.15-VA" on your picture and situated in "All physical machines" group of AMS is NOT "ESX VMware HOST Server" as you depicted. It is Acronis Virtual Appliance, hosting Acronis ESX Agent. Yes, it is what i've said and nothing else. "10.10.1.15" part of the name is IP of VMware ESX Server which hosts VA, and "VA" letters mean "Virtual Appliance". IP of the ESX Server in the name of Acronis ESX Agent doesn't mean it is ESX Server itself. If you see "-VA" ending in the name - it is VA, hosting Acronis ESX Agent. Is it clear?
R: Ok, now I understand.
10. Moreover, that "something" named "10.10.1.4" in "Virtual machines" group of AMS is NOT "Acronis ESX Appliance (agent)" as you depicted in the same screenshot. It is VIRTUAL Dynamic group on AMS, hosting all Virtual Machines from the ESX Server where your VA is deployed. I'll repeat - it is VIRTUAL Dynamic group, made for comfort only. You may have tens of VAs on AMS and this must help to filter the needed Virtual Machines from the concrete ESX Server. This Dynamic group is created automatically and can't be deleted or edited somewhow. It disappears automatically ofter Acronis ESX Agent is removed from AMS.
R: I understand and this "Virtual Dynamic Group" is named after the IP Address, 10.10.1.4 (or the DHCP address if I didn't change it)
11. Now i'll tell you RIGHT way to fiz the problem we have from point 7 of this story. Yes, your way workaround too, i understand. But you must also understand that barbaric way you power of VA when it is starting can lead to internal data corruption - any modern OS, Linux or Windows can be damaged this way. So here is solution: a) delete Acronis ESX Agent entry from AMS by deleting "10.10.1.X(dhcp)-VA" from "All physical machines" group of AMS. This way you tell AMS to "forget" about Acronis ESX Agent; b) add Acronis ESX Agent using it's new IP address (10.10.1.4) to "All physical machines" group of AMS using "Credentials for connection to the agent" depicted on the first scrrenshot (you've already set them on VA using ESX Client).
R: I did that, I tried your fix - that did not work. That's why I had to power off when it's starting. I understand it may cause corruption, but I had no choice.
12. That's all - you have WORKING Acronis ESX Agent without dangerous power-offs and playings with virtual networking on ESX.
Summary: We understand each other just fine, but there is a bug - at least for me - that does not allow me to do #11 or #3 (ovf import. I can import it, it just won't talk to AMS). So, there is a communication issue bug for me. My setup is a separate, physical server outside of my virtual environment that has my AMS, ALs, and Storage Node. The only way I could get this to work is to do the workaround above.
I also have another bug...see this post: http://forum.acronis.com/forum/8999
Thanks again for helping and I apologize for misunderstanding you before.
I'll response some points, missing those you've understood already. I'll mark my replies with "SA:".
1. Acronis ESX Agent is deployed to ESX as Virtual Aplliance (VA). To understand what is VA one can readhttp://en.wikipedia.org/wiki/Virtual_appliance
R: I'm not sure I completely understand (but I do some) and my ESX environment consists of a Linux host server (10.10.1.15) and an iSCSI SAN.
SA: Being concrete your 10.10.1.15 is not "Linux host server". VMware says it is ESX itself. Actually it is hidden Virtual Machine with some sort of Red Hat Linux, it is called like "Service Console" in VMware documents. So, to be clear, this IP is the IP of Servise Console - you may think it is ESX Server itself.
3. Acronis ESX Agent can be deployed to ESX either manually, using .ovf import from ESX Client or automatically from AMS.
R: I understand I think - this is my 10.10.1.4. In my VMWare console it shows as "AcronisESXAppliance(10.10.1.15)" listed like the other servers. I've deployed it both ways at various times in testing. If I import the .ovf, I can't get the AMS to see it at all. The only way for me to get the AMS to see it is to automatically deploy from AMS.
SA: When you connect to ESX Server using VMware Client, manually install VA, start it - first screen you see is where you must enter password for the "root" account. You must use these credentials to add Acronis ESX agent hosted on this VA to the "All physical machines" group of AMS, so remember these credentials. After you've set the password you need to enter IP and "root" password of ESX Server (10.10.1.15) so VA can connect to ESX Server to get the list of hosted Virtual Machines and to be able to backup\restore them. Then you must enter trial license or give the adress of License Server. After you can also change IP of VA to statica, as you've done before. Here VA is ready to be added to AMS using it's DHCP or static IP, "root" login and appropriate password you've set when VA started first. I can't believe that if you'll do al the steps i've described you won't be able to add VA to AMS or connect to it directly. I personally did this plenty of times while testing the product. If you won't mix up IP of ESX Server and IP of VA everything MUST work just fine. Else i have no idea what went wrong - take help from Customer Support team.
7. After you've changed IP on Acronis ESX Agent it disappers from AMS, because AMS can't indentify Acronis ESX Agent using "old" DHCP address (you've just changed it) and doesn't know how to find new IP.
R: It didn't disappear from AMS, only that it was offline or unavailable.
SA: I meant this actually, you understand... :)
8. That is the case you had. But you went wrong way from here. Why?
R: Why? This is what I want to know. At this point, since AMS no longer sees the DHCP Acronis ESX agent, I try (using AMS) to connect, synchronize, etc - all fail.
SA: That was rhetorical question :)
11. Now i'll tell you RIGHT way to fiz the problem we have from point 7 of this story. Yes, your way workaround too, i understand. But you must also understand that barbaric way you power of VA when it is starting can lead to internal data corruption - any modern OS, Linux or Windows can be damaged this way. So here is solution: a) delete Acronis ESX Agent entry from AMS by deleting "10.10.1.X(dhcp)-VA" from "All physical machines" group of AMS. This way you tell AMS to "forget" about Acronis ESX Agent; b) add Acronis ESX Agent using it's new IP address (10.10.1.4) to "All physical machines" group of AMS using "Credentials for connection to the agent" depicted on the first scrrenshot (you've already set them on VA using ESX Client).
R: I did that, I tried your fix - that did not work. That's why I had to power off when it's starting. I understand it may cause corruption, but I had no choice.
SA: I have no working environment now so can't test myself, but if you'll read p.3 and it doesn't help - i can't help either. This may be you problem or real bug. But i had no problems with adding VA's with static IP's to AMS myself. Contact official support.
Summary: We understand each other just fine, but there is a bug - at least for me - that does not allow me to do #11 or #3 (ovf import. I can import it, it just won't talk to AMS). So, there is a communication issue bug for me. My setup is a separate, physical server outside of my virtual environment that has my AMS, ALs, and Storage Node. The only way I could get this to work is to do the workaround above.
SA: If my info won't help try this - select VA (configured with static IP-address) on ESX Server, open it's configuration console, press Ctrl+Alt+F2. Type "ping %IP_of_your_AMS%", press "Enter". So you can understand if IP packets can go between VA and AMS. This may help support to give more solutions.
I also have another bug...see this post: http://forum.acronis.com/forum/8999
SA: Can't help here, sorry.
Thanks again for helping and I apologize for misunderstanding you before.
SA: That's OK. I help you - you help me :)
I just have to say that I experiance exactly the same problem my self.
No need to explain the problem once again, and the workaround that helps, is what Jeff is describing.
Thanks Kurt - this confirms for me it's a bug and not just my configuration.
Hello all,
Thank you very much for your posts. I would very much like to assist you with this issue.
I am sorry for the inconvenience but at the moment it is difficult to say if this is a known problem with our software. We will need additional information so that our Quality and Assurance team can reproduce it.
If you would be kind enough to gather the following logs which I wrote about in this thread as well as clarify 2 things that I asked in this thread.
I would really appreciate if you can either PM or reply to my post with the case number so that I can forward it to our Expert team.
Let me know if you have additional questions.
Thank you.
Could this be the answer/solution to the problem?
Link updated a few days ago.
http://kb.acronis.com/content/9178
Kurt Hodneland
Could this be the answer/solution to the problem?
Link updated a few days ago.
http://kb.acronis.com/content/9178Kurt Hodneland
Basically - yes, and if you look at the created date of that KB (March 9th), it is after my initial complaint. So maybe that actually investigated and found that it IS an issue\bug. It would have been nice if they would have come back and said, "Yes Jeff - we have a bug and are working to fix it.".
Hello all,
Thank you very much for your posts. I would very much like to assist you with this issue.
I am sorry for the inconvenience but at the moment it is difficult to say if this is a known problem with our software. We will need additional information so that our Quality and Assurance team can reproduce it.
If you would be kind enough to gather the following logs which I wrote about in this thread as well as clarify 2 things that I asked in this thread.
I would really appreciate if you can either PM or reply to my post with the case number so that I can forward it to our Expert team.
Let me know if you have additional questions.
Thank you.
Everything you have asked for is out there and I have also PM Yana. What you need is there...
Hello all,
Thank you very much for your comments.
The Knowledge Base article that you refer to - Acronis Backup & Recovery 10 Advanced Server Virtual Edition: Connection to Virtual Appliance Fails after the IP Address Change does talk about this issue, although it offers a different workaround. I would recommend to wait the next officially released build of Acronis Backup & Recovery 10 which is coming out soon, and in case of any issues, we can continue troubleshooting from there.
Please let me know if you have additional questions.
Thank you.
I'm on 13545 and I had exactly the same problem that Jeff has.
I had a different workaround for in-place systems. I had not realized that Acronis would allow their ESX agents grab a DHCP address and further allow the associated backup policies get messed up when the ESX agents pick up a new leased IP.
However, my method was to enter the SQL database by a local installation of SQL Server 2005 Management Studio and connecting to the database that Acronis is mapped to on local credentials wherever the database resides.
I was able to find the list of machines with AMS on it... and find where the problem is.
In SQL Management Studio, after accessing the database server,
\ACRONIS -> Databases -> acronis_cms -> Tables -> dbo.Machine -> Open Table
You'll see your discrepancies there.
Apparently the system is using the "OriginalName" column and not the "MachineAddress" column. When the IP was changed to a static IP, the "MachineAddress" column got updated, not the "OriginalName" column. The backup policies seem to be wanting to use the "OriginalName" column and not the "MachineAddress" whether it's a DNS address or not.
I updated the "OriginalName" column of all the incorrect data and all was well afterwards.
Cheerio,
Ian P.