Friday, September 13, 2013

Zerto Virtual Replication



Zerto Virtual Replication 3.0 was designed to provide replication at the hypervisor level. Zerto Virtual Replication provides a business continuity (BC) and disaster recovery (DR) solution in virtual environments, enabling the replication of mission-critical applications that also provides automation of failovers and recoveries.

Zerto has moved physical array based replication to the hypervisor which follows the trend of abstracting hardware functionality to software for the software-defined datacenter. Their solution dramatically simplifies disaster recovery designs, and gives IT professionals the option of using cloud DR solutions from one of Zerto's cloud partners.

The Zerto components include:

  • Zerto Virtual Manager (ZVM): A Windows service, which manages everything required for the replication between the protection and recovery sites, except for the actual replication of data. The ZVM interacts with the vCenter Server to get the inventory of VMs, disks, networks, hosts, etc. and then service the Zerto GUI within vSphere Client console for the user to create and manage protected virtual machines. The ZVM also monitors changes in the VMware environment and responds accordingly. For example, a VMotion operation of a protected VM from one host to another is intercepted by the ZVM so the Zerto GUI will update it accordingly to the user. 
  • Virtual Replication Appliance (VRA): A virtual machine installed on each ESX/ESXi hosting virtual machines to be protected or recovered, to manage the replication of data from protected virtual machines to the recovery site.
  • Zerto Cloud Connector (ZCC): A cloud connector routes traffic between two networks belonging to different organizations, such as between a customer network and a cloud provider replication network, in a secure manner. Using a ZCC means that a cloud provider does not need to go through complex network and routing setups to ensure complete separation between a customer network and the cloud provider network.
  • Zerto vSphere Client console plug-in: A plug-in in the vSphere Client console that enables managing recovery using Zerto Virtual Replication from the console.

Sunday, September 8, 2013

vExpert Chili


In the spirit of the new football season I thought I would post my vExpert chili recipe.

2 lbs lean ground beef
1 lb beef sirloin, cubed
4 (15 oz) cans of kidney beans
3 onions, minced
2 tsp black pepper
12 bay leaves
4 cloves of garlic
2 (6 oz) cans of tomato paste
4 cups of water
2 cups of dark beer
8 tbsp of chili powder
1/8 tsp ground cayenne pepper
5 tbsp distilled white vinegar
3 tsp ground cinnamon
3 tsp ground allspice
2 tsp Worcestershire sauce
2 tsp salt
1 cup of brown sugar
1 tbsp unsweetened cocoa powder
2 cups shredded colby cheese
  • Brown ground beef in skillet with onions
  • Drain fat
  • Add and brown beef sirloin
  • Combine remainder of the ingredients
  • Cook over low head for 3 hours
  • When ready to serve, top with colby cheese and serve with tortilla chips

Tuesday, September 3, 2013

VMware Horizon Suite Insights

I wanted to post some insight I gained from VMworld around Horizon Suite and end user computing (EUC). VMware's focus is to provide a cost effective and performance driven solution for virtual desktop infrastructure. Some of this will be provided by new capabilities that are coming with vSphere 5.5.

vSphere 5.1 was the first vSphere release to provide support for hardware-accelerated 3D graphics—virtual graphics processing unit (vGPU)—inside of a virtual machine. That support was limited to only NVIDIA-based GPUs. With vSphere 5.5, vGPU support has been expanded to include both Intel- and AMD-based GPUs. Virtual machines with graphic-intensive workloads or applications that typically have required hardware-based GPUs can now take advantage of additional vGPU vendors, makes and models.

There are three supported rendering modes for a virtual machine configured with a vGPU: automatic,
hardware and software. Virtual machines still can leverage VMware vSphere vMotion technology, even across a heterogeneous mix of vGPU vendors, without any downtime or interruptions to the virtual machine. If automatic mode is enabled and a GPU is not available at the destination vSphere host, software rendering automatically is enabled. If hardware mode is configured and a GPU does not exist at the destination vSphere host, a vSphere vMotion instance is not attempted.

News: Top vBlog 2016 Trending: DRS Advanced Settings