Accesser® Node receives PUT command from
client and begins writing the object to both vaults in parallel.
Figure 1. Accesser® Node writes Slices to both vaults in mirror
(simplified view)
Accesser® Node remembers vault response when a write request
has succeeded to one of the component vaults. Response to user is not delayed by a response from the
slower component vault.
Note: Protected Mirrors perform synchronous or asynchronous writes based on
the configuration of the vault. Therefore, when configured for asynchronous write operations,
Accesser Devices will return to the client that a write has finished after only a single vault has
successfully written the contents.
Note: If the attempt to write to one of the vaults fails for any reason, the objects mirror state is
set to Failed and the object is added to the Accesser® Node list of objects to synchronize.
Figure 3. Accesser® Node informed of failed write to vault
2
Figure 4. Vault now in Failed state and Accesser® Node queues
Object to synchronize
The Accesser® Node continues to write to vault 2, if
applicable.
Note: If the attempt to write to one of the vaults fails for any reason, the objects
mirror state is set to Failed and the object is added to the Accesser® Node list of objects
to synchronize.
Figure 5. Accesser® Node informed of failed write to vault
2
Figure 6. Vault now in Failed state and Accesser® Node queues
Object to synchronize
Note: Protected Mirrors perform synchronous or asynchronous writes based on the configuration of the vault. Therefore, when configured for asynchronous write operations, Accesser Devices will return to the client that a write has finished after only a single vault has successfully written the contents.The Accesser® Node continues to write to vault 2.
