Forum Discussion
15 Replies
- Nigel_ChesherLevel 4
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.
- CraigVModerator
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!
- pkhModeratorIf 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
- Nigel_ChesherLevel 4
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
- CraigVModerator
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!
- CraigVModerator
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!
- pkhModeratorSynthetic backups is equivalent to a full backup and can take a long time. Some you are doing synthetic backups, your full and incremental backups are true image backups which will take longer than normal backups
- Nigel_ChesherLevel 4
- CraigVModerator
How have you set up the iSCSI connection? Are the ports on the storage and switches all hard-coded to the fastest speed avaiable, ie. 1000MB FULL?
Does a job created on the MMS run faster?
Thanks!
- Nigel_ChesherLevel 4
The ports are teamed, both to the network and the iSCSI storage, speed is 2.0 Gbps for eac of them.
I've managed to get the job running again: Instal latest updates both on BE server and Data server. Update agent. Re-create job!
It still runs slow, It's a 2.5TB backup of data files and it doesn't start transfering data until 15+ hrs into the job!
Any thoughts on why it takes so long actually start transfering the files?
Thanks
Related Content
- 9 years ago
- 6 years ago
- 10 years ago
- 10 years ago