jbroussard Posted June 30, 2003 Report Share Posted June 30, 2003 There is a fantastic setting for controlling whether or not a backup will take place in the client portion of a script's settings that checks the throughput speed and will not run the backup if the speed is too low. However, this logic falls apart if the script is a scheduled recycle backup. When a recycle backup is run, the backup is reset first, then the throughput is checked. The end result is that when the speed is too low, the backup is completely erased, then the recycle backup doesn't run, leaving you with an empty file. It would be great if the throughput was checked prior to performing any operation of the backup (espeicially before the backup is reset for a recycle backup) instead of the way it is now. Link to comment Share on other sites More sharing options...
Mayoff Posted June 30, 2003 Report Share Posted June 30, 2003 We could do something like this, but that would be a problem if the script contained 100 clients (which is not unusual). We recommend having alternate backup sets, so if you recycle one set, you have another to access if needed. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.