Dustin.Loftis Posted April 14, 2008 Report Share Posted April 14, 2008 Hello there. We are having a problem with Retrospect SBS, Multi Server and Single Server, all version 7.5, all with the latest patches and drivers. We use SATA hard disks to run our clients' backups, generally using two disks and swapping them on and offsite. The problem I am encountering is this: BackUpSet_A is the drive in the system. It has only a few GB free, but backups are not failing; grooming is working. I remove BackUpSet_A and insert BackUpSet_B. For reference, let's say BackUpSet_B is half-full. It really doesn't impact this scenario either way. My backup scripts are set to back up to both drives, so that they will back up regardless of which drive is in the system. The media timeout is set for two minutes, so the scripts trying to back up to the off-site set will timeout when it is not found. The problem is this: When the script tries to back up to BackUpSet_A, it initiates a groom. The grooming system attempts to locate the missing backup set, and prompts the user to insert it. This dialog does not time out. It also prevents all other scripts from running. It even keeps Proactive Backups from occuring. The groom dialog will still be sitting there a week later when I swap the drives again. The only solution that will get the backups running when the offsite set is missing is to report the set missing/damaged, or forget it completely. Is this something that can be addressed in an update? If the media sets are supposed to time out, they should time out regardless of whether grooming is needed or not. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.