Macrium Site Manager 8

Versions Compared

Old Version 3

changes.mady.by.user Jack Mansfield

Saved on

compared with

New Version 4

changes.mady.by.user Macrium Software

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space MSMBASE and version 8.0

...

OptionDescription
Custom NameThe custom name is shown in the UI to identify the sync. If left blank, the server/local path of the sync will be used instead.
Folder Name

The folder name set here will be created on the server/remote path to store the synchronized backups.

Info

The path configured as part of the network or server path must exist on the remote server or the sync process will generate an error, however, Site Manager will create the folder set as the folder name if it does not already exist.

For example, if remote sync is configured with a server of sftp://192.168.0.1/home/backups and a folder name of SiteManager1, the sync process will store image files in /home/backups/SiteManager1, creating the SiteManager1 folder if necessary.

Multiple repositories can sync to the same server/network path so long as the folder name is different for each one.

Synchronization Window - TimesThe synchronization window controls what time of day the sync will run. When the start time is reached, Site Manager will stop scheduling backups on the repository, wait for any existing backups to finish then run the sync. After the sync has finished, backups resume. If the sync can't be started before the sync end time is reached, the sync attempt is abandoned until the following day. This option allows some control over when high internet bandwidth options like sync get run.
Synchronization Window - FrequencyThe sync process can be limited to only happening on some days of the week by selecting the desired days here.
Options - Allow Backups During Remote Sync

If this option is selected, backups to the repository will be allowed to continue during the synchronization process, with some limitations. 

  1. The remote sync can only start when no backups are running - this is so that there is a consistent, point in time view of which backups exist
  2. The sync process will find changes and data to upload and sort them by computer
  3. Changes are uploaded for the computer with the smallest amount of data to upload
  4. The computer from step 3 is 'unlocked' and backups for this computer may now start
  5. Steps 3 and 4 are repeated until all data is uploaded
  6. The change is committed in the remote location. Before this step, if the sync fails, the changes can be rolled back to the previous repository state
Enable per folder upload

Uploaded backups are committed to the remote location immediately after new data has been uploaded for each folder. A folder in the repository corresponds to the backups for an individual computer and backup definition. This option reduces the impact of upload failures by more frequently checkpointing so that less work is required to recover a consistent checkpoint and continue the sync on reupload. It can also reduce the amount of temporary storage space on the remote sync target as each checkpoint will flush old files that are no longer needed.

When using this option, the remote store will always remain in a state where it can be rolled back to the last checkpoint should a connection be interrupted. This is generally not an issue - if the sync is retried after interruption, the sync will continue from the checkpoint until completion, but if the sync cannot be retried (due to repository disk failure for example), some folders in the remote sync will have the pre-sync contents and some post-sync contents. If there is a requirement that the backups for two computers remain in close sync (e.g. a replication set of servers), this option may be inappropriate. 

Finishing the Wizard

When finishing the wizard, a connection test is performed by the server and any errors are highlighted to be fixed:

...