Config db ntf: 20171013140700
Analyze db ntf: 20171013140700
Help db ntf: 20171013140700 / Content: 20171013140700
Windows Version: 6.0.0 :: MAC OS X Version: 6.0.0 :: Linux Version: 2.0.52
Eclipse Plugin: 3.0.1
Major Improvements: Extensive enhancements for Roaming/Rollback and Backup actions, new Roaming Cleanup, database scanning added to XML Export action, stub actions.xml support
General Notes | |
|---|---|
 | Supported IBM Notes releases: 5.x, 6.x, 7.x, 8.x, up to 9.0.1 including the IBM Notes Browser Plugin and ICAA. (Administrators need at least IBM Notes 8.x clients, the new chart functionality requires at least version 9.x for both client and server. Selected administrative tasks, such as Online Update, also require Microsoft Windows and Notes 9.0.1 FP7) Supported client-side operating systems: Microsoft Windows XP, 2003, 2008, Vista, 7, 8, 10, and Citrix/WTS, Apple Intel Mac OS X 10.5-10.10 (Leopard, Snow Leopard, Lion, Mountain Lion, Mavericks, Yosemite), Linux Supported server-side operating systems: any supported by IBM (operating system independent) NOTE: Support is limited for platform and release combinations not supported by IBM |
| Linux: Eclipse Management, Skinning, Realtime, Zip/Unzip and Attachment Blocking are not available on Linux or Mac OS X; Citrix, Linux & Mac OS X: the MarvelClient Upgrade module is only available on Windows (=not on Citrix, Linux or Mac OS X) MarvelClient on Linux does not support the runtypes "Before Login - Init", "After Login - After Write", "On first server access", "Background - Init" and "Background" - any such actions must be set to run at a different supported runtype, e.g. "After Login" |
| IMPORTANT NOTES | This release contains select important updates highlighted in red |
Configuration Database | |
| FIX | Fixed an issue where the Automate Sync agent didn't work due to a problem with the logging library. |
| ENHANCEMENT | The profiling/backup/roaming key in Backup and Roaming/Rollback actions now support a new placeholder: %DATE_FORMAT_*% |
| ENHANCEMENT / NEW | New target types available in Backup/Roaming actions. They all provide support for all usual features in the Backup and Roaming actions and can be used as replacement for filesystem targets (since they do not require Notes login, they work before login). WebDAV: Backup to/Roam from a web server via http. This also includes single-sign-on via SPNEGO (Kerberos and NTLM are supported). FTP: Backup to/Roam from an FTP server. This requires either anonymous access or credentials that need to be included in the action. Notes database via http: This is a special setting where the Backup action does a normal backup into a provided Notes database (similar to an upload into the AnalyzeDB) - and also creates an upload view in the target database, if it is missing. The Roaming action then will be able to access this view via http and download the roaming set. This http access requires working SPNEGO authentication (Kerberos or NTLM). Users require the ACL right "Create shared folders/views" in the target database, and the http task on the server needs to be turned on. The main idea behind this target type is to use the user's own mailfile as a backup/roaming target. |
| ENHANCEMENT / NEW | New option in Backup and Roaming/Rollback actions to use a limited replica (=data only) for names.nsf and journal.nsf. Instead of uploading the entire database every time, it will only upload a subset that excludes the database design. This should help to reduce network and file server load. |
| ENHANCEMENT / NEW | New options in File Deployment action: Newer only: only downloads the file if the target file is older (or doesn't exist). Missing only: only downloads the file if no file exists at the target location. Always: always downloads the file and overwrites any file at the target location (same behavior as before). Newer only is limited to zip archives. If a zip archive is set to unzip, these options individually apply to files with the archive. |
| ENHANCEMENT / NEW | New options in the Extended XML Export action; it can now run additional database scans. These scans make it possible to find databases outside of the data directory. It can scan all fixed disks, all assigned drive letters, and/or a list of provided directories; it also has options to exclude certain directories. Furthermore, the scan result will be merged into the database info cache MarvelClient maintains, and will be available to other actions (and will be written to disk in the normal databases.xml). This can be turned off, however, so that the scan results are discarded after the action. The DLL already has been supporting this functionality since version 5.0.4 (however there has been a bug fix recently, so using a 6.x DLL is recommended) |
| NEW | New action: Roaming Cleanup. This action allows you to clean up backup/roaming sets within a certain key on a filesystem or WebDAV target.
|
Analyze Database | |
| FIX | Fixed a rare issue with the display of attachments in the upload document for attachments whose revision number was much larger than the configured revision limit. |
| FIX | Addon Collect Mail Archive Details: Fixed an issue where the agent would look for local archives even if the mail archive was configured as "on server". |
MarvelClient Help | |
| UPDATE | Updated release notes |
MarvelClient Upgrade | |
| MCUpgrade (5.4.2) | - No Changes - |
Eclipse Plugin | |
| MC Eclipse Plugin (3.0.1) | - No Changes - |
.DLL Updates (Windows) / .dylib Updates (Mac OS X 64-bit) | |
| FIX (6.0.0) | Fixed a logging issue where File Operation actions didn't properly log what they deleted. This only affected the log output, not what the action did. |
| FIX (6.0.0) | Fixed a bug in the Backup action. Files in a backup set that no longer are part of the Backup action would not get properly set to the "end" revision, instead their revision would keep increasing. This didn't cause any problems with roaming or backup, but would cause display issues in the Analyze database. |
| FIX / CHANGE (6.0.0) | The return value "available_instances" in the Backup action now will be set to "created" if a new backup set is created (instead of being "none") |
| FIX / CHANGE (6.0.0) | In the Extended XML Export action, setting the database scan to discard the results after writing the XML will no longer prevent an id file XML export. |
| CHANGE / ENHANCEMENT (6.0.0) | Backup actions will no longer search for a backup set to write to; they will just use the backup key to find the path, and create a new backup set if there isn't one. The new behavior doesn't apply to database targets. This should help to reduce the load on network and file servers. Set <mc:backup_action_do_search> to 1 to restore old behavior of scanning all backup sets in the target location to find the newest one that matches the key. |
| CHANGE / ENHANCEMENT (6.0.0) | Added some code to attempt to parse the Notes hotfix number from the release string (<notes:version_release_string>) and set <notes:version_hotfix> accordingly. |
| CHANGE / ENHANCEMENT (6.0.0) | The DLL Update action will now add the config value <mc:version_build_updated> (set to 1) when it switches out the DLL. |
| ENHANCEMENT (6.0.0) | New Placeholder: %DATE_FORMAT_*% (where any combination of Y, M, D, and W can be used in place of the *). |
| ENHANCEMENT (6.0.0) | New option <mc:journal_get_path_from_bmprofile> (bool, defaults to 0). Set this to 1 to try and get the journal path from the hpsettings profile in the bookmark.nsf before trying other places. |
| ENHANCEMENT / NEW (6.0.0) | Added new target types to Backup and Roaming actions. They all work via http/ftp by using cURL, and all http variants support single-sign-on via SPNEGO. |
| ENHANCEMENT / NEW (6.0.0) | Added support for so-called "limited replicas" during backup and roaming. Instead of uploading the entire database, or replicating it with the target location, it locally creates a temporary replica that only contains a subset of the notes/documents in the source replica. Database design is automatically excluded, and a formula can be provided to further narrow down the documents that should be included (@All by default). This temporary replica is then zipped and uploaded to the backup set. On roaming, the same process runs in reverse. If the database doesn't yet exist locally, it is just copied to the target destination, and a design refresh is triggered. |
| ENHANCEMENT / NEW (6.0.0) | File Deployment actions now support a "do not overwrite" option. |
| ENHANCEMENT / NEW (6.0.0) | Added a new config setting <mc:viewreader_next_cleanup>. Set to "replace" or "refresh" (both without quotes) to trigger a cleanup replace or refresh on the next viewreader that runs (successfully). This works similarly to the existing settings like <mc:viewreader_afterlogin_cleanup>. |
| ENHANCEMENT / NEW (6.0.0) | Added support for a stub actions.xml to be used on a client start where there is no actions.xml on MC_NetworkDirectory (e.g. the first time a new user starts). Set <ini:MC_ActionsXMLStubPath> to point to the stub xml file. The same placeholders as in MC_WorkingDirectory can be used. What it does: If no actions.xml can be found, the provided stub will be copied to the normal location and renamed to actions.xml, if needed (so the stub file does not need to be named actions.xml). It will set <mc:actions_from_stub> to 1 when this happens. It will also automatically trigger a viewreader cleanup replace the next time action download happens (by setting <mc:viewreader_next_cleanup> to "replace"). This means, that all actions will be read from the download view and local actions will be replaced with the downloaded ones regardless of timestamp, and actions that have no match in the download view will be removed from the actions.xml. |
| NEW (6.0.0) | Added new Roaming Cleanup action. This action allows the cleanup of MarvelClient backup-/roamingsets stored on a filesystem or WebDAV target. It has 2 functions: Cleanup: remove old backup sets, either by count (only keep x newest) or by age (only keep newer than x days). It also provides an option to safeguard against removing all backup sets. Fix folder location: This will fix the folder naming/structure of backup sets that have been manually renamed to once again match their profiling keys. It will overwrite older sets if the occupy the target path, and has an option to keep or discard the wrongly named sets. This is limited to fileystem targets only. Use with caution, and only if really needed. |
.dylib Updates (Mac OS X 32-bit) | |
| .dylib (2.0.51) | - No Changes - |
.so Updates (Linux) | |
| .so (2.0.52) | - No Changes - |
