gommog's Posts

I decided not to try and fix this in the end as i can see this getting really indepth and beyond my knowledge of vmware replication. I unregistered the faulty appliance from vcenter following thi... See more...
I decided not to try and fix this in the end as i can see this getting really indepth and beyond my knowledge of vmware replication. I unregistered the faulty appliance from vcenter following this KB article http://pubs.vmware.com/srm-51/index.jsp?topic=%2Fcom.vmware.srm.install_config.doc%2FGUID-EA052863-034D-47EE-B513-9D1F514A6A2D.html . I then removed the other VA completely from disk. I created a new instance and rebooted the vcenter server, i've now removed all the hbr files from the replicated folders and i've recreated the jobs using the old replica disks as seeds. It seems to have done the job but it's not something i'd want to repeat and raises questions about the validity of using VR in a live environment.
Yes i've browsed through and found the extension, not sure exactly what you're after but  this shows the VA i removed: I'm not a linux user so viewing those logs was troubling but i mana... See more...
Yes i've browsed through and found the extension, not sure exactly what you're after but  this shows the VA i removed: I'm not a linux user so viewing those logs was troubling but i manage to get in, i can't see anything relating to not updating extension data but then i wouldn't know specifically what i'd be looking for. This is the contents of the hms.log login as: root Using keyboard-interactive authentication. Password: Last login: Wed Mar 20 12:25:09 2013 from czc13127hx.dca-design.com localhost:~ # cd /opt/vmware/hms/logs localhost:/opt/vmware/hms/logs # hms.log -bash: hms.log: command not found localhost:/opt/vmware/hms/logs # view hms.log 2013-03-20 07:48:55.102 ERROR jvsl.security.authorization [hms-vlsi-server-thread-69] (..security.authorization.VcPrivilegeSupplier)  | Unable to collect user's (hmsuser) privileges. com.vmware.jvsl.util.ExceptionAdapter: java.util.concurrent.ExecutionException: com.vmware.vim.binding.vim.fault.InvalidLogin: inherited from com.vmware.vim.binding.vim.fault.VimFault: inherited from com.vmware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password.         at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(BlockingFuture.java:70)         at com.vmware.jvsl.sessions.net.impl.vc.ExtensionLoginHandler.doLogin(ExtensionLoginHandler.java:36)         at com.vmware.jvsl.sessions.net.impl.vc.ImpersonatingLoginHandler.doLogin(ImpersonatingLoginHandler.java:31)         at com.vmware.jvsl.sessions.net.impl.vc.ConnectionHandlerImpl.doLogin(ConnectionHandlerImpl.java:125)         at com.vmware.jvsl.sessions.net.impl.vc.ConnectionHandlerImpl.doLogin(ConnectionHandlerImpl.java:39)         at com.vmware.jvsl.sessions.net.impl.PersistentConnection.connect(PersistentConnection.java:531)         at com.vmware.jvsl.sessions.net.impl.PersistentConnection.start(PersistentConnection.java:131)         at com.vmware.jvsl.sessions.net.impl.vc.ServerViewImpl.start(ServerViewImpl.java:76)         at com.vmware.jvsl.sessions.net.impl.vc.ServerImpl.getVcUserView(ServerImpl.java:144)         at com.vmware.jvsl.security.authorization.VcPrivilegeSupplier$VcConnector.getVcServerView(VcPrivilegeSupplier.java:297)         at com.vmware.jvsl.security.authorization.VcPrivilegeSupplier.getPrivileges(VcPrivilegeSupplier.java:97)         at com.vmware.jvsl.security.authorization.CachedPrivilegeSupplier.getPrivileges(CachedPrivilegeSupplier.java:64)         at com.vmware.hms.security.authorization.TimeEnabledPrivilegeSupplier.getPrivileges(TimeEnabledPrivilegeSupplier.java:115)         at com.vmware.jvsl.security.authorization.TicketAuthorizer$TicketPrivilegeChecker.checkPrivilege(TicketAuthorizer.java:301)         at com.vmware.jvsl.security.authorization.TicketAuthorizer.checkAuthorization(TicketAuthorizer.java:209)         at com.vmware.jvsl.security.authorization.TicketAuthorizer.authorize(TicketAuthorizer.java:146)         at com.vmware.jvsl.security.authorization.JvslActivationValidator.validate(JvslActivationValidator.java:103)         at com.vmware.vim.vmomi.server.impl.ValidationStartTask.run(ValidationStartTask.java:67)         at com.vmware.hms.util.executor.LoggerOpIdConfigurator$RunnableWithDiagnosticContext.run(LoggerOpIdConfigurator.java:133)         at com.vmware.hms.util.executor.LoggerOpIdConfigurator$2.run(LoggerOpIdConfigurator.java:100)         at com.vmware.jvsl.sessions.net.impl.TlsPreservingWrapper$2.run(TlsPreservingWrapper.java:47)         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)         at java.lang.Thread.run(Unknown Source) Caused by: com.vmware.vim.binding.vim.fault.InvalidLogin: inherited from com.vmware.vim.binding.vim.fault.VimFault:                                                                                                                   1,1           Top I can confirm that the ovfEnv.xml file has values though
Hi Martin, Thanks for the reply, i did always wonder about having 2 replication appliances but the way i read the docs seemed like i needed 2. I've got rid of the problem appliance, rebooted t... See more...
Hi Martin, Thanks for the reply, i did always wonder about having 2 replication appliances but the way i read the docs seemed like i needed 2. I've got rid of the problem appliance, rebooted the working appliance and logged out of the web client. I even went as far as rebooting the vcenter server again. I'm still seeing the error "Unexpected status code 503" if i try to configure replication for a VM though. Additionally if i check the web client there are no sites showing under replication. It seems like my ability to manage replication in any way has completely failed. If i check the service health of the vcenter server it shows a problem with VR management "Unable to retrieve health data from https://192.168.10.245:5480/service/hms/cgi/health.py" , this IP is the problem VA so for some reason it's still trying to communicate with this, is there any way to remove/reconfigure this?
I have been using vsphere replication now for a couple of months, this morning i noticed that the option for replication was not showing in the home page of the web client. I first tried to resta... See more...
I have been using vsphere replication now for a couple of months, this morning i noticed that the option for replication was not showing in the home page of the web client. I first tried to restart the vcenter server assuming this was something to do with a service not running, on reboot i still didn't see the option. We are replicating between 2 esxi 5.1 hosts both managed by the same vcenter server and have 2 replication appliances (one on each host), i rebooted both appliances. One rebooted fine but the other is asking for a root password for login, i entered the root password used during setup (this is a standard password i use for many network services) but this was not accepted. I'm now at the stage where replication is showing as an option in the web console but none of my jobs are displaying. Has anyone come across this issue before? I can't recreate the jobs as if i try to do so i get the message Unexpected status code: 503, someone please help.
Thanks Mohammed, i will live in hope for now as i'm sure they're coming in a future release.
Thanks Biliana, that's a useful tip and one i'll be keeping an eye on, what i'm really interested in though is some way to monitor the rate at which replication is taking place at any given time.... See more...
Thanks Biliana, that's a useful tip and one i'll be keeping an eye on, what i'm really interested in though is some way to monitor the rate at which replication is taking place at any given time. For instance when i start an initial full sync i can check the datastore and get a rough idea of how much data is copying across but not any decent stats. Is there anything i can do from the PowerCLI for instance?
I've recently started using vmware replication and everything seems to be working fine, the only issue i have is that i have no idea what rate replication is taking place at and although i can se... See more...
I've recently started using vmware replication and everything seems to be working fine, the only issue i have is that i have no idea what rate replication is taking place at and although i can set the RPO at 15 mins for critical VMs i have no idea what amount of data is being replicated at any one time. The only way i can test this is to copy files to a vm, stop replication and power off the vm then recover the copy. This has worked fine for smaller files but i have no idea how long this would take if i were to copy GBs of data. What i'm looking for is some way to monitor the replica to see if files have been copied across, anyone know of a way to do this?
I've recently done a comparison between Veeam, vmware replication and double-take, we wanted to upgrade to esxi 5.1 so double take was out as it's not compatible with 5.1. What i found was that V... See more...
I've recently done a comparison between Veeam, vmware replication and double-take, we wanted to upgrade to esxi 5.1 so double take was out as it's not compatible with 5.1. What i found was that Veeam had a lot of useful features, way more than VR, and was very easy to use but it uses snapshots to provide the replication function. This ultimately slowed VMs down so was a no go for us, if you don't mind taking the performance hit and you've got the environment to support it then take a look at Veeam. We'll be pushing out VR and i'm just hoping it will catch up to veeam in terms of features in the future.
I'm also trying this and finding the documentation from vmware to be very confusing to say the least. What i've found is this: 1. v5.1 of vcenter isn't supported on Win XP, it took me a while ... See more...
I'm also trying this and finding the documentation from vmware to be very confusing to say the least. What i've found is this: 1. v5.1 of vcenter isn't supported on Win XP, it took me a while to find this out although there were many mentions of not being able to do an in place upgrade on xp to v5.1. 2. You can't do a migration of vCenter between 2 differrent OSs. What i can tell from this is there is no supported route from a Windows XP vCenter server v4.x to Windows 2008 v5.x. Here's what i did to get around this: 1. Created a new Windows 2008 server instance. 2. Installed vCenter v4.x onto Windows 2008 machine. 3. Stopped the vcenter server service on both machines. 4. Backed up the VIM_VCDB database on the XP machine. 5. Removed the VIM_VCDB database on the 2008 machine. 6. Restored from the backup on the 2008 machine. 7. Shutdown the XP machine. 8. Give the new 2008 machine the same ip as the XP machine had. 9. Start the vcenter service. 10. Connect through the vSphere client and then connect to your hosts (there should be a way to copy over the SSL certificates but i couldn't find the destination on win 2008. 11. You should then be able to do an in place upgrade to v5.x. This worked for me but we only have 2 hosts and no resource pools, vapps so a simple configuration, i hope this helps.