Appendix

Windows Event Log

Magnus Box logs all job messages to the Windows Event Log. The log content is identical to the job log content seen in the Magnus Box server's log browser, or the Magnus Box history table. This should allow you to check for errors and/or ensure that jobs are running on time, by monitoring the Windows Event Log. However, please note that this only covers client-side jobs, that do actually run. e.g. because "Missed Backup" job entries are generated server-side, they won't appear in the client's e...

Data validation

There are three types of integrity verification in Magnus Box: Referential integrity Referential integrity means that for each snapshot, all its matching chunks exist; that all the chunks are indexed; and so on. This is verified client-side every time the app runs a retention pass, so you should ensure that retention passes run successfully from time-to-time. Data file integrity at rest Data file integrity ensures that each file in the Storage Vault is readable and has not been corru...

Magnus Box Exclusion List

Due to Magnus Box being unable to backup specific config files, we have created a global exclusion list. This is not a complete list and please use at your own risk. Exclusion list *\Users\*\AppData\Local\Microsoft\WindowsApps\AppleInc* *\Users\*\AppData\Local\Microsoft\WindowsApps\Microsoft.MicrosoftEdge* *\Users\*\AppData\Local\Microsoft\WindowsApps\iTunes.exe *\Users\*\AppData\Local\Packages\Microsoft.SkypeApp* *\Users\*\AppData\Local\Packages\Microsoft.Xbox* *\Users\*\AppData\Local\Mi...

Encryption and key management

The user's password is used to derive two 192-bit keys (the "L" and "R" keys) via PBKDF2-SHA512, with hard-coded parameters for repeatable output. - The L-key is used to log in to the Authentication Role server in place of the real password; the server stores only a bcrypt(sha512) hash of this L-key. - The R-key never leaves the client, and is used to encrypt secret keys stored within the user's profile on the server. This means that one password can be used for all client-side accoun...

Applying hotfixes

When you report an issue to Magnus Box staff, every attempt is made to reproduce the issue in-house. Once the issue is reproduced, we can confirm a fix internally. Sometimes an issue depends on specific environment details that are infeasible to recreate. In these situations, support staff may ask you to run a "hotfix" version of Magnus Box that contains experimental changes, to test a potential resolution for your issue. Hotfixes normally come in the form of a replacement backup-tool file. A...

Changing Magnus Box's temporary directory

Magnus Box uses the local system's temporary directory for some cache files while the backup job is running. The needed storage size is small; but on some devices (e.g. NAS with fixed-size /tmp/ mounts) the system's default temporary directory may be insufficient. On Linux, you can change the temporary directory Magnus Box uses by adding export TMPDIR=/some/other/path/ in your startup script (e.g. normally /opt/MagnusBox/backup-daemon-start.sh or any custom rc.local file). However, any changes ...

Marketing resources

Download and customize our ready-made marketing materials to help sell your backup service. Click here to download and customize these resources to get started. (https://magnusbox.com/wp-content/uploads/2019/07/Magnus-Box-Promo-Flyer-Blank-2.zip) This kit contains brochure assets for use with Adobe InDesign. If you have any questions about this resource, please email support@magnusbox.com (mailto:support@magnusbox.com)

Suppressing Before / After command failures

When a command-line program displays some output, the output is either sent to stdout ("fd 1", for normal messages) or stderr ("fd 2", for error messages). Magnus Box will mark a Before/After command as a warning if there was content on stderr, or, if the command had a non-zero exit code. If you are certain that the command cannot fail, you can - redirect stderr messages to go to stdout instead, by adding 2>&1 to the end of your command - override the command exit code, by adding to...

Importing backup settings from other products

Magnus Box supports importing settings from certain other third-party backup products. In all cases, only user configuration settings are read from the other product. - Existing backed-up data is not converted to Magnus Box's format; you must back up the data again using Magnus Box - Historical logs are not imported. Ahsay OBM/ACB 6.x or compatible Ahsay, OBM, and ACB are trademarks of Ahsay Systems Corporation Limited. Magnus Box can import settings from an installed version ...

Configure two-factor authentication

Two-factor authentication is an additional layer of protection for your Magnus Box Server administrative login account. When this feature is enabled, an additional device (such as a cellphone app, or a hardware token) is also required to log in to the web interface. This means that a stolen password is insufficient to break into the web interface. TOTP The Magnus Box application supports two-factor authentication for administrator accounts in compliance with the TOTP standard....