2017-02-15 Aimes Status Update

Owned by Tim Whitlock (Deactivated)
Last updated: Jan 22, 2018
2 min read

Current Status

• We have completed the physical build of the HA infrastructure.
• We have built the Veeam Hypervisor and are in the process of building the Veeam VM infrastructure.
• We have connected the Veeam backup server to the Vcenter management VLANs on the OLD hypervisors.
• We are expecting the DELL engineer on site to configure the SANS WC  , in the meantime we are building the Vcenter environment on local storage.
• The firewalls have been configured for local support access.
• There are a number of streams of work in this project, the most immediate is getting the Veeam backup environment established.

Future Work

• Establish and test backup of the OLD system hypervisors (expected WE ) 
• DELL to configure SANs (expected WE )

  • Establish a basic backup of all existing VM’s with RR (expected WE  )
  • Aimes to establish RDP server for RR to access infrastructure (expected WE  )
  • Aimes to test restore of VM’s to new infrastructure (expected WE  )
  • Aimes/RR to agree Migration plan (expected WE  )
  • Aimes/RR to test Migration plan (expected WE  )

• Migration, when RR are happy with the plan of actions

RR Actions

• Agree with Aimes how they want to control the cutover of backups from IDERA to VEEAM
• Identify any VM’s they have static data, that can be migrated early.
• Review Migration Plan
• Test Migration Plan, test migrated servers.
• Set a migration date.

Migration Considerations

• Support of the Vcenter infrastructure will be via a Windows RDP server (max 2 concurrent users) from the N3.
• A migration Test will be undertaken to restore all VM’s to the relevant hypervisors. This will need RR support (see below)
• There will be a freeze on all system changes after the test migration.
• All VM’s will maintain the current users facing IP’s. (this will mean Migration testing will be internal only)
• It is expected that all VM’s will lose the IP information on migration (different MAC addresses) and will need to be re-addressed by RR, via the Vcentre Console access.
• All VM’s will move to different Backlan VLAN numbers and will need amending on the Vcentre systems (RR). This will be new Backlan VLANS for the WWW facing systems.
• Migration test restores will be timed to provide an estimate of actual migration downtime.
• Migration test VM’s will be deleted after the test.
• RR to test all test VM’s have internal access as expected, redhat licencing works etc.
• Aimes to migrate existing firewall rules to new firewalls.
• Firewalls will move to the existing external IP addresses on Migration (Arp issues)
• All above actions will be documented after the test migration.
• Aimes/RR must sign off the migration plan and set the date for migration once the testing is complete.

ALL DATES ARE ESTIMATES ONLY AND MAY CHANGE AS ISSUES DICTATE.