Hi Julian,

NTP is working fine on both Ends, so that can be ruled out in this case. Would you mind elaborating on your second point? I would be especially curious about how this would be a Microsoft issue and what the BCP for a case, where your save set for DR simply takes more than a day for the Initial backup, would be.

Thanks for taking the time answering here

Regards

Hi suiluj

     Since the "DISASTER_RECOVERY" is just sitting in waiting to run for more that 24hrs it is doing this.

What I am trying to understand is sine you are using DD as the back end device, even though the first backups fail for :WINDOWS ROLES AND FEATURES:\ it should complete much faster in the second attempt as the dedup would kick in. Can you check if client direct is working for the new machine that you are trying to backup. Also, try increasing your client parallelism to a number equal to the number of partitions on this systems and see if that helps.  

Hi crazyrov and Julian,

going the route of skipping the DR backup for the first run and about 27 hours in so far. Gonna report back when it is done which should be tomorrow.

Thanks again for your help

Regards

by the way, what is the volume to be backed up?

Skipping the windows DR part let the backup complete without errors. Since this is an acceptable solution for us there is no need to dig any further right now. Thank you for pointing me in the right direction.

Good Morning I'm with the same error as you my schedule is right with NTP information Could you please explain to me how you solved this problem? Thank you

In the Save set selection of the Client Properties General tab, exclude the DISASTER_RECOVERY:\ directory. You may backup this directory as a separated task.