|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (4)
View Page History...
h3. What To Expect When Using Docstore
The Docstore is not a very big application, and does not need to be updated very often once it is installed. However, if you are updating the Docstore, you are probably also updating the SBM packages on the machine, which will most likely cause the replication to fail when the CDP server is restarted.
What happens to site-to-site replication tasks during a Docstore update?
* If the SBM has Site-to-Site replication configured and updates to a Docstore release, the tasks won't spawn when a replication task is executed while Disk Safes are being upgraded.
* If the replication task tries to send to a non-Docstore SBM, don't worry. The metadata language hasn't changed, so Docstore metadata can be sent to any SBM before or after version 5.14.3.
* If the SBM has Site-to-Site replication configured and updates to a Docstore release, the tasks won't spawn when a replication task is executed while Disk Safes are being upgraded.
* If the replication task tries to send to a non-Docstore SBM, don't worry. The metadata language hasn't changed, so Docstore metadata can be sent to any SBM before or after version 5.14.3.
* If the replication task tries to send to an SBM that is in the process of being upgraded to Docstore, the task will fail, and the target Disk Safe will have a recovery point marked as "Replication Interrupted."
The Docstore is not a very big application, and does not need to be updated very often once it is installed. However, if you are updating the Docstore, you are probably also updating the SBM packages on the machine, which will most likely cause the replication to fail when the CDP server is restarted.
h3. {color:#000000}{*}Tips and Tricks{*}{color}
...