31 mai 2013

Automating VM recovery with stand-alone vSphere Replication

With vSphere 5.1 VMware introduced the stand-alone vSphere Replication feature that enables you to continuously replicate Virtual Machines between different hosts using different storage. Formerly this feature was only available with SRM (Site Recovery Manager), this is why I call the SRM-less version "stand-alone" here, although this is not the official product name.Stand-alone vSphere Replication is included with the vSphere Essentials Plus Kit, the Standard, Enterprise and Enterprise Plus Editions. It... [Lire la suite]
Posté par jcdemarque à 15:19 - - Permalien [#]
Tags : , , , , ,

26 janvier 2011

Obviating Outlook Client Restarts after Mailbox Moves

The History Historically, when an administrator moved an Exchange 2010 mailbox from one database to another, the user's Outlook client would present them with a message stating: The Exchange administrator has made a change that requires you quit and restart Outlook. Only after restarting Outlook would the user have access to their mailbox. To understand this behavior, it's helpful to understand what generates the dialog in Outlook and why Exchange 2010 triggers the message. Outlook caches three items about each Exchange... [Lire la suite]
Posté par jcdemarque à 18:45 - - Permalien [#]
Tags : , , , , , , ,
26 octobre 2010

Did you know? All hosts failed…

Today I received a very valid question around a full cluster failure. What happens when all the hosts in a cluster go down and at some point return? Will the VMs be restarted and what do I need to have in place to ensure they will? It seems to be an urban myth that you need to use “auto-start” for a full cluster failure. But as you might have noticed that won’t work when HA is enabled. So what will? VMware HA Is it really that simple? Yes it is! When a full cluster fails and nodes start powering up HA will restart the VMs. As... [Lire la suite]
Posté par jcdemarque à 07:38 - - Permalien [#]
Tags : , , , , , , , ,