How To Handle Down CMMs?

Thanks for the advice. That is what I figured we would have to do in the event our CMM goes down. 

I never was able to get a weekly or monthly cleaning of my CMMs like I planned to. I wanted to schedule a day like every first of the month and dedicate that day to backup the CMMs, cleaning all surfaces like the granite, monitor, keyboard, probes, and even the scales but I never got around to do that. I only clean the scales if there is a reference error when homing. 

I have 5 batch files that backup all my programs, one for each night of the week, so I have 5 days of backup on a second drive in the PC and on the PC for the other CMM.  This is in addition to the nightly backups that IT runs (I don't trust IT)

Do all of your CMMs use the same pcdmis version? My CMMs range from 2016 to 2021 and my offline seat is 2019.

I have 2 CMMs, I save backup each other every month. And save programs to the D drivers every week.

We have 2015.1 2019.2 and 2020.1 ( Sister plant next door , share the  same intranet)

Ours are the same version 2023.1. They also have 2013, 2015 and 2018 installed on them and I can launch any one of them whenever I want. One at a time. Our workstations have their desktops, documents, download, etc folders mapped to the server. PC-DMIS probes, programs and other settings files are mapped there as well. The entire server is backed up daily on to one of four external drives swapped out every Monday. Our PCs don't have anything on them except the programs needed to run on them. I don't just program and operate the CMMs. I am IT.

I program everything in V3.7, the Global uses 2016.  BUT, the only thing I have to watch for when migrating the programs is round slots and square slots.  Nothing else ever has any issues.  There are some minor things that may or may not need to be tweaked from machine/version to machine/version, but those are mostly how AUTOMOVE (avoidance move) works.  Center of probe to edge of probe difference between machines/versions, and it only needs tweaking in tight spots.

I program everything in V3.7, the Global uses 2016.  BUT, the only thing I have to watch for when migrating the programs is round slots and square slots.  Nothing else ever has any issues.  There are some minor things that may or may not need to be tweaked from machine/version to machine/version, but those are mostly how AUTOMOVE (avoidance move) works.  Center of probe to edge of probe difference between machines/versions, and it only needs tweaking in tight spots.