Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

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.

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

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
      Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Make sure sites/suppliers/users have been notified.

 

Post Migration

Check machines are (or can) able to operate successfully

    • Document Firewall Requirements

 

  • No labels