Hello,
I've just run into a Micros RES 3700 server which is filling up its disk space with database backups during nightly maintenance. The directory is D:\Micros\Data\Database\Backup (I may have gotten some pathname components mixed up, he says sheepishly), and the backups come in sets of two files, where the DB backup filename is of the form micros_MM_DD_HH_MM.db and has a similarly named .log file. The folder contains several months of daily backups, and the first backup in the folder, chronologically, has an additional ".good" file extension.
For some reason, whatever nightly script that does the voodoo that it does, is no longer deleting the older backups, and I'd be mildly curious how to restore this happy behavior before I'm buying petabytes of disk space to satisfy the POS beast -). Is it possible that that first ".good" backup is confusing the script?
I would be very grateful for any hints, tips, insight (or large disk drives)! Thank you!
AN.
I've just run into a Micros RES 3700 server which is filling up its disk space with database backups during nightly maintenance. The directory is D:\Micros\Data\Database\Backup (I may have gotten some pathname components mixed up, he says sheepishly), and the backups come in sets of two files, where the DB backup filename is of the form micros_MM_DD_HH_MM.db and has a similarly named .log file. The folder contains several months of daily backups, and the first backup in the folder, chronologically, has an additional ".good" file extension.
For some reason, whatever nightly script that does the voodoo that it does, is no longer deleting the older backups, and I'd be mildly curious how to restore this happy behavior before I'm buying petabytes of disk space to satisfy the POS beast -). Is it possible that that first ".good" backup is confusing the script?
I would be very grateful for any hints, tips, insight (or large disk drives)! Thank you!
AN.