I have a few jobs that are only to back up our user data. This is a backup to disk job, the job starts, but then sits with a status of running for anything up to and beyond 24 hours. This happens for both the Full and the Incremental. I realise that a lot of data files will be slow, but to have to wait for such a long time appears to be counter productive compared to an older version of BE that I used to use that would complete a backup to tape job in the same time this one takes to actually start transfering data! I admit to being very confused about this.

If you've got an antivirus running on the media server, put in an exclusion for the B2D location. B2D should actually be faster (a bit) than tape as it allows the data to be streamed to it at a consistent rate. No stop/start like a tape drive. When the job kicks off again, just make sure there arent any pending alerts you need to respond to as well. Thanks!

If you are using the Archive bit method, change it to the modified time method and see whether it makes a difference. Also is you have sufficient disk space, do a backup to disk to test. As previously advised, check that there are no outstanding alerts that you need to respond to

Thanks for the responses.. Anti Virus is excluded from scanning the BEData folder. I have 45TB available space on my B2D storage. There are no pending alerts. The jobs are set to modified time. I have re-started the BE services (the job would not cancel), the job is a Full with incrementals and Synthetic. Currently the Synthetic thinks it is running! Status: Queued, Current Operations: None, Elapsed time: 05:00:00 It does this for the Full and Inc jobs as well but eventually starts transferring data. I attach a screen shot of the Job Activity. Thanks

Wait, there is a CASO involved? Where are the Catalogs and job information located? Centrally on the CASO? Replicated between the MMS and the CASO? The job was created on the CASO...what happens to the backup if you create it on the MMS explicitly? Thanks!

Slow backup.

15 Replies

CraigV
Moderator
9 years ago
...are there any alerts while it's waiting to start transferring data?
Nigel_Chesher
Level 4
9 years ago
No. It just sat there with a Status: Running Current operation: Backup. Then all of a sudden data starts to flow!

My reason for asking is that I have larger jobs to run that can sit there for 2-3 days before they start transfering data. Some are on my other BE server, so at least they're both acting the same even if it's not really acceptable from my point of view.
CraigV
Moderator
9 years ago
OK, how many concurrent jobs are running to the B2D? Are you sure you have enough?

What happens if you run this job manually with no other jobs running?

Thanks!
Nigel_Chesher
Level 4
9 years ago
I've set it to a maximum of 5 concurrent jobs. At this moment there are two jobs running, both data only jobs.

1st job: status - Running, Current operation - Backup, Elapsed time - 01:04:29:55, Bytes - 0.

2nd job: status - Running, Current operation - Backup, Elapsed time - 14:25:56, Bytes - 0.

They just sit there, if I wait long enough they usually start transfering data!

Both jobs are B2D and there is currently 41TB of free space available.
mgmasterv2
Level 6
9 years ago
i have kinda same problem , job get stuck in queue, backup or loading media state for long time.

Forum Discussion

Slow backup.

15 Replies

Related Content

Backup-to-disk-to-tape slow

Backup Exec 15 Performance Slow

ZFS BACKUP SLOW THROUGHPUT

Slow backup speed

NBU 7.7.3 - Slow catalog backup

Recent Discussions

Backup Exec Job got canceled

BackupExec for Oracle 23ai?

Add Oracle DB in Backup Exec

Veritas Backup Exec version upgrade & migrate to another new Server

Veritas Backup Exec 23 - Slow Backup after Windows server 2019 upgrade