UltraVersion21
MIS
Hey,
We are using BackupExec 7.3 and lately it has begun to take a very long time to perform the backups (it varies anywhere from 10 hours to three and a half days). My client doesn't always check on the backup, and so it was allowed to run this long. However, these backups do register as successful. The interesting thing is that it consistently slows down when backing up. I will show you the end of the log (the backup of our last drive where the problem occurs)I have taken the most extreme example.
----------------------------------------------------------
Media Name: "Media created 02/04/02 01:00:06 AM"
Backup of "F: Data"
Backup set #4 on storage media #1
Backup set description: "Full Backup 0001"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 2/4/02 at 2:14:52 AM.
Drive and media information from media mount:
Changer Name:
Drive Name: Seagate 1
Media Slot: 0
Media Cartridge Label: MC000004
Targeted Media Set Name: Media Set 1
File "(deleted to protect client).wpd" in use - Backed up.
Backup completed on 2/8/02 at 1:33:23 PM.
Backed up (deleted to protect client) files in (deleted to protect client) directories.
1 file was in use
Processed (deleted to protect client) bytes in 56 minutes and 15 seconds.
Throughput rate: 42.3 MB/min
Software compression ratio: 1.3:1
----------------------------------------------------------
Job ended: Friday, February 08, 2002 at 1:34:24 PM
Job completion status: Successful
-----------------------------------------------------------
From her it simply picked up the next scheduled backup on 2/8/02 and performed that one for about a day and a half. It is curious that it's start and end are accurate, but it's processed time (in all of these cases) is 56 minutes and xx seconds (with xx always falling in the low to mid teens). However, a successful backup (and a normal one) can take two-plus hours (and it records this time accurately). If anyone has any ideas as to what could even begin to cause such a bizarre phenomenon I would be thrilled to hear from you. Thanks,
jason
We are using BackupExec 7.3 and lately it has begun to take a very long time to perform the backups (it varies anywhere from 10 hours to three and a half days). My client doesn't always check on the backup, and so it was allowed to run this long. However, these backups do register as successful. The interesting thing is that it consistently slows down when backing up. I will show you the end of the log (the backup of our last drive where the problem occurs)I have taken the most extreme example.
----------------------------------------------------------
Media Name: "Media created 02/04/02 01:00:06 AM"
Backup of "F: Data"
Backup set #4 on storage media #1
Backup set description: "Full Backup 0001"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 2/4/02 at 2:14:52 AM.
Drive and media information from media mount:
Changer Name:
Drive Name: Seagate 1
Media Slot: 0
Media Cartridge Label: MC000004
Targeted Media Set Name: Media Set 1
File "(deleted to protect client).wpd" in use - Backed up.
Backup completed on 2/8/02 at 1:33:23 PM.
Backed up (deleted to protect client) files in (deleted to protect client) directories.
1 file was in use
Processed (deleted to protect client) bytes in 56 minutes and 15 seconds.
Throughput rate: 42.3 MB/min
Software compression ratio: 1.3:1
----------------------------------------------------------
Job ended: Friday, February 08, 2002 at 1:34:24 PM
Job completion status: Successful
-----------------------------------------------------------
From her it simply picked up the next scheduled backup on 2/8/02 and performed that one for about a day and a half. It is curious that it's start and end are accurate, but it's processed time (in all of these cases) is 56 minutes and xx seconds (with xx always falling in the low to mid teens). However, a successful backup (and a normal one) can take two-plus hours (and it records this time accurately). If anyone has any ideas as to what could even begin to cause such a bizarre phenomenon I would be thrilled to hear from you. Thanks,
jason