Azure Site Recovery – Data upload blocked for the ‘/dev/sda’ disk’s replication on the source machine – No crash consistent recovery point available for the VM in the last …
In the event of an error:
Data upload blocked for the ‘/dev/sda’ disk’s replication on the source machine
or
No crash consistent recovery point available for the VM in the last 60 minutes.
On source server please run:
1. Stop replication:
service boottimemirroring_phase1 stop
service boottimemirroring_phase2 stop
service inm_hotplug stop
service nmbd stop
service svagent stop
service vxagent stop
service vConService_linux stop
service uuidd stop
ps -ef | grep ASR|grep -v grep |awk ‘{print $2}’ | xargs kill -9
ps -ef | grep ASR|grep -v grep – should not show any processes
2. Start replication services:
service boottimemirroring_phase1 start
service boottimemirroring_phase2 start
service inm_hotplug start
service nmbd start
service svagent start
service vxagent start
service vConService_linux start
service uuidd startps -ef | grep ASR|grep -v grep – show all replication processes
3. Restart Process Server
Steps 1,2 and 3 can be repeated twice to be sure that everything works smoothly.
The above applies to scenarios of replication source Linux machine based on VmWare or physical server.
In 2 hour check in azure Portal if replication starts again.
Azure Site Recovery – Data upload blocked for the ‘/dev/sda’ disk’s replication on the source machine
W przypadku wystąpienia błędu:
Data upload blocked for the ‘/dev/sda’ disk’s replication on the source machine
lub
No crash consistent recovery point available for the VM in the last 60 minutes.
Na maszynie, która podlega replikacji należy:
1. Zatrzymać procesy replikacji:
service boottimemirroring_phase1 stop
service boottimemirroring_phase2 stop
service inm_hotplug stop
service nmbd stop
service svagent stop
service vxagent stop
service vConService_linux stop
service uuidd stop
ps -ef | grep ASR|grep -v grep |awk ‘{print $2}’ | xargs kill -9
ps -ef | grep ASR|grep -v grep – nie powinien pokazywać żadnych procesów
2. Uruchomić procesy replikacji:
service boottimemirroring_phase1 start
service boottimemirroring_phase2 start
service inm_hotplug start
service nmbd start
service svagent start
service vxagent start
service vConService_linux start
service uuidd startps -ef | grep ASR|grep -v grep – powinien pokazywać procesy replikacji
3. Restart Process Serwer’a.
Kroki 1,2 i 3 można powtórzyć dwukrotnie aby mieć pewność.
Powyższe tyczy scenariuszy replikacji do Azure maszyn wirtualnych Linux’owych opartych na VmWare oraz fizycznych serwerów.
Po wykonaniu powyższego, należy sprawdzić w portalu zarządzania usługą Azure, czy wszystko działa prawidłowo.