Introduction
This guide explains the transitional solution of how to create a failover scenario for the Silent Brick Archive.
This is a transitional solution only until the build-in automatic failover is introduced in the next software release.
-
-
Add an A name record for both Silent Brick Systems
-
Create a CNAME entry pointing to the primary Silent Brick System ( here SB-01 )
-
-
-
If the primary Silent Brick System is unreachable the software can not access the share
-
The path has to be switched so the software accesses the secondary Silent Brick system
-
-
-
Only nescassary if the Archive / Volume / Share configuration has changed on the source side.
-
Open the UI of your secondary Silent Brick System
-
Set the archive offline
-
Set the archive online again
-
This procedure will be automatically executed in the coming software release
-
-
-
Switch the DNS CNAME to the second Silent Brick System ( here SB-02 )
-
Access to SB-VIRT will now be redirected to the secondary Silent Brick System
-
The software can access its data again
-