The following are the requirements for upgrading Orchestrator. See the Aspera Orchestrator
User Guide for more information about the directory locations referred to in this
procedure.
- User access: all commands must be performed as Administrator or an equivalent superuser.
- Orchestrator is already
installed on the Windows server.
- A backup of MySQL data has been performed by MySQL dump.
$ mysqldump -h localhost –u root –p orchestrator >
C:/Temp/orchestrator_db_backup_timestamp.sql
Note: The
generated .sql file may take several gigabytes of disk space
depending on the database size, so make sure that enough space is available on the
targeted partition (/tmp in the example above) before running the
backup
- A backup of Aspera Orchestrator data performed with the Snapshot feature. Refer
to the Orchestrator User Guide for information on taking a snapshot.
Note: Move all backup
files onto a safe server after running the backup so that they don’t take up space on
Orchestrator.
- Archive the var directory. The location of the directory to use
for backup will differ depending on the version of Orchestrator currently installed. The
table below displays the directory
options.
Orchestrator Release Version |
var Folder Location |
Older than v2.3 |
C:\Program Files (x86)\Aspera\var_Orchestrator |
v2.3 and later |
C:\Program Files (x86)\Aspera\Orchestrator\www\var |
- Archive the config directory. The location of the directory to use
for backup will differ depending on the version of Orchestrator currently installed. The
table below displays the directory options.
Orchestrator Release Version |
var Folder Location |
Older than v2.3 |
C:\Program Files (x86)\Aspera\Orchestrator\config |
v2.3 and later |
C:\Program Files (x86)\Aspera\Orchestrator\www\config |
Again, be sure to move all backup files onto a safe server after running
the backup so that they don’t take space on Orchestrator.
- Files in the following folder are overwritten with the new release
files:
C:\Program Files (x86)\Aspera\Orchestrator