Create Remote Backup between 2x4bay PR4100 devices

My Cloud OS 5 My Cloud PR
1

I am trying to create a remote backup between two PR4100 (4-bay) devices and failing.

On my source PR4100 I had previously configured a remote backup successfully to the destination PR4100, but due to a network issue the IP addresses have changed. There appears to be no simple way to just change the IP address in the scheduled job, so I deleted the scheduled backup (as this now fails) and tried to create a new one using the same settings - but I cannot browse the destination share to set it (and it does not allow to manually add it).

I have set the password and SSH password to the same on both devices as I thought the password might be the issue, but still am unable to select a destination share. Both devices are ethernet connected via a Virgin media Hub and both allow me to perform admin functions and to see the shares, but do not seem to talk to each other!

All I want to do is to have the main NAS device archived to an identical backup NAS device (both attached to broadband network hub via ethernet - the only difference is drive size - 4TB to 3TB drives) in case one fails so I always have a valid file-share. Does anyone know what is going on here?

2

Hi @ChrisEM

Have you checked our knowledge base articles?
(Support for Western Digital Hard Drives | Western Digital)

Try this one.

Have you opened a Support Case?
If not, contact Western Digital Technical Support for assistance.
[Contact Us | Western Digital]

3

I have successfully created 10 remote backup jobs. If I go into the dashboard, select the remote backup app and select config I can see them all and run them. When I leave the NAS devices to run the tasks automatically as scheduled, they fail. When I check the failure and subsequently manually run the failed job, it runs succesfully to competion. The question is, why does the scheduled background remote backup fail? I have yet to diagnose and to correct this issue with scheduled remote backup sessions. I have not opened a support case as I was hoping someone in the community might recognise the issue and already have the solution.