Rebuilding a Best Practice Virtual Machine

Draft

---

Friday

Prepare for rebuild

Tuesday

Upgrade hypervisor to XCP-NG

Wednesday

Upgrade VM to newer Windows Server version

Thursday

Install previous software

1

Take a snapshot of the old VM

2

Stop and disable services that could be providing results, referrals, research data, or any other medical or marketing software

TIP

Common software to be stopped includes, but is not limited to

Service name	Service provided	Company
mqscheduler	Pathology	Medway
FetchDaemon	Pathology	Sonic Healthcare
CAPRICORN	Referrals	Medical Objects
Isaac Connector	App functions	Medinet
Automed Launcher	Just about everything	Automed Systems

3

Take a backup of the BP database on the old VM

Picture guide

Ensure that "Complete backup" is selected
Ensure that "Uncompressed file" is selected

If you have enough space on the hypervisor, you can create a temporary migration disk to hold the BP backup

Ensure that the size is at minimum the size of the existing database

You may wish to name this disk, to ensure its purpose is known

4

While the BP database is backing up, prepare the new VM to accept the database

Increase the storage attached and expand the C drive of the new VM

Picture guide

DANGER

If you have a recovery partition, as pictured below

Perform these steps to remove the recovery partition

reagentc /disable
diskpart
list disk
select disk <x>
list part
select part <y>
delete

Replace <x> with the number corresponding to the main disk, typically this will be 0

Replace <y> with the number corresponding to the recovery partition, highlighted below

Update the hostname to the format XXXX-SRV-BP-01 (XXXX being the )

Picture guide

Add the new VM to the Myhealth - SRV TeamViewer group

Picture guide

Enable the Myhealth IT scheduled tasks

Picture guide

If an SQL Server license is required, activate it

Picture guide

5

Power off the old VM, and increase the memory allocated to the new VM to 24GB minimum

WARNING

Take a snapshot, now that all the basic setup is done - name it "Pre-restore"

6

Restore the BP database backup on the new VM

Picture guide

7

Verify that the NASH and B2B device are still valid

8

Shut down the old VM, detach its disk, and attach it to the new VM

Video guide

WIP