Implementation Guide
Contents
1. WebGUI Dashboard once cece cssesessssceseessseeseseeseseeseseeseseesesesseseesesesseseeseseesessssessesssesseseasesessesessssessesessesesseseeseseeeseeseneeteneeveneseeneseens 31 1 31 ITI NIE www movis co at The way you like IT 7 3 NN CHONG Tal SVCD GW BCG roo seem snevenenseenaaneea 7 3 2 WebGUI Planned Failover 7 3 3 WebGUI UnPlanned Failover 7 3 4 WebGUI Recover venter 7 3 5 WebGUI History n os VSPHERE SETTINGS eene 2 7 2 0 WebGUI Clusters View L2 WebGUL Hosts VIEW utres 7 2 4 WebGUI Storage Pods View ween 7 2 5 WebGUI Datastores VIEW cece 7 2 6 WebGUI Virtual Machines View _ Failover e i NOVIS J RE Si ww movis co at The way you like IT 1 Overview 1 1 Description vCenter S S ESX i HA Cluste Met ML HN Replicated Datastores _ Fatlover vfailover provides an automated failover and failback mechanism for virtualized data centers in VMware environments Mirrored data stores and raw device mappings can be switched between sites either in planned or disaster scenarios Due to its broad range of supported VMware high availability cluster configurations it can be easily integrated in existing environments vfailover closes the gap between storage and application administration by combining deep VMware knowledge with years of storage array experience vfailover is a solution designe2. vfailover 7 0 Web Application 2014 2015 au marci iaid Ce Choose between different Instances Display Fullscreen LogOut Start Stop HORCM Instances Hide Left Menu Bar 31 ms mOVIS www movis co at The way you like IT Failover 7 2 2 WebGUI Clusters View After the Cluster is chosen information about Datastore LDEV and replication information will be shown If Virtual Machines button will be clicked information about the virtual machines running within that cluster will be shown VFailover E M ovis Jemo v ClusterComputeResource ap j gt MowsClus n EN Name MovisCluster Effective CPU 21404MMHz 27192MHz Bu share T TT vSphere DRS true Clusters 8 Hosts 2 Effective Memory 8E809MB 982868 Datastores 13 MovisCluster Virtual Machines Virtual Machine Status Label Type Data Center Serial Ldev Datastore Backup State Horcm State Replication State Application Server 1 vV Festplatte 1 FLAT Vienna 83014974 401 tan vfasower 1 wv wv PVC PAIR SVOL PAIR gt vented Application Server 2 v Festplatte 1 FLAT Vienna 83014974 400 tan wfasover v v PVOL PAIR SVOL PAIR Application Server 3 wv Festplatte 1 FLAT Vienna 3014974 401 san vfasower 1 v v PVOL_PAIR SVOL PAIR Application Server 4 vV Festplatte 1 FLAT Vienna 3014974 401 san vfasower 1 v wv PVOL PAIR SVOL_PAIR Application Server 5 v Festplatte 1 FLAT Vienna 83014974 401 san vfadsower 1 wv wv PVOL PAIR SVOL PAIR MailServer v Festplatte
3. Storage Vendor ID HITACHI HNAS SetInvisible SCSI Hide the S Vols after Failover TRUE FALSE SetInvisibleWithConfig SCSI Hide the S Vols during Config Run Backup TRUE FALSE HUR HUR Mirror Unit Number for Horcm Files ExcludeList Path to the LDEV Exclude List RDMs which are not mirrored One per Line Decimal CTGNO Consistency Group Number which will be covered with this configuration file Rescan HBA Rescan Option SERIAL PARALLEL RemoveVMHostOnfFailure in case of UNPLANNED Failover choose to remove ESX Hosts with dead objects data stores and or virtual machines from Config YES NO ObjectPrefix Choose Prefix for virtual machine and data store name on recovered Site during UNPLANNED failover e g recovered by vfailover j VMsInParallel How many VMs should be registered in parallel default 50 Log Level LogLevel Specify Logging 1 Error 2 Warning 3 Info 4 Debug Datastores Datastore Clusters dsCluster Datastore Cluster s handled by vFailover comma separated e g DSCProduction dsldentifier Datastore s handled by vFailover comma separated vFailover dsvCenter Datastore where the vCenter server is located e g san_vCenter Email Settings for Mode Status EmailNotification Email Notification enabled NEVER ONERROR ALWAYS EmailSmtpServer SMTP Server for sending mail EmailFrom Email sender address vFailover should use EmailTo Email Recipient s
4. Vendor HITACHI HNAS s RemovevMHostonFailure YES NO ObjectPrefix custom prefix SetInvisible TRUE FALSE SetInvisiblewithconfig TRUE FALSE 2 Rescan SERIAL PARALLEL ExcludeList file with RDM LUN Numbers to exclude on failover gt EN P e M Preu C Hor cmRoOot C HORCM et c vendor HITACHI SetInvisible FALSE SetInvisiblewithconfig FALSE Rescan SERIAL RemovevMHostOnF ai lur e NO ObjectPrefix Recovered by vFailover z Ee wt T cnc RETRO TE UNES SEINE UEM N TUR IISNGT OUS OEIORSSMR UE log level 1 Error 2 Warning 3 Info 4 Debug E PC Re Rea a ue T E E RE SU ME SER NC ES LogLevel 4 datastore s or datastore cluster examples s dsc luster myo0s5c luster dsIdentifier vfailoverNAS nasi nas20 ne a E E A a a ee ee dsc luster vFai loverDsc zdsIdentifier ESX PROD VIENNA ESX PROD PRAGUE inp coe email settings vfailover sends result of mode status EmailNotification NEVER ONERROR ALWAYS s Emails5mtpserver smtp server EmailFrom from email addr s EmailTo to email addr gt comma separated Ee ea E LM Kee EmailNotification ALWAYS EmailSmtpserver movismxs movis
5. allover 7 2 4 WebGUI Storage Pods View Information about Datastore Clusters Storage Pods will be shown there The member datastores their extents LDEV and Replication Status will be shown If Virtual Machines button will be clicked in the StoragePod Frame information about the virtual machines running on that Storage Pod will be shown V Failover j 2 MovisDemo v Name Childs Storage DRS IO Load Balance Default VM Behavior Load Balance Interval Storage Pods oO vFailoverDSC Replication State Q Datastore Status E san vfallover 0 v n an vfallower 1 san vfailover Y san vfailover 2 wv Datastore Statut wtfttodofdentries 3torag ePod gt vFalowrDSC vFailoverDSC 3 true Used Space true automated 480 gt Datactores Extent Data Center Serial Ldev Storage Pod Backup State Horcm State Replication State 0 Vienna 83014974 400 vFallowerDSC v v PVOL_PAIR SVOL PAIR 0 Vienna 83014974 401 vFallowerDSC v v PVOL PAIR SVOL PAIR Vienna 82014974 407 vFailoverDSC vY PVOL PAIR SVOL PAIR 1 Vienna 83014974 403 vFailoverDSC v wv PVOL PAIR SVOL PAIR Extent Data Center Serial Ldev Storage Pod Backup State Horcm State Replication State WFailover y i 2 MovisDemo Name Childs Storage DRS i Instance 8 O Load Balance Default VM Behavior Load Balance Interval Storage Pods a Replication State vFalloverDSC Q Virtual Machine n Application Serve
6. has to be confirmed with Y Set ExecutionPolicy unrestricted Set ExecutionPolicy bypass 3 2 3 System Environment Variable To allow vfailover to be installed at any place on the vfailover Management Server please add the following System Environment variable to your Management Server variable VFAILOVER value Installation Path of vfailover gt f e if vfailover is installed at C Program Files vfailover set the system environment variable to VFAILOVER C Program Files ITI NZIES 10 Lm uM ovis co at The way you like IT Nm Failover 32A vfailover Cluster Configuration File vfailover setup is based on configuration files depending on the vSphere environment Three different types of vCenter configurations are supported described in chapter 2 1 1 Configuration is stored in properties files There are several sections where the operating parameters will be specified The configuration Files have to be created in conf subfolder in the vfailover directory e g cNprogram files vfailover cont on both vfailover management hosts This will be done at the initial setup of vfailover for the existing environment Every time an additional VMware HA Cluster is added new files have to be created These files will be created by WebGUl from version 6 6 3 but you can create it manually as well 11 Global Settings HorcmRoot Path where Hitachi Command Controller Interface is installed Vendor
7. 1 FLAT Vienna 83014974 400 san vfasiover 0 wv wv PVOL PAIR SVOL PAIR MailServer v Festplatte 2 FLAT Vienna 83014974 400 san_vfailover_0 v v PVOL_PAIR SVOL_PAIR MailServer v Festplatte 3 FLAT Vienna 83014974 400 san vfadower 0 v v PVOL PAIR SVOL_PAIR vcenter wv Festplatte 1 FLAT Prague 200 san_data_vcenter v v PVOL PAIR SVOL PAIR Failover 25 MovisDemo Bl Hon lt meari urn onam e ClusterCornputeResource d shiboard gt MowsClusrer UR db Summary i fi m 4 4040 27192 Instance a Name MovisCluster Effective CPU 21404MHz 27192MH vSphere HA true vSphere DRS true BIEN REED Clusters B kis r osts 2 Effective Memory 89809MB 98286ME MovisCluster Datastores 13 Replication State virtual Machines gt Datastorer tuai Machines E DL I Datastore Status Extent Data Center Serial Ldev Storage Pod Backup State Horcm State Replication State san data wcenter v i Prague 82015218 200 I wv PVOL PAIR SVOL_PAIR 4 st san vfailaver 0 wv 0 Vienna 82014974 400 vFailoverDSC wv vw PVOL PAIR SVOL PAIR ian vfailaver 1 wv 0 Vienna 82014974 401 vFailoverDSC wv wv PVOL PAIR SVOL PAIR san vfailaver 2 wv 0 Vienna 83014974 402 vFailoverDSC wv wv PVOL PAIR SVOL_PAIR san vfailawer 2 v 1 vienna 83014974 403 vFailoverDSC v v PVOL PAIR SVOL PAIR Datartore Status Extent Data Center Serial Ldev Storage Pod Backup State Horcm State Replication State 32 ITIONM LE um Www movis co at Th
8. 2 MovisDemo O0 Recover vCenter gt MoasDerno ec Recover vCenter i A gt Recover vCenter beep arget Data Center Prague Target ESX Host prague movis local Datastore san data vcenter After that the datastore will be brought online on the remaining site the vCenter server will be brought online As soon as vCenter is up and running an unplanned failover operation for all the other protected VMs in the environment can be started MOVIS aa BL WWE ww movis co at The way you like IT Failover For the failover recovery of vCenter server some questions have to answered J as Recover vConter x E B REE TERETE bici Nonii QR CEA search resto E vfailover Logn Question Is the storage subsystem at failed site still available y Br Recover vCerter Sven moni vfaliover Login Question jeCopy HUR volume pairs still ir eoo eo Dre 45 w NOVIS EE The way you like IT 46 y s Recover vCenter Ld T viennamgmt cU vfallover Login y F Task viesnangnt 2080 vFatove Question the command device Question Proceed stil avallable TA tA MOVIS www movis co at The way you like IT 7 3 5 WebGUI History History shows task list and link to logfiles for troubleshooting Y a amp 47 Failover Action ance Task History Task Type vCenter Recovery vCenter Recovery vC
9. 32 03 01 HUS and AMS and above 01 32 03 06 USP USP V VSP G1000 HUS VM and above 2 5 vfailover Management Server If running vfailover on the vCenter server vSphere compatibility matrix has to be checked http www vmware com resources compatibility search php The following operating systems and additional software is supported by vfailover Windows 2003 Server R2 Windows 2008 Server Windows 2008 Server R2 Windows 2012 Server Windows 2012 R2 Server Windows Powershell 4 0 ITI NIE LI j RE Si wuw movis co at The way you like IT Nm Fatlover 3 Implementation 3 1 Installation and Preparation 3 1 1 One vCenter server with two dedicated vfailover management Hosts e Preparation of two virtual machines Software requirements described in chapter 2 e Installation of Windows Powershell software and or update to v4 http www microsoft com en us download details aspx id 40855 e Installation of PowerCLl software e Download PowerCLIl from VMware website and install as described in the installation Guide http communities vmware com community vmtn vsphere automationtools powercli e Installation of VMware vSphere Client e Installing Hitachi Command Control Interface e Presenting of at least one Command Device per Hitachi Storage Array as raw device mapping to the virtual machines e Copying vfailover Delivery Kit to C Program Files vfailover 3 1 2 Two vCenter Servers The same steps as descri
10. Technology as NOVIS i I Second Site Do ww movis co at The way you like IT Nm Failover vCenter server is the core component in the VMware virtual infrastructure It is essential that it is available or can be easily restored to running state in case of a site failure There are several ways best practice to achieve this Two virtual center configuration one at each datacenter In this setup no extra tasks are necessary to make vCenter accessible on both sites vfailover can be integrated on each vCenter server Cold Standby vCenter server vCenter server is setup as virtual machine in the virtual environment Scheduled clones of the vCenter VM to a datastore located at the other datacenter ensures that vCenter server is ready to be booted at the remaining datacenter in case of disaster The datastore where the VM Clone resides should be available to all ESX i hosts in the second datacenter Then the administrator can decide where to register and startup the backup vCenter server Clones should be created on a regular basis once a day to make sure vCenter configuration is current The schedule depends on the configuration changes or monitoring needs for the environment Two separate vfailover management hosts one at each site have to be used in this configuration because it is not possible to establish clones from virtual machines with raw device mapping Any other method making vCenter server available There are
11. address comma separated a NOVIS J RE Fiw movis co at The way you like IT Nm Failover Virtual Machine Boot Order Control WaitOnPing vFailover waits on ping before starting next set of VMs TRUE FALSE PingTimeOut Seconds to wait for ping reply Site A Datacenter A Configuration Settings DataCenterA Data center Identifier vCenterServerA vCenter Server Name or IP Address ConnectionTypeA vCenter Server connection type http https InstanceA Instance Number used by Hitachi Command Control Interface PortA TCP Port used by Hitachi Command Controller Interface StorageA Storage subsystem serial number HAClusterA vSphere HA Cluster SiteA ESX i hosts in site A comma separated Site B Datacenter B Configuration Settings DataCenterB Data center Identifier vCenterServerB vCenter Server Name or IP Address ConnectionTypeB vCenter Server connection type http https InstanceB Instance Number used by Hitachi Command Control Interface PortB TCP Port used by Hitachi Command Controller Interface StorageB Storage subsystem serial number HAClusterB vSphere HA Cluster SiteB ESX i hosts in site A comma separated TTNOVIS um movis co at The way you like IT Failover Example property file HDS properties 13 i HDS properties Notepad File Edit Format View Help lj global settings HorcmRoot horcm folder
12. before starting next virtual machine If empty or custom attribute not exists vWait 60 vBoot Start VM or keep VM powered off If empty or custom attribute does not exist VM will be started if it was running before failover or will be kept powered off if it was not turned on before failover SP Edit Departement IT Services Book Yes Priority 1 walk 300 Motes Failover Test Server al 15 e i NOVIS j WII Si ww movis co at The way you like IT Nm Failover 3 2 0 vfailover Configuration File Parameter CTGNO vfailover can handle two different types of consistency group usage Scenario 1 CTGNO needs not to be defined in configuration file e Data store 1 CTGNO 2 o virtual machine 1 virtual disk on data store 1 CTGNO 2 inherited raw device 1 CTGNO 2 aw device 2 CTGNO 2 o virtual machine 2 virtual disk on data store 1 CTGNO 2 inherited raw device 3 CTGNO 2 Scenario 2 CTGNO needs to be defined e Data store 1 CTGNO 5 o virtual machine 1 virtual disk on data store 1 CTGNO 5 inherited raw device 1 CTGNO 5 o virtual machine 2 virtual disk on data store 1 CTGNO 5 inherited aw device 2 CTGNO 5 e Data store 2 CTGNO 5 o virtual machine 1 virtual disk on data store 2 CTGNO 5 inherited o virtual machine 2 virtual disk on data store 2 CTGNO 5 inherited In scenario 1 there is no need to set the CTGNO parameter as there is only one data store conf
13. local EmailFrom praguemgmtavf ai lover com Emai ITo info movis co at PENE E E E E E EE E M m MM M virtual machine boot order control vfailover waits on ping before starting next set of virtual machines WAITONPING TRUE FALSE PINGTIMEOUT seconds to wait on ping 32 P o e M HOP is sl css amas as as RI WaitonPing TRUE PingTimeout eo 3 Site A a Ra ce Re ee oe Data center Identifier DataCenterA Vienna vSphere vCenter Server Name or IP Address vCentersServerA 192 165 1 200 vCenter Server connection type http https ConnectionTypeA HTTPFS Instance Number and TCP Port used by Hitachi Command Control Interface InstanceA i0 PortA 11030 Storage subsystem serial number StorageA 7519 vSphere HA Cluster Name HAC TuUSterA Movisc luster ESX 1 hosts in site A comma separated SiteA vienna mowvis local cates re Site B Ld 4 k E w i NOVIS i rn The way you like IT Nm Failover With some of these parameters the specific vSphere environment will be defined Here are configuration examples for the different setups one VMware vSphere HA cluster with one vCenter server HAClusterA myVMwareCluster HAClusterB vCenterServerA myVSphereServer vCenterSer
14. machines will be displayed This has to be confirmed by entering yes to start the takeover Workflow major steps for an unplanned failover operation e Connect to ESX I server e Find out the virtual machine where vcenter server is installed e Based on user input storage will be treated as available or not availabe e Available Swap storage replication horctakeover of datastore LUNs at Storage level Truecopy mirrors volumes will be failovered e Not available Make replication volumes read and writeable on second storage subsystem Enable write access to LUNs at the remaining datastore remove write access from primary volumes if still available e Rescan HBAs and VMFS Rescan ESX i host to refresh vCenter LUN configuration e Resignature datastore Datastore may be recognized as Snapshots at the other site As the base signature values have changed other storage subsystem resignature will be executed to write a new signature onto the datastore This operation involves another vmfs rescan e Rescan HBAs and VMFS Rescan ESX i host to refresh vCenter LUN configuration e Register virtual machine Virtual Machine will be registered on ESX i host e User can decide if the script should power on the virtual machine 25 a i NOVIS j RE Si wuw movis co at The way you like IT Nm Failover 5 vfailover Framework vfailover uses a designated Folder structure This structure is already preconfigured in the vfailover
15. 10 22 20 19 2015 03 10 21 Uo 4 03 2015 03 10 21 33 06 2015 03 10 21 25 53 2015 03 10 20 45 15 2015 03 10 20 36 38 2015 03 10 20 19 18 20 09 58 2015 03 10 2015 03 10 20 09 11 2015 03 10 20 08 36 Date The way you like IT Nm Failover 8 vSphere Settings In vSphere 5 environments an additional parameter is mandatory for Setups with only one vCenter Servers If access to Storage is lost in VMware this scenario is called APD AII Path Down In this case the VM Hosts ESXi Server try to get the paths back online again This may result in a condition where all affected ESX Hosts even on remaining site and VMs will get unresponsive which in some circumstances causes the whole virtual environment to fail To avoid this behavior a parameter has to be changed on the ESX Hosts This parameter tells the ESX Hosts to fail unresponsive LUNs when all paths are gone Storage outage Value for VMFS3 FailVolumeOpenlfAPD has to be set to 1 EP FTT Settings Ea Annotations BufFerCache H Contig E Vpx Sv Motion E Syslog H YMkernel 48 VIMES3 FailvalumeopenIFAPD 1 Fail VMFS volume open operation iF the underlying device is deemed to be under an all paths down can Min O Max 1 VIMES3 HardwareAcceleratedLocking fo Enable hardware accelerated YMFS locking requires compliant hardware Min O Max 1 yMFS3 MaxHeapSizeMB o Maximum size in MB to which Ehe YMFS he
16. 18 TTNOVIS www movis co at The way you like IT Failover 4 3 Operation Mode status Operation mode status displays the state of vFailover setup and configuration backup and the according state of the Truecopy mirror In a working vSphere environment this information can be used for documentation purposes or to check if all Truecopy mirrors are working and in the proper state Sample syntax for operation mode status after v6 6 2 C Program Files vfailover Scripts vfailover os1 ConfFile vfailover MainCluster Mode status Sample output for operation mode status YMware Sphere PowertLI 5 5 Release 2 Patch 1 Co Program Files vFailover cripts gt vFailover psil Mode status ConfFile MovisDemo Read Credentials of user UMWARE Read Credentials of user STORAGE Connect to vSphere vCenter xml Backup of all Configuration Settings Cluster Datastore VM was successful 0 or not X vm host all VM Hosts ESXi Servers specified in porperties File are available 0 or not X horcm HORCM Files are available and Instances are running 0 or not X replication Truecopy Replication Status is OK 0 or not OK X 19 ITICO MICTS Wm movis co at The way you like IT Failover 4 4 Operation Mode planned Operation mode planned is used for planned switching failover failback operations It can only be used if the affected vSphere HA Clusters are fully operational and th
17. Failover 2 MovisDemo v t Dashboard S HostSystem wennarmovs local Name vienna movis local Vendor System manufacturer zi Mo System P EX instance Mc Je Syste roduct Name CPU Model Intel R Xeon R CPU E5520 2 27GHz CPUS 8x 2266 MHz t Power State P poweredon 4 x Connection State connected m Boot Time 22 01 2015 12 06 49 vienna movis Jocal CPU 62 MEMORY Mact Replication State gt Virtual Machines Q Virtual Machine Stetus Label Type Data Center Serial Ldev Datastore D Applicaton Server 1 vY Festplatte 1 FLAT Vienna 83014974 401 san_vfallover_1 Applicaton Server 2 v Festplatte 1 FLAT Vienna 83014374 400 san vfallaver 0 Application Server 3 wv Festplatte 1 FLAT Vienna 2014974 401 san_Mailover_t Application Server 4 wv Festplatte 1 FLAT Vienna 83014974 401 san vfailover 1 Application Server 5 vw Festplatte 1 FLAT Vienna 83014374 401 san vfallower 1 wcenterdb v Festplatte 1 FLAT Prague 83015218 200 san data wcenter Virtual Machine Statut Label Type Date Center Serial Ldev Datastore Application 2014 2015 Backup State 4466 6 wv Backup State Horcm State Y PVOL v PVOL v PVOL Y PVOL v PVOL wv PYOL_ Horcm State Replication State PAIR SVOL_PAIR PAIR SVOL PAIR PAIR SVOL PAIR PAIR SVOL PAIR PAIR SVOL PAIR PAIR SVOL PAIR Replication State 33 LE um www movis co at ITIONM The way you like IT __
18. V oo Z Faiilower Implementation and User Guide Version X Nm Failover OV ERVE VV s DNE E T e B li Sue X OO 9Av E 4 13 BITS E 4 BP ed OT EIEN ES c 5 2 1 VMWARE ENVIRONMENT csccssessessesssssessessessessecsecsesssssussussussisassassssssessussassussussnsansassessssessessussassssssssisansassssessessessessesssssssseaseaseateaeaseeses 5 22 ide uices ds 6 2 3 HITACHI DATA SYSTEMS STORAGE ARRAYS ccsscsscssessessessessessssssesssssssssssssessasassissississsssisasassintissistississisatsansississintissississusetsecsetsessieetseessessess 7 2 4 IITACHLDAPA SYSTEMS SOFTWARE REQUIREMENTS saccscccedcc cuco nett deant E pu spetta nct ues dre bcc EE EE 2 5 VPAILOVER MANAGEMENT SERVER IMPLEMENTATION EEEn 8 oA INSTALLATION AND PREPARATION MM 8 3 11 One vCenter server with two dedicated vfailover management Hosts c ccceccssecsssessesescesesceseeseseeceseceeseceeseseereseeteneeenee 8 3 1 2 TWO vCenter Servers
19. a 82014974 400 san vfailover wv v PVOL_PAIR SVOL_PAIR MailServer wv Festplatte 3 FLAT Vienna 82014974 400 san vfailaver wv v PVOL_PAIR SVOL_PAIR Virtual Machine Status Label Type Data Center Serial Ldev Datastore Backup State Horcm State Replication State MOVIS The way you like IT OB uws www movis co at Nm Failover 7 2 6 WebGUI Virtual Machines View Information about Virtual Machines will be shown there This information will be fetched from vCenter Server You can see utilization of disk space memory and cpu The replication state is displayed and if there is an actual backup In the Datastores menu more detailed information from the underlying datastore will be displayed y f Application Server 3 B OMNEM ELM 2 a viennamgmt 50 ilove iebapp main MovisDemos allover webappj VirtualMact m 7468 C Search P wfallover Login i ett V Failover p Home nstance Virtual Machines Appl cation 5erver 3 5 MovisDemo v VirtualMachine Applicaton Server 3 tS a Summary E A r Name Application Server 3 Used Storage 5GB 8GB mm Template false ER instance e P ere tU M Path Name san vfailover 1 Application Server 3 Application Server 3 vmx Guest Name Microsoft Windows Server 2003 32 Bit Unshared Storage SGB 8GB Clusters DNS Name vfapp4 movis local IP Address 192 168 1 153 TR Power State P poweredOn ean tae ESX Host vienna movis local tas E a Virtual Mach
20. ap is allowed to grow Min 16 Max 256 VMFS3 OpenWithaut Journal 1 Open File system when aut of space For journal allocation allowing reads and no meta data updates Min O Max 1 EE NN Cancel Help ee TIONIS EB RE Si ww movis co at The way you like IT
21. bed in chapter 3 1 1 apply to this configuration There is no need to prepare dedicated virtual machines for vfailover although it would be possible 3 1 3 Different vCenter Setup Any other vCenter server configurations have to be verified before starting the installation vfailover can be integrated in various scenarios but some may require additional effort ITI DN IES D RE Si wuw movis co at The way you like IT Nm Fatlover 3 2 vtailover Configuration 3 2 1 Permissions To make vfailover working permissions on the vCenter server and on the management hosts are needed For the installation and operation of vfailover local administrator rights are required either on the dedicated management hosts or on the vCenter servers Additionally vfailover can only be executed with a user account that has the datacenter administrator role assigned 3 2 0 VMware PowerCLl Configuration vfailover is a scripting solution based on Windows Powershell and VMware PowerCLl extension It can only be executed in a Windows Powershell Environment To allow scripts be executed from within the shell the execution policy has to be set You may also get a warning during the installation of PowerCLl This warning can be ignored and the installation continued im V ware vSphere PowertLI The PowerShell execution policy of this computer is nok set to RemoteSigned This prevents execution of PowerShell scripts an your computer Th
22. d for minimizing downtime in cases of disaster or planned maintenance operations in a VMware HA Cluster environment running in two datacenters There is no need to reconfigure the virtual environment before initiating failovers Failover Failback tasks are fully automated and initiated the same way Replication may be configured bidirectional vfailover works on data store RAW device mapping basis That means single multiple or all mirrored Datastores can be switched between datacenters in one task with one click command vfailover is a script based solution running on vCenter Server or a system which has network connection to vCenter Server There slightly different requirements depending on the supported storage platforms vfailover works in environments with one or two vCenter servers vCenter is an essential component It has to be assured that it s available or can be recovered easily at the remaining site in case of a disaster With this solution and storage vendors remote replication technologies it is possible to protect important virtual machines by mirroring the underlying data stores a NOVIS j WII Si ww movis co at The way you like IT Nm Failover 1 2 Environment vCenter Server Central Management Server for the virtual infrastructure ESX i Servers Hosts with VMware ESX or ESXi Hypervisor configured into VMware High Availability Clusters HDS Storage Array HDS enterprise or modular storage array
23. delivery kit and should be copied to ProgramFiles folder on the vfailover management host s or vCenter server s Folder Structure E T vFailover n Backup Hj Conf Js db Ji Log El i Scripts E j tmp m Web e Backup Folder not actively used by vfailover Could be used to store xml File exports from db folder e Conf vfaillover Cluster Configuration files created during initial setup or if new clusters are added e Db xml Files with backup of the vCenter configuration Created during operation mode config if parameter backup is specified e log Log file folder for all vfailover operations e Scripts vfailover Powershell script folder e mp Folder for temporary files created during vfailover operations e Web Folder for vFailover WebGUI 26 TIONIS www movis co at The way you like IT 6 Parameter Type Decription string Name of configuration file Obsolete from v6 5 on use StoreCredentials instead Mode string planned planned Failover unplanned unplanned Failover Status Status View config update vfailover DB repair Repairs Virtual Machine configuration vcenter failover mirrored Datastore with vCenter server on it ConfFile m M Default config Datastore Identifier if not specified in properties file or entries in properties file should be overruled Datastore string Default all Is an option when executing wit
24. e ConsoleOutput string If a filename is specified for this parameter the console output will also be piped to the respective file RESERVED PARAMETERS Name Type Decription PluginRequest string RESERVED FOR WebGUI vCenterRecoveryServer string RESERVED FOR vCenter Mode RecoveryUserPwd RESERVED FOR vCenter Mode 28 MOVIS OB WWE ww movis co at The way you like IT Nm Failover 7 vFailover WebGUI vFaiover WebGUI is designed to support the administrators using vFailover in their environments If a GUI is preferred all the modes can be executed through the Web Browser Even configuration settings can be done there There is all the Information Cluster Host VMs Datastores Disks displayed which is necessary for operating vFailover The WebGUI has to be installed on both management servers Requirements for the WebGUl per Management Server e Apache Tomcat 7 0 47 for Windows e X64 Java JRE 7 latest Update e Web Browser Firefox working with others too but vFailover WebGUI is optimized for Firefox 4 WebGUI Login 1 1 1 Login At the Login Frame the vFailover instance a valid username and password has to be specified W yfallover Login x P viennamgmt 3080 vfailoverfwebapp login C A Search F wfailover Login ate Sign In vCenter Server ESX Host 192 168 1 200 T User movisxadministrator Password Sign in Contact us About info vfailover com Versio
25. e Truecopy mirrors are in pair state This mode is designed for a planned takeover of one or more datastores to the other datacenter This may be necessary for example if one of the sites has to be brought down for maintenance work Sample syntax for operation mode planned after 6 6 2 Sample output for operation mode planned In this example all datastores containing san vf in the datastore name will be switched to the datacenter named Remote with the vCenter user account administrator After executing the vfailover operation the password for user administrator has to be entered for a successful connection to vCenter server Before the takeover will be executed a summary of the affected datastores and virtual machines will be displayed This has to be confirmed by entering yes to start the takeover p VMware ee PowerCLI 5 5 Rolcase 2 Patch 1 e Movislemo Dest inat tonDataler i Vienna i Vienna gt Ulenna C Program Files svFailoversSerip 20 si NOVIS ww ww movis co at The way you like IT Nm Failover Workflow major steps for a planned failover operation Shutdown PowerOff virtual machines all virtual machines where VMware Tools are installed will be shut down properly If not possible or no VMware Tools are available they will be powered off The script waits 5 minutes initially on the shut down process If some of the virtual machines do not shut down within the first 5 minutes user will be ask
26. e way you like IT 1 2 3 WebGUI Hosts View _ allover After one of the VM Hosts ESXi Server is chosen information about Datastore LDEV and replication information will be shown If Virtual Machines button will be clicked in the HostSystem Frame information about the virtual machines running on that host will be shown V Failover 25 MovisDemo eb gt wenna rnows local firtual Machines gt Datastores Name vienna movis local vendor System manufacturer a Mode System P SS instance B Model System Product Name CPU Mode Intel R Xeon R CPU E5520 2 27GHz CPUS 8x 2266 MHz Power State P poweredon H Connection State connected nx B Boot Time 22 01 2015 12 06 49 vienna movisdocal x 244 OU loan MEMORY gt Replication State Q c Datastcre a Status Extent Data Center Serial Ldev Storage Pod 9 san data wcenter v 0 Prague 83015218 200 san_vfallover_0 v 0 Vienna 83014974 400 vFallowerDSC tan vfailover 1 I d 0 Vienna 83014974 401 vFailoverDSC t n wfallover 2 wv 0 Vienna 82014974 402 vFailoverDSC san vfailover 2 wv Vienna 83014974 403 vFailoverDSC Datastore Statue Extent Data Center Serial Ldev Storage Pod owing 1 to Sof 5 ent Backup State Backup State Horcm State Horcm State PVOL_PAI PVOL_PAI PVOL_PAI PVOL PAI PVOL_PAI N Replication State R SVOL PAIR R SVOL PAIR R SVOL PAIR R SVOL PAIR R SVOL PAIR Replication State W
27. ed whether to wait another 5 minutes to wait forever or to force a power off Possible User Input waitbmin forever poweroff Reconfigure virtual machines for failover Raw Device Mappings and virtual disks which reside on a different datastore than the main datastore of the virtual machine have to be removed from virtual machine configuration for a proper takeover Attention If virtual disks reside on different datastores user has to failover all the datastores together in one step Unregister virtual machines Virtual Machines will be unregistered from vCenter configuration Unmount data store s from all ESX i hosts if vSphere Version 5 is installed Swap storage replication horctakeover of datastore and RAW Device LUNs at Storage level Truecopy mirrors volumes will be failovered Rescan HBAs and VMFS Rescan of all ESX i hosts to refresh vCenter LUN configuration Resignature datastores Datastores may be recognized as Snapshots at the other site As the base signature values have changed other storage subsystem resignature will be executed to write a new signature onto the datastore This operation involves another vmfs rescan Rescan HBAs and VMFS Rescan of all ESX i hosts to refresh vCenter LUN configuration Register virtual machines Virtual Machines will be re registered in the vCenter Reconfigure virtual machines o Raw Device Mappings and virtual disks will be added back to the Virtual Machine conf
28. enter Recovery Backup Disaster Recovery Maintenance Activity Backup repair repair Backup Task Type Show vfailover ng 1 to 10 0f 19 en State Error X Error X Error wf Success Warning warning wf Success wf Success O Unknown Success State 7 0 Web Application 2014 2015 Message No valid ESX hosts found to register virtual machines Gather datastores failed Gather datastores failed Backup for MOVISDEMO finished successfully Disaster Recovery was cancelled by user Maintenance Activity was cancelled by user Backup for MOVISDEMO finished successfully virtual Machine Repair for MOVISDEMO finished successfully N A Backup for MOVISDEMO finished successfully Message Log File vFallover_ vFailover vFailover vFailover vFailover vFailover _ vFailover vFailover vFailover vFailover Log File Movic viovis B nwic VIOVIS Movis Movis Mavic VIOVIS Movis Mnvic VIOVIS Mr viOvis Movis AA e VIOVIS Demo vcenter 2015 03 10 21 34 45 log Demo vcenter 2015 03 10 21 9 log emo vcenter 2015 03 1 Demo config 2015 03 10 21 23 53og Demo planned 2015 03 10 20 30 00 log Demo config 2015 03 10 20 Jemo repair 2015 03 10 20 09 15 log Demo repair 2015 03 10 20 09 06 log Demo config 2015 03 10 20 06 52Jog LE um www movis co at Demo unplanned 2015 03 10 20 39 42log ITIONM _ allover Date v 2015 03
29. h mode planned or unplanned DestinationDataCenter string Data center to which the script should failover the data stores and virtual machines Is an option when executing with mode config Backup boolean Stores information in the db folder of vfailover that allowes unplanned failover Default true StoreCredentials boolean Usage example vfailover ps1 conffile hitachi mode status storecredentials true gt you will be asked for vcenter and storage user credentials will be stored for this user 128bit encryption After that you can run vFailover without Parameter User vfailover ps1 conffile hitachi mode config status planned etc without user With WebGUI you need a User with stored Credentials No other user can modify the credentials only the user itself Default false 27 TIONIS www movis Co at The way you like IT Failover Type Decription MaintenanceMode boolean Is an option when executing with mode planned If for example all the datastores should be switched from SiteA to SiteB for maintenance reasons and this option is set to Strue all the ESX i hosts at SiteA will be brought into maintenance mode Default false SilentMode boolean Is an option when executing with mode planned No interaction with user at all In case of a failure the script retries each function 5 times before configuring automatic failback Default fals
30. ials of onnect to inis r ather objecti z Start H R H ins tances r virtual machin BRIERE L m At Lin Low d a d Hpplicati Lon Application Applic at App lic on 2 App L Lc 2t Lon Server 5 Mai Server uo lur Laure umfs r valid Unos t 3 Register virtual machinels d Credentials of user UPHRE 2 ORAGE WA HotRunn ing Old LA vA m TT F IIIS Ie e EC x unu fe ooo Y App Li Lo at ic im Ser Hppli Lc at Lo in f Application Appl i Loat Lon m Appl i ication Ser Hat Server configure cluster configure virtual apps m iT o on Fart Virtual machinels top HORCH instances occa C Proaram Files veFailover Scriptz 22 17 MovVvis ww ww movis co at The way you like IT Nm Failover Workflow major steps for an unplanned failover operation e Move still running virtual machines VMs have to be moved from VM Hosts that also run virtual machines with failed datastores Storage Subsystem failure e f Parameter RemoveVMHostOnFailure is set to Yes VM Hosts and or VM Hosts with failed datastores will be disconnected and removed VM Hosts with orphaned objects have to be removed from vCenter configuration for proper failover operation If Parameter RemoveVMHostOnFailure is set to No VM Hosts and VMs will remain in configuration as orphaned objects Mirrored Datastores and depending VMs will be recovered and get a prefix as defined with the ObjectPrefix pa
31. iguration o Move virtual machines into its folder o Set custom attributes o Reconfigure virtual distributed network switch configuration Reconfigure cluster to rebuild all the virtual machine settings that have been before failover Power on virtual machines as defined in bootorder File a ITICON IES J RE Si ww movis co at The way you like IT Failover 4 5 Operation Mode unplanned Operation mode unplanned should only be used in case of a site ESX i host storage array failure With this mode failed datastores and virtual machines will be brought online at the remaining site Sample syntax for operation mode unplanned after v6 6 2 C Program Files vfailover Scripts vfailover os1 ConfFile vfailover movis ha Mode unplanned DestinationDatacenter Hemote In this example all datastores containing san vf in the datastore name will be switched to the datacenter named Remote with the vCenter user account administrator After executing the vfailover operation the password for user administrator has to be entered for a successful connection to vCenter server Before the takeover will be executed a summary of the affected datastores and virtual machines will be displayed This has to be confirmed by entering yes to start the takeover VMware vSphere PowertLI 5 5 Release 2 Patch 1 C Program Filles ZCTR lover Seripte gt aufai lower psi Hode unplanned ContF il i it it ad Credent
32. igured in consistency group 2 Typically you would create one vfailover configuration file per Vmware cluster setup In scenario 2 there are two different data stores serving the same virtual machines with capacity In that case it makes sense to define consistency group as the virtual machine might need consistency over all their hard disks in case of a failure Therefore you need to configure those two data stores into the same consistency group 5 By specifying CTGNO 5 within the vfailover configuration file the HORCM instances will be created with only one group instead of a group per data store You create as much vfailover configuration files for the same Vmware cluster as consistency groups exists In case of a failover at scenario 1 you can failover data store by data store or all data stores at once In case of a failover at scenario 2 you can only failover all data stores together 16 THOVIS www movis co at The way you like IT CB uws Nm Failover 4 vfailover Operation 4 1 User Authentication User Authentication has changed with version 6 6 2 to a more secure method User Name and password had to be specified during execution of vFailover Credentials were stored if optional parameter StoreCredentials true was used Now you have to use StoreCredentials true parameter the first time you execute an vfailover operation for a specific User Then you will be asked for Username and password These credentials wi
33. ines e Mail Appl ti Replication State Virtual Machines Datastores Application Server 4 Application Server 5 Q 10 M Application Server 3 Virtual Machine Status Label Type Data Center Serial Ldev Datastore Backup State Horcm State Replication State Pp Application Server 3 wv Festplatte 1 FLAT Vienna 83014974 401 san vfailover 1 wv v PVOL PAIR SVOL PAIR rdb Virtual Machine Status Label Type Data Center Serial Ldev Datastore Backup State Horcm State Replication State Showing 1 to 1 of 1 entries vfailover 7 0 Web Application 2014 2015 36 ITIONIt LH um The way you like IT www movis co at Nm Failover 7 3 WebGUI Actions 7 3 1 WebGUI Backup WebGUI Backup means that a configuration run of vFailover will be initiated to get all the actual configuration information With Start Backup config run may be initiated immediately Additionally a scheduled task Task Scheduler Menu can be created in the Windows Task Scheduler for the configuration run Then it will be assured that configuration information will be updated in a regular basis These scheduled Tasks can only be created but have to be deleted manually from within the Windows Task Scheduler y E aon x mies 8 verengt titres eros irr eetpoortrtci e a sore jesto Vfailover Login V Failover 2 MovisDemo v Am Action SS instance a Export v c El Home os PORCH e ACtION gt Manage Tasks viailover Task C
34. is will result in non problematic errors when VMware vSphere PowerC is invoked It is recommended that vau set the execution policy to RemateSigned in order to be able to execute scripts and ka hide the errors in VMware vSphere PowercLI Console This can be done by invoking the command Set ExecutionPolicy RemoteSigned from a PowerShell prompt Press Continue to skip and continue install or Cancel to exit the installation Cancel InstallShield MOVIS www movis co at The way you like IT Failover Setting the execution policy can be done after the first run of the PowerCLI Console There an error message similar to the screenshot will occur E Administrator VMware vS5phere PowertLI PS G XProgram Files amp x86 5 UMuare Infrastructure uSphere PowerCLI gt Powershell scripts can be signed with digital signatures and per default only signed scripts are allowed to be executed Detailed instructions about signing scripts are described in the Windows Powershell documentation vfailover can only be executed on dedicated systems where only authorized administrators with the necessary permissions have access to Therefore the vfailover script has no digital signature To allow the execution of an unsigned script it is necessary to set the execution policy within the PowerCLl environment to unrestricted Run as Administrator if UAC enabled This can be done with the following commands and
35. ll be stored and encrypted After that you do not need to specify the User or password parameter for this user For WebGUI operation you have to have a user with stored credentials otherwise no Login is possible 4 2 Operation Mode config This mode is essential for a working vfailover environment Every time LUN configuration changes occur in the vCenter clusters vfailover operation mode config must be executed After a failover failback the operation mode config has to be executed too For a successful configuration all datastores which should be used with vfailover have to be mirrored between the two sites and mirror state must be PAIR from within Storage Navigator Modular or Command Control Interface If mirror state is different operation mode config may not be able to detect the exact datastore to LUN mapping and Truecopy configuration To keep vfailover configuration up to date a scheduled run of vfailover operation mode config at regular basis is recommended This can be done with the Windows Scheduler or any other task scheduling tool on the host s vfailover is installed Sample syntax for operation mode config before 6 6 2 C Program Files WfailoverlScripts failover pst ConfFile vfailover MainCluster User Aaministrator Mode config Sample syntax for operation mode config after 6 6 2 C Program Files WfailoverlScriptsfailover pst ConfFile vfailover MainCluster Mode config StoreCredentia
36. ls true You then will be asked for user name and password 17 as NOVIS uw WP s co at The way you like IT Nm Fatlover After that you can run any vFailover command without credentials within this user context C Program Files vfailover Scripts vfailover os1 ConfFile vfailover_MainCluster Mode config In this case the configuration file vfailover MainCluster properties will be used for the vCenter setup parameters vfailover database configuration will be done for all Datastores which are specified in the properties File with the parameter dsCluster or dsldentifier If a is specified for the parameter dsldentifier all datastores will be stored in the vfailover database settings specified in the properties File can be overruled if parameter Datastore is used in the COMMAND prompt during execution For the connection to the vCenter server the vCenter user administrator will be used After executing this operation mode a password prompt appears in the PowerCLl window VMware vSphere PowertLI 5 5 Release 2 Patch 1 C N Program Files uFailover Scripts uFailover psi Mode config ConfFile Read Credentials of user UMWARE Read Credentials of user STORAGE Connect to vSphere vCenter Gather umfs volumes Gather virtual machinets gt Export config to xml Check umfs volumets gt Create HORCM instances Start HORCM instances Prague Prague Prague Prague G Program Files uFailover Scripts m
37. lusters a MovisCluste n 8 y xm VWREPEPERPSE H R M i LLLLLALLLLLIZLAIXLIIZDEZUXII Ha viennamgmt fa bar niM gt r nkent t earch w 8 4 fr e V Failover D SK gt MowsDemo GR Dast e Ac By Ac Instance B nstance MovisDemo Waiting for user input false Clusters 8 Task Name Backup Task State Ok Mov Name Target Status Details Initiated by Requested Start Time v Start Time Completed Time 1 1 Ep Task No data available in table 3 History Name Target Statut Details Initiated by Requested Start Time Start Time Completed Time Showing 0 to 0 of 0 entries MOVIS af p WW Fi ww movis co at The way you like IT o gt gt Failover 7 3 2 WebGUI Planned Failover Planned Failover can be initiated through the WebGUI Either an Maintenance Activity planned or an Disaster Recovery Unplanned can be initiated First select the Datacenter and the active datastores are shown which may be switched to the other datacenter All datastores which are selected will be switched to the other site after Start button is pressed gt Failover Failover Type Maintenance Activity planned Disaster Recovery unplanned vfailover 7 0 Web Application 2014 2015 MOVIS EB WD wew movis co at The way you like IT 38 Failover After vFailover initialization has finished the failover task has to be confirmed by pressing
38. n 7 0 1 www vfailover com Copyright by MOVIS Solutions 2014 2015 all rights reserved Partner Hitachi Data Systems 29 a i NOVIS um www movis co at The way you like IT _ Fatlover 7 1 2 Instances Additionally a new instance properties file may be created in the login window An existing instance may be edited after login with button Edit at the top These settings will then be saved to the vFailover Conf folder All necessary parameters are shown in the WebGUI and may be filled out if used Pile E3 W vfailover New Instance Wh viennamgmt 8080 vfailover webapp instance nev E Q search b 4 e A e F wfailover Login T e New Instance Instance Name J CCI root folder CAHORCM etc Vendor HITACHI Set S VOLs invisible TRUE 9 FALSE Set S VOLs invisible with backup TRUE FALSE Rescan Vmfs Option e SERIAL PARALLEL No of parallel VMs to be registered sp Remove ESX server on failure YES e NO Object prefix after disaster recovery Recovered by vfailover i Exclude RDMa Configuration file to 9 exclude LDEVs zl MOVIS 30 L WD ww movis co at The way you like IT Nm Failover 7 2 WebGUI Overview 7 2 1 WebGUI Dashboard After logging in an overview about the selected vFailover configuration MovisDemo will be displayed Information about the Last Backup Clusters Hosts will be shown Boot Order Settings and VM Sta
39. other methods several third party products and VMware vCenter Heartbeat to replicate vCenter server to a secondary site and make it available in a disaster scenario As long as vfailover runs on its own management servers there should be no impact to vfailover operations Because of disaster recovery is a complex topic each individual solution should be verified by a consultant before starting a vfailover implementation 2 20 VMware Software Requirements The following VMware software versions are supported VMware vSphere vCenter 4 0 4 1 5 0 5 1 5 5 ESX ESXi 4 0 4 1 5 0 5 1 5 5 PowerCLIl 4 0 4 1 5 0 5 1 5 5 a i NOVIS J RE Si ww movis co at The way you like IT Nm Fatlover 2 3 Hitachi Data Systems Storage Arrays The following HDS storage systems are supported Hitachi Thunder 95 0V 9580V Hitachi AMS 200 500 1000 Hitachi AMS 2100 2300 2500 Hitachi TagmaStore Universal Storage Platform 100 600 1100 Hitachi TagmaStore Network Storage Controller 55 Hitachi Universal Storage Platform V VM Hitachi Virtual Storage Platform IP and FC based Command Device support G1000 Hitachi Unified Platform VM Hitachi Unified Storage 100 Family HUS 110 HUS 130 HUS 150 2 4 Hitachi Data Systems Software Requirements The following HDS software products are required Recent Storage Array Controller Firmware Software Hitachi Truecopy synchronous replication Hitachi Command Control Interface 01
40. r wennamgmt Of vfalover Login LU TE 25 MovisDemo v e rc TEE instance Datastores 5 san vfailover 0 En T y wf san vi akrver 0 wviennamomt f vfallower Login WFailover c EL Datastore san valor 0 Name san vfailover 0 Used Space 27GB 39GB Connected Hosts 2 Virzual Machines Templates 2 Provisioned Capacity 1GB Subscription 2 6 Version 5 60 Extents 1 Replication State Virtual Machines Datartores a Datastore a Status Extent Data Center Serial Ldev Storage Pod Backup State Horcm State Replication State san wfatover 0 wv 0 vienna 83014974 400 vFailoverDSC v v PVOL_PAIR SVOL PAIR Datastore Status Extent Data Center Serial Ldev Storage Pod Backup 5tate Horcm State Replication State T 1 Uu El 5 MovisDemo Datastores san vfailover 0 n 9 35 ros san val wer D Name son vfailover o Used Space 27GB 39GB Type VMFS Connected Hosts 2 Virtual Machines Templates 2 Provisioned Capacity 1GB Subscription 2 Version 5 60 Extents 1 Replication State gt Virtual Machines Q wr Virtual Machine Status Label Type Data Center Serial Ldev Datastore Backup State Horcm State Replication State Application Server 2 v Festplatte 1 FLAT Vienna 82014974 400 san_Mailover_ wv wv PVOL_PAIR SVOL_PAIR MailServer wv Festplatte 1 FLAT Vienna 82014974 400 san_Mailover_0 wv v PVOL PAIR SVOL PAIR MailServer v Festplatte 2 FLAT Vienn
41. r 1 Application Server 2 Application Server 3 Application Server 4 Application Server 5 MailServer MailServer MailServer Virtual Machine Status vFailoverDSC 3 true Used Space true automated 420 gt Virtual Machines Lobel Type Data Center Serial Ldev Dotostore Backup Stote Horcm State Replication State Festplatte 1 FLAT Vienna 3014974 401 san vfailover 1 v v PVOL PAIR SVOL PAIR Festplatte 1 FLAT Vienna 83014974 40 san_vfailover_0 wv v PVOL PAIR SVOL_PAIR Festplatte 1 FLAT Vienna 3014974 401 san_vfailover_1 wv wv PVOL PAIR SVOL_PAIR Festplatte 1 FLAT vienna 3014974 401 san_vfailover_t wv wv VOL PAIR SVOL PAIR Festplatte 1 FLAT Vienna 83014974 401 san vfailover 1 v v PVOL PAIR SVOL PAIR Festplatte 1 FLAT vienna 3014974 400 san_vfailover_0 v v v PAIR SVOL PAIR Festplatte 2 FLAT Vienna 3014974 401 san vfailover 0 v v v PAIR SVOL PAIR Festplatte 3 FLAT Vienna 3014974 400 san_vfailover_0 v v PVOL PAIR SVOL PAIR Label Type Data Center Serial Ldev Datartore Backup State Horem State Replication State 34 MOVIS Lg um The way you like IT www movis co at __ allover 7 2 5 WebGUI Datastores View Information about Datastores will be shown there The extents StoragePods LDEV and Replication Status will be shown If Virtual Machines button will be clicked in the Datastore Frame information about the virtual machines running on that datastore will be shown y Wf sen vfalove
42. rameter in the config file VCenter configuration has to be cleaned up manually delete orphaned objects after unplanned failover operation e Based on user input storage will be treated as available or not availabe e Available Swap storage replication horctakeover of datastore and RAW Device LUNs at Storage level Truecopy mirrors volumes will be failovered Like in planned mode e Not available Make replication volumes read and writeable on second storage subsystem Enable write access to LUNs at the remaining datastore remove write access from primary volumes if still available e Rescan HBAs and VMFS Rescan of all ESX i hosts to refresh vCenter LUN configuration e Resignature datastores Datastores may be recognized as Snapshots at the other site As the base signature values have changed other storage subsystem resignature will be executed to write a new signature onto the datastore This operation involves another vmfs rescan e Rescan HBAs and VMFS Rescan of all ESX i hosts to refresh vCenter LUN configuration e Register virtual machines Virtual Machines will be re registered in the vCenter e Reconfigure virtual machines o Raw Device Mappings and virtual disks will be added back to the Virtual Machine configuration o Move virtual machines into its folder o Set custom attributes o Reconfigure virtual distributed network switch configuration e Reconfigure cluster to rebuild all the virtual machine se
43. ripts gt m 24 TTNOVIS www movis co at The way you like IT Nm Fatlover 4 7 Operation Mode vcenter Operation Mode vcenter can only be used if virtual center server is a virtual machine which resides on a mirrored datastore Only and all vcenter related VMs should be on that datastore e g server where vcenter db is installed if not the same machine Operation mode vcenter can be used in case of a site ESX i host storage array failure or in case of a planned failover With this mode failed datastores and virtual machines will be brought online at the remaining site In this mode you need to specify a user account which has root permission on one of the remaining ESX i hosts Because in case of no virtual center server is available switching tasks have to be done on one of the ESX I hosts Sample syntax for operation mode unplanned C Program Files vfailover Scripts vfailover os1 ConfFile vfailover_Maincluster User root Mode vcenter DestinationDatacenter Hemote Datastore vcenter In this example the Datastore called vcenter will be switched to the remaining or remote Datacenter All other systems won t be affected After executing the vfailover operation the password for user root has to be entered for a successful connection to an ESX i server Before the takeover will be executed you have to choose the ESX i host and answer a few questions Then a summary of the affected datastores and virtual
44. s with Truecopy replication setup for datastores PowerCLI VMware scripting interface for virtual infrastructure vfailover Script environment managing automated failover between sites in the virtual environment 1 3 Integration Identify datastores which should be protected between sites Setup Truecopy replication for datastores which shall be protected Provide access to Truecopy secondary volumes to all ESX i hosts in the VMware high availability cluster s Install Hitachi Raid Manager software and VMware PowerCLI at the vCenter Server s or a dedicated management host which remains available in case of disaster and has network access to vCenter server Present Hitachi Command Devices to either vCenter server s or dedicated management host for vfailover Setup vfailover parameters Storage vCenter and Site setup Run vfailover configuration Initiate failover test with non production datastore a i NOVIS J uw WP s co at The way you like IT Failover 2 System Requirements 2 1 VMware Environment vfailover supports 3 different types of VMware vSphere data center configurations e One VMware vSphere HA cluster with one vCenter server WAN LAN y i 5 La b vSphere vCei m Y Cluster S e nt VMware ESX Replication Technology e Two VMware vSphere HA clusters with one vCenter server VMware ESX Cluster B Replication Technology Replication
45. stions on screen and answer them correctly with yes no dontknow E 3 vernsngnt 3 7et n E Question Question F verano f z 8 tX e Question 41 w NOVIS EE The way you like IT IA Fatlover Then type yes again to proceed and initiate the failover 6 9 06 x e Q Search vfailover Login Question Proceed as MOVIS The way you like IT No movis co at 42 Nm Failover 7 3 4 WebGUI Recover vCenter On the Login page login to one of the ESXi hosts on the remaining site which is still running and has access to the datastore mirror S Vol where vCenter server is stored Make sure that you have root permissions to the ESXi host That is used for bringing a vCenter Server and all the VMs at the same datastore online on the remaining site after an unplanned outage This is possible if the vCenter Server and its database server are on the same datastore which is mirrored with Truecopy or HUR Ji tor oan LJ viennamgmt 7 arct f e f e W vfallover Login Eai NEW INSTANCE ailover ign ir Server ESX Host prague movis local Jot gt Contact us About Copyright by MOVIS Solutions 2014 2015 all rights reserved 43 TIONIS www movis co at The way you like IT Nm Failover Press Start to recover vCenter server y t Recover vCenter viennamgmt F wfalover Login WFailover E Hom
46. the yes button If Browser will be accidentally closed it can be started again and the ongoing task status will be displayed g iu vfalover Login Question oceed 39 es I NOVIS J BP wmoviscoat The way you like IT Nm Fatlover 7 3 3 WebGUI UnPlanned Failover Unplanned Failover can be initiated through the WebGUI Select Disaster Recovery Unplanned First datacenter has to be selected then active datastores will be displayed Choose all datastores that should be switched Then Start Button has to be pressed yy eon J o M c e viennamamt 80 talnove ebapp main MovisDemos vf allove riweb app i ntentj action io Q 5earcr T 9 4 A W vfallover Login WV Failover Home Action MovisDemo v Action gt Manage Tasks d Dashboard vfailover Task gt Failover Backup State Check Task Scheduler e Action gt Inst T Vienna Select datastore s nf D ut san vfailover 0 san wfailower 1 g m 2 san vfailover 2 Failover Type Maintenance Activity planned 8 Disaster Recovery unplanned vfailover 7 0 Web Application 2014 2015 40 mMOVIS Lim WWE S ww movis co at The way you like IT Failover After vFailover initialization has finished some questions have to be answered Depending on the failed components Please follow the que
47. ttings that have been before failover e User can decide if the script should power on the virtual machines based on their previous state or as defined in the BootOrder File or if the virtual machines should stay powered off 23 a ITICON IES J RE Si ww movis co at The way you like IT Failover 4 6 Operation Mode repair Operation mode repair checks all the Virtual Machines in a cluster after an unplanned failover for custom attributes resource pool association folder association and dvSwitch configuration If there are any paramters missing they will be reconfigured ATTENTION You must have valid configuration files Folder vfailover db from the point of time before the unplanned failover was done Do not run the script with mode config after an unplanned failover if you want to use the repair mode Sample syntax for operation mode repair after v6 6 2 C Program Files WfailoverlScripts Failover pst ConfFile maincluster Mode repair Sample output for operation mode repair Mode repair creates a list of all VMs and reconfigures the VM parameters VMware vSphere PowertLI 5 5 Release 2 Patch 1 PERS ITUR TUBE Files vFailoverScripts gt vFailover psil Mode repair ConfFile Read Credentials of user UMWARE Read Credentials of user STORAGE Connect to vSphere vCenter ucenterdh Application Application Serv MailServer Deru Deru Deru C2 Program Files vFailover Sc
48. tus Information are available as well In the left Sidebar Instance Name Dashboard Action Instance Task and History can be selected Backup and Failover tasks can be started within the Action menu From the Instance selection different views Clusters Hosts Storage Pods Datastores Virtual Machines may be chosen Every operation failover backup status will be started as task and information is displayed in Task menu History shows a task history and links to log files y a Dashboard x viennamgmt J vf ailo ve jet yt IM W vfallover Login INSTANCES V Failover Your instances v 2 MovisDemo v Fe Dashboard t db Sum nary a QE Acti Clusters E Hosts on Storage Datasto Tasi co virtual Michines Last Bacup 0 03 2015 18 58 49 Hist iz Boot Qrder ESX Host Power State Boot Priority Virtual Madhine Powered On on ping time out 60sec E Applicationliberver 3 prague movis local MailServer vienna movis local P Powered On Wait on ping time out 60seq Wait on ping time out 60gPc Application ferver 2 prague movis local lo Powered off Application Server 5 prague movis local B Powered Off Wait on ping time out sec prague movis local B Powered Off Wait on ping time oug Application Wait on ping time gut 60sec Application S prague movis local B Powereg Sift 9999
49. verB two VMware vSphere HA cluster with one vCenter server HAClusterA myVMwareClusterA HAClusterB myVMwareClusterB vCenterServerA myVSphereServer vCenterServerB two VMware vSphere HA cluster with two vCenter server HAClusterA myVMwareClusterA HAClusterB myVMwareClusterB vCenterServerA myVSphereServerA vCenterServerB myVSphereServerB Configuration files need to be created for each VMware vSphere HA cluster configuration or each consistency group that builds a unique block out of some data stores and or raw device mappings 14 a i NOVIS um co at The way you like IT Nm Failover Sud S vfailover Bootorder Configuration It may be essential to define a specific boot order for the virtual machines to make sure the environment is working correctly after a failover failback operation For example Windows Domain Controllers must be the first systems which are up and running because most of the other servers depend on Active Directory Domain services Therefore it is necessary to define a boot order for the virtual machine startup process This will be done by specifying the Custom Attributes for Virtual Machines that have to boot before others for example Active Directory Domain Controllers LDAP Servers vPriority Boot Order Priority Ascending Lowest number first VMs with same priority are processed as they come if If empty or custom attribute not exists vPriority 9999 vWait Seconds to wait
50. we eecceccecsecsscssessessesssssssessssssssssssusssssssassasssssessisssssssessansisassissssssssissssassassississsssussusstsansiussssissiessssussusaueaeetsecsieaneeeee 8 ale WTS Ge io 8 2 2 ae Ea qe M 9 CANET 00 E Rem 9 322 VMW e POW CUC angur e E one EE EAE EES eE E W 9 SN E SAUL 4 210 RR 10 UU EE OS OS COO ED Nm 11 ee VN CT OC ls ONIN AN o ANTE 15 3 2 6 vfailover Configuration File Parameter CTGNO occccccccccsssssssssssesessssessssssassssssssssssssssssssssassanssssssssssssessassansanssessearsaneaneseeseeees 16 VEAILOVBRIOPEBANMO D scere E uM UM M 17 4 1 ee ua lgaus v A 17 4 2 aos we sbprse dci RR RR T UU TIT 17 4 3 eoi we De i E E 19 4 4 oce MN ebd b so EEEE 20 4 5 e owe MEUS E Ss NN RR 22 4 6 PEBATIENTIDBESSEPAIBE etat UDec EDU EDU MU D MEE M 24 47 OP ON ee E 23 VFAILOVER FRAMEWORK BN m 26 PNA TR eeepc NIE Mu M uu I 27 gredi m 29 Me VI ANGI T X 29 ik eee ere ene 29 FX PI 1a E EAE EE E AAA 30 rs A CUE dn 31 7 214
Download Pdf Manuals
Related Search