Panel | |
---|---|
|
...
Upgrading Universal Data Mover Gateway
Upgrading UDMG refers to the increase of a currently installed pre-2.0.x Version, Release, or Modification level of UDMG (1.5.x, 1.4.x, 1.3.x, 1.2.x) to UDMG 2.0.x.
Warning |
---|
As a precautionary measure, it is highly recommended that you back up the UDMG database prior to upgrading. |
Upgrading from a pre 2.0 UDMG release
If you are upgrading an installation of UDMG from any release before 2.0.0.0, the following changes must be reviewd carefully.
Note | ||
---|---|---|
| ||
Starting with UDMG version 2.0, a license key must be provided to enable file transfers. Contact your Stonebranch representative or Customer Support to receive the license key before upgrading to version 2.0 or later. |
...
Note | ||
---|---|---|
| ||
The start parameters for several services have changed. Please review the start scripts, especially for manual installation or if the Systemd service files have been edited. The following modules now require a 'start' command in server mode.
Without it, they will only display the command line usage information. In addition, a 'test' command allows the syntax of the configuration file to be verified without starting the server. |
...
New configuration parameter with UDMG 2.0.0.0
Note | ||
---|---|---|
| ||
Category | Prior releases | Release 1.3 |
user and group | mft:mft | udmg:udmg |
binaries | /usr/local/bin | /opt/udmg/bin |
configuration files | /etc/mft | /opt/udmg/etc |
log files | /var/opt/udmg/logs | /var/opt/udmg/logs |
UDMG Admin UI assets | /opt/udmg/var/www/mft | /opt/udmg/var/www/udmg |
Services |
|
|
Environment variables |
|
|
...
Pre-Installation / Upgrade Backups
The installation process overwrites the current files (exception: the configuration files are kept), this may affect your modifications.
Backing up the configuration files optimizes the time it takes you to get up and running after installing or upgrading.
/opt/udmg/etc/udmg/nginx/udmg.conf
/opt/udmg/etc/udmg/agent/client.toml
/opt/udmg/etc/udmg/agent/server.toml
/opt/udmg/etc/udmg/auth-proxy/config.toml
/opt/udmg/etc/udmg/web-transfer/config.toml
/opt/udmg/etc/udmg-server/server.ini
After upgrading RPM or DEB packages, review the new configuration file templates (with the extension .rpmnew or .dpk-new) and edit the current configuration files to add new parameters or remove deprecated parameters.
...
Release Migration
The UDMG release version is stored in the database to ensure the data structure is compatible with the version of the UDMG components.
After upgrading the component binaries and before starting the UDMG Server it is required to perform the release migration step.
The udmg-server "migrate" command handles the necessary database updates and the setting of the internal version.
Code Block |
---|
$ /opt/udmg/bin/udmg-server migrate --help
Usage:
udmg-server [OPTIONS] migrate [migrate-OPTIONS] [version]
Help Options:
-h, --help Show this help message
[migrate command options]
-c, --config= The configuration file to use
-d, --dry-run Simulate the migration but does not commit the changes
-l, --list List Migrations
-f, --file= Writes the migration commands into a file instead of sending them to the database
-v, --verbose Show verbose debug information. Can be repeated to increase verbosity
[migrate command arguments]
version: The version to which the database should be migrated |
The configuration file is used for the server mode, with the parameter for accessing the target database.
To get the list of supported target versions, use the list parameter. The last value is the release version of the udmg-server and the default target version. The current version of the UDMG database structure is shown with the [DATABASE] tag:
Code Block |
---|
$ /opt/udmg/bin/udmg-server migrate -c /opt/udmg/etc/udmg-server/server.ini --list | tail -n 2
1.5.0 [DATABASE]
2.0.0 [DEFAULT] |
It is recommended to set the verbose parameter (3 times) to follow the progress. If not specified on the command line, the target version is the latest release number.
Code Block | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
UDMG Server
|
Upgrading from a pre 1.3 UDMG release
Note | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
If you are upgrading an installation of UDMG from any release before 1.3.0.0, you must uninstall the older version before installing the new version. Migration from releases before 1.2.1.1 (0.7.1-sb.3) is not supported anymore.
It may be required to modify the work and data directories ownership or access rights and to update UDMG Server transfer rules to use paths that are accessible by the 'udmg' user. The configuration files must be reviewed and compared between the old and new locations. Special attention is required for the AESpassphrase parameter for UDMG Server. It must be the path for the file that was used by the previous release and must be accessible by the new service user. It is recommended to set an absolute path in the configuration file. |
Anchor | ||||
---|---|---|---|---|
|
Pre-Installation / Upgrade Backups
The installation process overwrites the current files (exception: the configuration files are kept), this may affect your modifications.
Backing up the configuration files optimizes the time it takes you to get up and running after installing or upgrading.
/opt/udmg/etc/udmg/nginx/udmg.conf
/opt/udmg/etc/udmg/agent/client.toml
/opt/udmg/etc/udmg/agent/server.toml
/opt/udmg/etc/udmg/auth-proxy/config.toml
/opt/udmg/etc/udmg/web-transfer/config.toml
/opt/udmg/etc/udmg-server/server.ini
After upgrading RPM or DEB packages, review the new configuration file templates (with the extension .rpmnew or .dpk-new) and edit the current configuration files to add new parameters or remove deprecated parameters.
Anchor db_migration db_migration
Release Migration
The UDMG release version is stored in the database to ensure the data structure is compatible with the version of the UDMG components.
After upgrading the component binaries and before starting the UDMG Server it is required to perform the release migration step.
The udmg-server "migrate" command handles the necessary database updates and the setting of the internal version.
Code Block |
---|
$ /opt/udmg/bin/udmg-server migrate --help
Usage:
udmg-server [OPTIONS] migrate [migrate-OPTIONS] [version]
Help Options:
-h, --help Show this help message
[migrate command options]
-c, --config= The configuration file to use
-d, --dry-run Simulate the migration but does not commit the changes
-l, --list List Migrations
-f, --file= Writes the migration commands into a file instead of sending them to the database
-v, --verbose Show verbose debug information. Can be repeated to increase verbosity
[migrate command arguments]
version: The version to which the database should be migrated |
The configuration file is used for the server mode, with the parameter for accessing the target database.
To get the list of supported target versions, use the list parameter. The last value is the release version of the udmg-server and the default target version. The current version of the UDMG database structure is shown with the [DATABASE] tag:
Code Block |
---|
$ /opt/udmg/bin/udmg-server migrate -c /opt/udmg/etc/udmg-server/server.ini --list | tail -n 2
1.5.0 [DATABASE]
2.0.0 [DEFAULT] |
It is recommended to set the verbose parameter (3 times) to follow the progress. If not specified on the command line, the target version is the latest release number.
Code Block |
---|
$ /opt/udmg/bin/udmg-server migrate -c /opt/udmg/etc/udmg-server/server.ini -vvv
2024/06/10 20:01:51 [INFO ] Migration: Starting upgrade migration from 1.5.0 to 2.0.0
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Drop the normalized transfer view'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Add a "src_filename, dest_filename" columns to the transfers table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Add a "src_filename, dest_filename" columns to the history table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Restore and update the normalized transfer view with the new filename'
2024/06/10 20:01:51 [DEBUG ] Migration: Skipped migration 'Check for required MySQL permissions'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Add a 'local_storage' column to the 'local_accounts' table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Fix the 'sb_user_session' table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Create the 'sb_license' table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Drop the normalized transfer view'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Add a 'local_agent_id' column to the 'transfers' table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Update the 'sb_generic_group_join' table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Update the 'sb_user_group_permission' table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Update the 'users' table'
2024/06/10 20:01:51 [INFO ] Migration: Applying migration 'Create the 'sb_local_account_auth' table'
2024/06/10 20:01:52 [INFO ] Migration: Applying migration 'Drop the 'local_agent_id' column from the 'local_accounts' table'
2024/06/10 20:01:52 [INFO ] Migration: Applying migration 'Restore and update the normalized transfer view with the new local agent id'
2024/06/10 20:01:52 [INFO ] Migration: Applying migration 'Create the 'sb_adhoc_share' table'
2024/06/10 20:01:52 [INFO ] Migration: Applying migration 'Create the 'sb_adhoc_download' table'
2024/06/10 20:01:52 [INFO ] Migration: Applying migration 'Bump database version to 2.0.0' |
...
Upgrading with Linux Software Packages
Step 1 | Contact your Stonebranch representative or Customer Support to receive the software package for the intended operating system. | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Step 2 | Perform the recommended backup of configuration files. | ||||||||||
Step 3 | Stop the components services. The exact steps depend on the system architecture and the deployed components, for example:
| ||||||||||
Step 4 | Upgrade the UDMG packages (RPM or DEB), for example:
| ||||||||||
Step 5 | Review the component configuration files. Note that new configuration file templates (with the extension .rpmnew or .dpk-new) that contain all the allowed parameters are added during the software package upgrade.
| ||||||||||
Step 6 | Perform the release migration. | ||||||||||
Step 7 | Review the component service configuration files. For instance, the UDMG Authentication Proxy service file (
Note the addition of the
The same applies for the other components:
| ||||||||||
Step 8 | Start the components services. The exact steps depend on the system architecture and the deployed components, for example:
| ||||||||||
Step 9 | Verify or apply the license; see UDMG Licensing. |
...
Step 1 | Contact your Stonebranch representative or Customer Support to receive the software package for the intended operating system. | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Step 2 | Perform the recommended backup of configuration files. | ||||||||||
Step 3 | Stop the components services. The exact steps depend on the system architecture and the deployed components, for example:
| ||||||||||
Step 4 | Replace the component binaries:
Change ownership/permissions on new files:
Upgrade the Admin UI:
| ||||||||||
Step 5 | Review the component configuration files. Refer to each component installation section below for the list of parameters. | ||||||||||
Step 6 | Perform the release migration. | ||||||||||
Step 7 | Review the component service configuration files. For instance, the UDMG Authentication Proxy service file (
Note the addition of the
The same applies for the other components:
| ||||||||||
Step 8 | Start the components services. The exact steps depend on the system architecture and the deployed components, for example:
| ||||||||||
Step 9 | Verify or apply the license; see UDMG Licensing. |
...
Panel |
---|
; Threshold before warning for long-running queries, the default is 10 seconds WarningTimeout=10s
|
...
Panel |
---|
|
The password key is used for the client authentication.
Setup the Systemd Services
Note | ||
---|---|---|
| ||
If you are upgrading an installation of UDMG from any release before 2.0.0.0, the start parameters for several services have changed. Please review them carefully, especially for manual installation or if the Systemd service files have been edited. The following modules now require a 'start' command in server mode.
Without it, they will only display the command line usage information. In addition, a 'test' command allows the syntax of the configuration file to be verified without starting the server. |
UDMG Server
Create a new service definition:
...
Anchor | ||||
---|---|---|---|---|
|
Security-Enhanced Linux (SELinux) is enabled by default on modern RHEL and CentOS servers. Each operating system object (process, file descriptor, file, etc.) is labeled with an SELinux context that defines the permissions and operations the object can perform. In RHEL 6.6/CentOS 6.6 and later, NGINX is labeled with the httpd_t
context.
When SELinux is enabled, the UDMG Admin UI shows "403 access denied" and "404 page not found" errors on the landing page, and permission errors are reported in the NGINX log files:
Panel |
---|
|
...