I'm using Backup Exec 9 on this particular server. It used to backup to a robotic library that had two drives. The drives have both failed. I've attached an external drive to another server and shared it out. Created a removable Backup-to-Disk device to the external drive. I used the default parameters for BTD folder (1GB size, etc). Modified the backup jobs to backup to the new BTD device instead of 'All Drives' just to make sure they would go there. Everything seems to be working... except... Back in the day when the tape library was working, BE saw that the library had two drives and would simultaneously run two jobs at once. All jobs (about 6) were set to Medium priority and scheduled for 12:01am. It didn't matter which jobs ran first or last as long as they all ran during the night. Now, what's happening is this... (and it actually may have something to do with the fact that I force-started all the jobs by right-clicking them as choosing 'Run Now'). BE changed the 4 jobs that I'm dealing with from On Hold to Queued. I think it was at this point that the Elapsed Time counter started for all the jobs. Then it started one of the jobs. Several minutes later, that job changed its status to Loading and then back to Queued. Another job started. Then that second job did the same thing. BE keeps doing this with all of the jobs. Finally, one of the jobs finished and now there are only 3 jobs bouncing around. They look like they're backing up normally except for this weird behavior. What I've noticed, when looking at the Backup-to-Disk folder (in Windows Explorer) on the external drive is that last file in directory (for example B2D000150.lck) keeps changing it's name after the current job changes its status to Loading. The filename keeps incrementing through all of the previous versions of the .bkf files (for example B2D000023.lck, B2D000024.lck, B2D000025.lck, etc.) until it reaches the highest numbered .bkf file. At this point, the job changes from Loading to Queued and another job will resume where it left off. Another problem that this creates (and again it could just because of the 'Run Now' in this instance) is that the Elapsed Time for all of the jobs are basically the same. This won't help me if I need to actually alter the jobs' scheduled start times so they don't overlap and start doing this again. What is going on here and how can I stop this behavior? Although everything is backing up, it's taking the backup to run much longer than it should. Any suggestions? Thanks.