07-05-2015 12:25 AM
We are using Backup Exec 2010 to backup an Exchange 2010 DAG. Two of the DAG nodes are located on the same LAN as the backup server and the job goes to a tape library.
One of the DAG nodes was recently replaced with a faster performing server. There are 22 databases and approx 2TBs to backup. I can see the backup is using the new DAG node.
The job rate is good at the start but when it gets to the end of a database, the job states it is "running" but no data is traversing the NICs and the byte count doesn't change. It takes forever to move onto the next database.
It would be great to know what it is actually doing? Any ideas?
07-05-2015 12:35 AM
07-05-2015 12:45 AM
thanks, any idea how I can verify what the job is doing? I'll get the usual "it worked before" :)
07-05-2015 11:40 PM
When the Status is "Running", what is Current Operation displaying ? is it backup or verify or catalog ?
07-06-2015 09:39 AM
It is showing backup
07-07-2015 12:12 AM
It may be doing GRT cataloging. Couple of options. You could either enable debug and check or better still, run a non-GRT backup and check if the same issue reoccurs or not. If not, then its definitely cataloging.
07-07-2015 12:47 AM
07-07-2015 12:28 PM
looks like it was related to vss, GRT was disabled all along. Once this was modified in the job it was back to the usual speed.