

If you’re gonna use it for backups, you should ensure it’s only syncing in one direction. If it’s set up like normal (where it functions like Dropbox and syncs changes from any device to all your devices), if your data is corrupted or something on one device, it’ll be synced everywhere. You can also configure it to store a certain number of revisions (which you could use either instead of one-way syncing or in addition).
Also, if you’re gonna use it for backups, it’d be a good idea to store your data offsite somewhere (whether that’s by storing your data encrypted at some cloud provider through a VPS/whatever or at friend’s/relative’s place or something, that’s up to you).
He should’ve done something like that on top of a delay in the script to prevent it from potentially being associated with the deletion of his name in AD (assuming the company backs stuff like that up, which is questionable since one dev was able to do all this lmao).
The other issue is that the computer responsible for the infinite looping was associated with him. Since he had seemingly unlimited access to everything, should’ve either plopped it on some shared device with a separate user or just configured it to also delete itself once it noticed the AD name being gone.
Anyway, this entire scenario is both hilarious and makes me never, ever want to use Eaton products.