Posted by Sheikvara
Since Vmware vSphere 6 is released the vCenter Virtual appliance (VCVA) has the same specifications as the Vmware vCenter installed on windows (VCS). So you can install the VC virtual appliance without to worry about limitations and also one windows server license less to buy. Downside is that there is nog migration path from VCS to VCVA, so before you upgrade to vSphere 6 you can first migrate to a VCVA 5.5 and the upgrade your virtual appliance to vSphere 6. there is a cool tool do this from Vmware fling website
“The VCS to VCVA Converter Appliance is the winning idea from the 2013 Fling Contest. It allows customers to migrate from Windows vCenter Server with an External Microsoft SQL Server Database to the vCenter Server Appliance with an embedded vPostgres database. The Fling migrates the vCenter database, roles, permissions, privileges, certificates and inventory service. The target appliance will run…
View original post 56 more words
The vCenter Server Appliance is good for small business to start with. VMware raised the limit from 5 ESX host en 50 VM to 100 ESX host and 3000 VM’s and this all with the embedded database. If you use an external oracle database then the limits are the same as the windows version
There are still some limitation in the vcenter Server Appliance
- no sql support for external database
- no linked vcenter possible
- no vmware update manager. you still need to install this on separate machine
- no heartbeat support
To deploy the vCenter Server Appliance 5.x:
- Launch the vSphere Client or vSphere Web Client.
- Go to File > Deploy OVF Template.
- Browse to the location of the vCenter Server Appliance downloaded
.ovffile and click Open.
- In the OVF Template Details page, click Next.
- In Name and Location, enter the name of your…
View original post 72 more words
After a week of installing vcenter 5.5, I noticed the event 7031 in the system logs and the vi client keeps disconnecting every few seconds.
the install was basic. only 2 esx host, vcenters server simple install on VM machine and arround 10 vm’s. only thing I did in advance is installing sql 2012 express because the database limit is 10GB instead of 4 GB on sql 2005.
So i started to investigate. First i though it was the update manager so i disabled the plug-in, next i uninstalled the IBM V3700 plugin. none of it worked. In the end i noticed that the disk only had 5 GB left and after looking what was eating up space i found the database grew to 10 GB. So here are some steps you can take to shrink the database and truncate the logs.
- stop the VMware VirtualCenter Server service
- install the…
View original post 361 more words
Posted by Sheikvara
Disaster recovery is something we pray never to happen but unavoidable in certain situations. Every business organization regardless of their size need to plan for a disaster recovery plan to protect their key business assets. In this articles we’re look into how Azure Disaster Recovery (Cloud based DR) can be used to protect critical business applications systems.
With recent updates there are several methods we can use Azure Site Recovery (ASR) to protect our on premise systems,
1. On-premises Hyper-V site to Azure protection with Hyper-V replication — Orchestrate replication, failover, and recovery from an on-premises site with one or more Hyper-V servers but . Virtual machine data is replicated from a source Hyper-V host server to Azure.
2. On-premises VMM site to on-premises VMM site protection with Hyper-V replication — Orchestrate replication, failover, and recovery between on-premises VMM sites. Virtual machine data is replicated from a source Hyper-V host…
View original post 958 more words
I came across above error when tried to setup ASR using new portal. Every step went find until I get below error,
clearly this highlight I cannot replicate the VM successfully to the Azure Recovery Vault. I’ve tried re-registering the Azure Site Recovery agent on the HYPER-V host as well. Though HYPER-V host register properly on the Recovery Vault VM protection fails with above error. On the hyper-v console I can see VM replication is on error state.
So finally meddle around the host logs I found out ASR has been setup previously and has not been removed properly. This means each VM replication also not completed and hanging around on error state. Only way to proceed is to clear those unsuccessful replication data on the host side targeting individual VM’s which is effected.
You need to run below mention PS command on each host targeting the effected VMs,
View original post 62 more words