Pre-Everything

• • Check Patch Level on both VM5 Hosts
  • Ask AIMES about Firewall/Switch Firmware Updates
  • Ask AIMES about access to DRAC + SAN Management Interfaces
  • Check Encryption has been enabled on SANs
  • Check Encryption has been enabled in Veeam
  • Confirm with AIMES we want them to manage the backups
  • Ask AIMES about backup security (in particular potential for access to PID via Internet)
  • Ask AIMES about reporting/alerts from Veeam.
  • Ask AIMES if it is possible to have read-only access to Veeam console.
  • Ask AIMES (again) for a copy of the Firewall rules.
  • Check whether there is a grace period for the RedHat licences as we move between Hosts.
  • Ask AIMES about Cisco "FirePower" functionality - Note: I understand that several of the features require a licence to enable but it may have some capabilities "out of the box"
  • Ask AIMES about future remote access - see 
    Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Check for Cisco Problems - https://www.theregister.co.uk/2017/02/03/cisco_clock_component_may_fail/
  • When/How are we getting the VMWare / Veeam Licences. (Support website accounts etc.).
  • Find out how many Windows VMs they will be setting up. There might be a spare one or two.
    
    

Pre-Migration Testing

Migration of VM from VM5 to VM6 Cluster

• • Test that VMs boot and do some checks that the data is not corrupt.

Test how VMotion works

• • Check if VMs can make use of both VMHosts in normal operation
  • Check failover works.

Test Backups

• Find a way to simulate modifications to HealthShare and PV for incremental backups
  • HealthShare: Processing about a day's worth of assorted files should do it, though we need to think about the message and journal purge activity too.
  • For PV I think what we would have to do is modify PVOut in HealthShare to collect PV2 XML files and then write a local web client to submit them. This would require PV Web and PV DB to be able to communicate.
  • Hmm... I wonder if there's any way you could do one or both of the above by having it replay or undo Transaction Logs to generate the activity.

RedHat Licencing

• Check how this is configured in a cluster
• Check VM Failover works
• Check Failover of the RedHat LM itself works.

Estimate time required for migration

Develop a back out plan

During Migration

Setup Holding Pages

• • For the Internet side see Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Make sure sites/suppliers/users have been notified.

Disable PV Output Queue

Post Migration

Check machines are (or can) able to operate successfully

• • Document Firewall Requirements

Uninstall R1Soft/Idera from VMs