I use SyncBackPro in a production environment with a non-existent IT budget and find that it suits my needs well. I do network backups of 5 servers to a Drobo S every night and server system state / exchange backups on an alternating schedule.
It would be helpful to have an elastic scheduling scheme to have backups start when another finishes instead of a firm start/stop time/date. Right now I have my quickest backups taking up an hour of schedule time to account for a sudden arrival of a lot of data, when most days that backup takes only 5 minutes. That's a lot of wasted time. This would greatly reduce idle time and increase server efficiency.
Thoughts?
It would be helpful to have an elastic scheduling scheme to have backups start when another finishes instead of a firm start/stop time/date. Right now I have my quickest backups taking up an hour of schedule time to account for a sudden arrival of a lot of data, when most days that backup takes only 5 minutes. That's a lot of wasted time. This would greatly reduce idle time and increase server efficiency.
Thoughts?