Reasons why Full Synchronization may start
- Explanation
- April 30, 2015
Content
Full synchronization starts instead of Fast in the following cases*:
- If HA device was configured to use write-back cache and its flush did not complete correctly upon StarWind service restart, or one of the servers was turned off not correctly (i.e. hard reset, power outage, service interruption etc);
- If the errors were detected during the writes on the disk;
- If partner, that should be the source of synchronization has the state other than “Synchronized”;
- If initial synchronization was interrupted due to any reason;
- If the Partner that should be the source of synchronization gained “Synchronized” state after initiating “Mark as synchronized” command;
- If StarWind service was turned off on all servers. Such case could be avoided by configuring disk-based synchronization journal: https://knowledgebase.starwindsoftware.com/maintenance/how-to-change-synchronization-journal-for-starwind-ha-devices/
Synchronization will not start automatically if the errors were detected during the writes on the disk.
*The options above apply to *.img based HA devices only.
In order to avoid Full synchronization when each server with HA devices should be turned off (for maintenance, scheduled power outage, etc.), the Maintenance mode feature can be used.
More information about the Maintenance mode can be found in this guide.
Request a Product Feature
To request a new product feature or to provide feedback on a StarWind product, please email to our support at support@starwind.com and put “Request a Product Feature” as the subject.
