Nigel_Chesher
Level 4
Joined 19 years ago
User Profile
User Widgets
Contributions
Re: Slow backup.
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.1.3KViews0likes0CommentsRe: Slow backup.
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.1.3KViews0likes0CommentsRe: Slow backup.
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? Thanks1.3KViews0likes0CommentsRe: Slow backup.
The job was created and is running on the CASO. Job Catalogs and information are local on the server, the storage is local to server via iSCSI. Attached is an image of the one time the job ran correctly. Current state is the same as before except it's now at "elapsed time: 21:21:30"1.3KViews0likes0CommentsRe: Slow backup.
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. Thanks1.3KViews0likes0CommentsRe: Slow backup.
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. Thishappens 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 versionof 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.1.3KViews0likes0CommentsRe: Exchange Information Stores not showing
Exchange server has been rebooted - no change. The service account is the same on both backup servers, so I know that it's not that. The only thing I didn't mention before, is that the backup server that I want to do the exchange backup from is on a different domain. That's not been a problem before, and I don't think it is now, as I can see and browse the DAG, I just don't see the Informations stores inside! Seemsmaybe I should try the upgrade to R3.839Views0likes0Comments