Changelog
Version 1.7
Version 1.7.0.1
Changed used SSH library from “renci” to “SSH.NET”
New parameter “-preview” implemented, usage described here: preview Option
Bugfixes on determining which paths come from AutoScanDepth and which are manually configured
Fixed expire function interfering with bunched paths
Various smaller Bugfixes
Version 1.6
Version 1.6.0.6
Bunching feature not in “BETA” status anymore
WebGUI now shows start time for backups in overview
New parameter “-noroot” to circumvent forced recursive root level backup jobs with certain sources (e.g. NetApp mounted on Windows), usage described here: noroot Option
magsX/magsC changed “libicu” dependency checking to warning
New configuration parameter “ReplaceRC”, usage described here: Modifying MAGS Return Codes
Backup logs now show manual subscan entries that will not be optimized by AutoScanDepth
Performance fixes for magsSrv
Fixing an issue, where backup job summary did not show enough log entries
Improved AutoScanDepth calculation performance
Various Bugfixes
Version 1.6.0.4
Fixed bunched backups using default server stanza when done with MagsX/MagsC instead of specified stanza.
Enhancements for MagsLogReport.
WebGUI change to prevent Remote dsmc API configuration entries being deleted accidentally.
Version 1.6.0.3
Support for TLSv1.2 with BackupEagle and MagsLogReport.
Improvements for handling paths not readable by dsmc client.
Version 1.6.0.2
Introduced new “bunch” function.
Introduced “Collect Support Information” function for support.
Enhancements for the MagsLogReport function, which is now included with MAGS.
magsX/magsC additional information to troubleshoot communication issues.
MAGS will now show the remaining days for a limited license.
Several improvements to AutoScanDepth handling.
Graphical improvements for the WebGUI
Various Bugfixes and performance improvements for mags, magsX and magsC.
Version 1.6.0.1
Fixed WebGUI issue showing 0% in progress bar for low values.
Performance optimizations for magsC dsmc starting behaviour
magsX/magsC support for backup job paths ending with a space character.
Various fixes for magsC component.
Version 1.6.0.0
Modernized WebGUI
Added new “magsC” component for running remote backups with a standalone component.
New documentation
Customizable temporary folder for remote MAGS instances (magsX and magsC).
Added new -expirepreview command
The STORAGE PROTECT API path is now dependent of the Client installation path
Added possibility to backup a specific backup source path when using “backup now” in WebGUI
Added additional checks when upgrading MAGS
Changed MAGS-log format to UTF-8 from UTF-16
General performance enhancements and optimizations
Version 1.5
Introduced a new backup button in the WebGUI.
Optimisations for WebGUI Scaling for high resolutions.
Introduced a Log button for the WebGUI overview page to directly jump to current/last logs for a MAGS instance.
Introduced support for HTTPS with the use of SSL-certificates. The certificate can be an already existing one or created by magsConf.
Enhanced support of STORAGE PROTECT return codes 4 and 8. Jobs with these return codes are now shown as yellow in the WebGUI.
Enhancements for the WebGUI overview page.
Generated backup priority lists are now consistent, so that a long-running job will be executed first, even when the last backup failed or was cancelled.
Various fixes for character issues in backup jobs.
Optimisations for logfiles
Fix for updating the STORAGE PROTECT Filespace “Last Backup Date” correctly when using more than one backup path.
Solves an issue where remote backups could fail with a RC12 if the path in question contained a single quote character and the backup was run as the root user (no sudo command prefix).
General performance enhancements and optimizations
Version 1.4
Introduced “Auto Scan”
Fixed various issues with the web interface, especially handling extremely long path names
Introduced inherent authentication
General performance enhancements and optimizations
Version 1.3
Version 1.3.0.2
Streamlining expiration of top level directories in MAGS to be much faster than with 1.3.0.0 and 1.3.0.1 and making expiration of these directories an optional process with the “-expire” command line parameter.
Fixed an issue where post-processing after each job could take a very long time and giving the appearance of hung processes if the “subdir=yes” option was present in the STORAGE PROTECT client option file.
Version 1.3.0.1
Fixed a problem with user authentication when accessing the MAGS web interface.
Version 1.3.0
Fixed a problem where some top level directories weren’t entirely expired after deletion/rename from the STORAGE PROTECT occupancy under certain circumstances. You may experience an unusually high number of “expired” objects when first running MAGS V1.3 on a directory previously backed up with the regular STORAGE PROTECT client or an earlier Version of MAGS.
Fixed an issue where subscans weren’t properly displayed in the web interface.
Fixed an issue where the magsSVC service was consuming a large amount of RAM during processing.
Introduced restore functionality directly from the web interface.
Added Linux client support.
Version 1.1
Added web interface for configuring and monitoring MAGS
Performance improvements when handling many jobs
License module introduced
Version 1.0
Version 1.00.0021
Fixed an issue where opening a log in magsmon could take a very long time when dealing with tens of thousands of jobs.
Extended evaluation to July 31, 2016.
Version 1.00.0020
Added a new function which enables updating of backup begin- and end-dates for a filespace on the STORAGE PROTECT server via the STORAGE PROTECT Client API.
Fixed an issue causing backup logs to take a very long time to load when displayed in tabular view.
Extended evaluation to April 10, 2016.
Version 1.00.0019
Introduced a new log mechanism which allows MAGS to keep any number of inactive log versions between 3 and 99. Magsutil now also offers the option to suppress automatic archiving to an “arch” log when the number of configured log file versions is exceeded.
Fixed an issue with Mags which caused excessive runtime for determining priority lists if the number of jobs resulting from a scan grew beyond a couple of thousand or so. Mags could take several hours to process priorities. From the log file, it seemed that Mags was doing nothing between scanning subdirectories and assigning jobs. This fix should allow Mags to finish that task in a few seconds.
Introduced an additional, long-term statistical overview of how Mags jobs developed over time in Magsmon.
Version 1.00.0018
Introduced automated priority sorting to MAGS. When MAGS is starting up, it now analyses the previous backup and dedicates a little more than half of the parallel processes to handling the longest running jobs first. In many environments, this has a positive effect on overall runtime of MAGS.
Fixed a problem where certain Unicode characters weren’t interpreted correctly by the STORAGE PROTECT client. In some cases, this may lead to the character(s) in question being replaced by a question mark which may lead to some directories being scanned twice if several paths with uninterpretable but different Unicode characters in the same positions exist.
Fixed a problem where log files couldn’t be displayed or popped annoying message boxes in MAGSMON when certain locales with certain versions of Windows 2012 and 2008 were used.
Version 1.00.0017
Extended evaluation period until February 2, 2015
Version 1.00.0016
Fixed a Problem where MAGS restore would appear to hang when using generic restore function and scanning a filespace. The status bar displays a message similar to “Getting information for path” but no path name actually displayed.
Affected Versions: - 1.00.0015
Impact: Caused MAGSREST to hang as soon as any of the “Scan and select…” functions with a level deeper than “next” were selected on a filespace.
Nature of fix: MAGSREST now omits empty dsmc query backup entries.
Added subscan information to log file table view in magsmon.
Added graphical view to log file exploration in magsmon.
Version 1.00.0015
Fixed a Problem where MAGS restore would appear to hang when using generic restore function and scanning a filespace.
Affected Versions: 1.00.0014
Impact: Caused MAGSREST to hang as soon as any of the “Scan and select…” functions were selected on a filespace.
Nature of fix: MAGSREST now scans only the appropriate level of directories even if “subdir=yes” is explicitly given in the used dsm.opt file.
Fixed a Problem where MAGS would ignore scandepth settings greater than 9 and revert to the default scandpth instead.
Affected Versions: - 1.00.0014
Impact: Caused MAGS to not scan deeper than default scandepth when configured with a subscan level of greater than 9.
Nature of fix: MAGS now properly applies subscans greater than 9.
Fixed a Problem where MAGS didn’t apply different default scandepths and backup sources when more than one job were defined in a MAGS option file.
Affected Versions: - 1.00.0014
Impact: Caused MAGS to either fail subsequent backups entirely or process them with the wrong scandepth.
Nature of fix: MAGS now processes more than one job per mags option file properly with individual default scandepths and backup sources.
Added the option to exclude finished jobs from displaying in magsmon.
Added the option to directly view log files in magsmon.
General performance improvements in magsrest and mags.
Added the possibility of restoring to multiple Isilon nodes simultaneously in magsrest.
Version 1.00.0014
Occasionally occurring conflict with pre-defined DSM_CONFIG and DSM_DIR environment variables removed.
Affected Versions: - 1.00.0011
Impact: Caused MAGS, MAGSREST and MAGSUTIL to stall when accessing STORAGE PROTECT from a user environment inheriting the variables DSM_CONFIG and/or DSM_DIR from system-wide Windows configuration.
Nature of fix: MAGS now overwrites these parts of its temporary execution environment with the options given by user through MAGSUTIL.
Introduced “Generic Restore” functionality to enable restore of data not originally backed up with MAGS and/or to enable better control of what and how parallel to restore certain directories independently of how parallel they were backed up.
Version 1.00.0011
Fixed an issue where MAGS could crash with a Windows AbandonedMutexException when starting up while MAGSMON was running on a desktop and logged on to the same MAGS Option File.
Affected Versions: 1.00.0000
Impact: Aborted MAGS. Happened on rare occasions. Could be avoided by closing the appropriate MAGSMON window.
Nature of fix: Should prevent the exception from occurring.
Fixed an issue where the STORAGE PROTECT client could not interpret a path containing a single quote character (‘) properly and tried to back up its Domain scope instead.
Affected Versions: 1.00.0000
Impact: Caused a mostly unnoticed and unnecessary backup of local resources such as system state and local disks. Prevented the path underneath the one containing the offending character from being backed up by STORAGE PROTECT when using MAGS without triggering an appropriate error message. The error could occur only in environments where the offending path was covered by the “ScanDepth” parameter. Paths further down the hierarchy were unaffected.
Nature of fix: MAGS now escapes paths containing ampersands properly and thus backs up data contained in those paths rather than the STORAGE PROTECT client’s Domain scope.