Hard drives do go bad. Physically remove the hard drive, connect it to a PC & use Norton Ghost to make an image. Burn the image into another hard drive & install/test operation. Leave tho old one on the shelf if you want at that point. You'll have the old drive (ready to plug in & go) plus a VERIFIED image on your server this way. There are only a few folders that contain all the programs, direct mode, hdd operation, tbackup, there is another that the techs install ladder update files in, another for gantry loader programs if you have a multiplex.
The toolcall is indeed wrong. However, I remove this in the file after post because I simple don't need it as I call my tool in my Mazatrol program. I have changed the same booleans in my post from your notes, but received no errors. Looks to be alright though. What I think is you need to adjust the post for each machine individually. Backup and Restore Azure database to and from.bak file. It would be very useful if we can move or copy Azure databases with the flexibility we can do this with regular SQL Server database - with a full backup file. You have left! (?) (thinking) Flag idea as inappropriate Restores to SQL DB Manages Instances will be supported.
We keep a good image that has been verified by burning a drive an physically testing it. You can reburn that image & add in all the folders that contain programs, etc (from your regular scheduled backups) in a couple of hours. Drives from Mazak aren't cheap plus don't come with all your programs on them.On a side note:If your backups are working great, you should be able to restore a program that was ACCIDENTALLY ERASED that is more than 24 hours old. I've accidentally erased programs before & been able to restore from a recent backup. Downside of the frequent backups is that when they're going on in the background it can really bog down the built in PC, since it doesn't have much computing power.