Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| blocks:server:mirror [2025-02-13 20:01] – Added Sync Errors note admin | blocks:server:mirror [2025-10-01 09:53] (current) – [Introduction] admin | ||
|---|---|---|---|
| Line 21: | Line 21: | ||
| However, if your Blocks server dies, and won't come back by turning power off and back on again, things are a bit more difficult. Assuming you have an up-to-date backup of your Blocks root directory, as well as other relevant server settings, you can replace the server with a new one, and bring it back to life using those backups. However, that may take a while to accomplish, rendering your entire Blocks installation non-functional in the meantime. | However, if your Blocks server dies, and won't come back by turning power off and back on again, things are a bit more difficult. Assuming you have an up-to-date backup of your Blocks root directory, as well as other relevant server settings, you can replace the server with a new one, and bring it back to life using those backups. However, that may take a while to accomplish, rendering your entire Blocks installation non-functional in the meantime. | ||
| - | A better option is to have a spare server sitting in the rack all along, just as suggested for the main switch above. If you're sufficiently concerned about your system' | + | A better option is to have a spare server sitting in the rack all along, just as suggested for the main switch above. If you're sufficiently concerned about your system' |
| {{ : | {{ : | ||
| - | The new Blocks Mirroring Service will keep your spare computer up to date with any changes applied to Blocks. As soon as you make any changes, such as editing a block or adding a new spot, those changes are copied across to the mirror server. Note, in the illustration above, that the main Blocks server is still connected and used as it was in the stand-alone illustration shown at the beginning of this article. The Mirror server uses a //second// network port as a backdoor connection to your Blocks server. This backdoor is used as a secure channel for copying all changes across as the system runs. | + | The Blocks Mirroring Service will keep your spare computer up to date with any changes applied to Blocks. As soon as you make any changes, such as editing a block or adding a new spot, those changes are copied across to the mirror server. Note, in the illustration above, that the main Blocks server is still connected and used as it was in the stand-alone illustration shown at the beginning of this article. The Mirror server uses a //second// network port as a backdoor connection to your Blocks server. This backdoor is used as a secure channel for copying all changes across as the system runs. |
| Furthermore, | Furthermore, | ||
| Line 349: | Line 349: | ||
| * Disable any such interface(s). in some cases this may need to be done in the computer' | * Disable any such interface(s). in some cases this may need to be done in the computer' | ||
| * Change their addresses to keep them out of this address range. | * Change their addresses to keep them out of this address range. | ||
| - | * Use the advanced //nic// setting to specify which interface to use. | + | * Use the advanced //interface// setting to specify which interface to use. |
| === Verifying over SSH === | === Verifying over SSH === | ||
| Line 358: | Line 358: | ||
| </ | </ | ||
| + | === Custom path to Blocks' | ||
| + | The Mirror service assumes that the main Blocks executable file (named " | ||
| =====Implementation Notes===== | =====Implementation Notes===== | ||