| Time | Item | Who | Notes |
|---|
| Network Changes | Tim Whitlock (Deactivated) | - Changes to the VLAN structure will require configuration changes to the VMs.
- Extra network interface on internet side (N3 would be unchanged?)
- Extra routing table entries
- Exact details unclear at the moment.
|
| | VM Testing configuration with network changes & testing | Tim Whitlock (Deactivated) | - Fully testing the VMs will not be possible for them all due data feeds required.
- Will need to confirm VMs function as expected and where possible check data flows.
- Internet websites should be fairly straight forward. N3-internet proxy, Redhat license manager will be harder.
|
| | Backup solution | Tim Whitlock (Deactivated) | - Should be possible to verify functionality
- Truly testing the "slow" backups will only be possible when the systems are live due to the way the data changes occur.
- We will start with managed backups so we can ensure any issues are ironed out before possibly taking over the backup management.
- Need to ensure we have documented methods for asking for backup changes, restores etc.
|
| | Backup testing before during and after migration | Tim Whitlock (Deactivated) | - Further backup testing will be required after we are live to verify all is working as expected.
- In particularly will need to do full test restores of patientview and healthshare to verify that the backups work and are complete.
|
| | Migration Plan | Tim Whitlock (Deactivated) | - AIMES "are working on a migration plan"
- We would anticipate doing some test runs of the process with all the VMs and verifying that they have transferred correctly and work.
- If changes to the vlan are required we will need to have a documented change list for each affected VM that should be applied to get it working. This change will need to be tested as well.
|
| | | | |