Moving your Enterprise Server/Connect Server/P2P/Client installation to a new Linux machine

Description

This article describes how to move your transfer server, P2P or Client installation to a Linux system.

Follow the instructions below based on the system that the original, existing installation is located on.

Linux to Linux

1. Export connections

If you make use of the GUI application for your product and would like to transfer the saved connections to the new machine, you will need to export the connections to a file.

For each user on the system you would like to export connections for, follow the exporting and file saving steps in the following Knowledge Base article: How to Export and Import Connections. You can choose to export all or only a chosen selection of connections.

Shared connections do not need to be exported as they are moved with files in a later step. Therefore, you only need to export connections that individual users have saved for themselves.

2. Move files to the new Linux system

You are now ready to move files from your old machine to the new one. Copy over the following files to a temporary directory on your new Linux machine:

  • /opt/aspera/etc/aspera.conf
  • /opt/aspera/etc/aspera-license
  • /opt/aspera/etc/ui.conf
  • the exported connection files
  • (if you use Pre-Post scripts) /opt/aspera/var/aspera-prepost and any other scripts it calls
  • (if your product is Connect Server) /opt/aspera/etc/webpasswd

Note: You cannot use the same license on multiple systems as this is a violation of your license terms.

You may use the license from your original system on your new system if you will be uninstalling your Aspera product on the original system right away. For more information on where your license is located, see this article.

If your original product installation needs to stay up and running for a short period, you may ask your account manager for a temporary license to use on your new installation.

3. Prepare your new Linux system

The rest of the instructions apply to the new Linux machine. On the new Linux machine, make sure of the following:

  • The product is installed for which you are moving files.
  • Your new Linux system has the same system users that your previous system had and used as transfer users

For example, if your original installation of ES used transfer users janedoe, hpotter and aspera, your new Linux system must also have the users janedoe, hpotter and aspera.

To add a user, you can run the following commands:

# useradd username
# passwd username

If you can’t recall all the transfer users your previous system used, you can look at the aspera.conf file in the <users> section. It can be found in the files you copied to a temporary directory:

  • /path/to/temp/aspera.conf

4. Stop services and transfers

Close the product GUI application if it is open, and make sure any transfers have stopped.

Stop services with the following commands:

# service asperanoded stop
# service asperacentral stop
# service asperahttpd stop

5. Move the files of the old machine to their proper locations.

You can use the commands below to copy the files to their proper locations:

# cp /path/to/temp/aspera.conf /path/to/temp/aspera-license /path/to/temp/ui.conf /opt/aspera/etc

## if you use Pre-Post ##
# cp /path/to/temp/aspera-prepost /path/to/temp/script1 /path/to/temp/script2 ... /opt/aspera/var

## if you have Connect Server ##
# cp /path/to/temp/webpasswd /opt/aspera/etc

6. Import connections

If you exported connections from your previous machine (step 1), you will need to import them for your users. For each user on the system you would like to import connections for, follow the importing steps in the following Knowledge Base article: How to Export and Import Connections.

7. Modify configurations if necessary

Double check your configurations to ensure that they apply to your new machine. For example, docroot, bandwidth and network settings may need to be modified.

For your transfer users, the docroot path may or may not be the same on your new system. You can change this and other settings either through the GUI, the command line tool asconfigurator or directly through aspera.conf.

If your transfer server interacts with a web application, you will need to change the IP address in aspera.conf in the <server> section to the address of your new Linux system.

8. Restart services

Start services with the following commands:

# service asperanoded start
# service asperacentral start
# service asperahttpd start

9. (for Connect Server web UI users) Configure Apache

If you have a Connect Server and will be making use of the Connect Server web interface, make sure Apache is properly configured on your new Linux system. Instructions for configuring Apache for the Connect Server web UI are in the product manual.

10. You have now finished moving your installation from Linux to a new Linux system

Windows to Linux

Note: Aspera products on Linux systems do not have Hot Folder functionality, therefore you will not be able to transfer any existing Hot Folders to your Linux system.

1. Export connections

If you make use of the GUI application for your product and would like to transfer the saved connections to the new machine, you will need to export the connections to a file.

For each user on the system you would like to export connections for, follow the exporting and file saving steps in the following Knowledge Base article: How to Export and Import Connections. You can choose to export all or only a chosen selection of connections.

Shared connections do not need to be exported as they are moved with files in a later step. Therefore, you only need to export connections that individual users have saved for themselves.

2. Move files to the new Linux system

You are now ready to move files from your old machine to the new one. Copy over the following files to a temporary directory on your new Linux machine:

  • C:\Program Files (x86)\Aspera\product_name\etc\aspera.conf
  • C:\Program Files (x86)\Aspera\product_name\etc\aspera-license
  • C:\Program Files (x86)\Aspera\product_name\etc\ui.conf
  • the exported connection files
  • (if you use Pre-Post scripts) C:\Program Files (x86)\Aspera\product_name\var\aspera-prepost.bat and any other scripts it calls
Note: If you use Pre-Post scripts you will need to adjust any Windows batch scripting to a Linux-compatible script (Perl, Bash, and so on).

3. Prepare your new Linux system

The rest of the instructions apply to the new Linux machine. On the new Linux machine, make sure of the following:

  • The product is installed for which you are moving files.
  • Your new Linux system has the same system users that your previous system had and used as transfer users

For example, if your original installation of ES used transfer users janedoe, hpotter and aspera, your new Linux system must also have the users janedoe, hpotter and aspera.

To add a user, you can run the following commands:

# useradd username
# passwd username

If you can’t recall all the transfer users your previous system used, you can look at the aspera.conf file in the <users> section. It can be found in the files you copied to a temporary directory:

  • /path/to/temp/aspera.conf

4. Stop services and transfers

Close the product GUI application if it is open, and make sure any transfers have stopped.

Stop services with the following commands:

# service asperanoded stop
# service asperacentral stop

5. Move the files of the old machine to their proper locations.

You can use the commands below to copy the files to their proper locations:

# cp /path/to/temp/aspera.conf /path/to/temp/aspera-license /path/to/temp/ui.conf /opt/aspera/etc

## if you use Pre-Post -- note aspera-prepost.bat must be renamed to aspera-prepost ##
# cp /path/to/temp/aspera-prepost.bat /opt/aspera/var/aspera-prepost
# cp /path/to/temp/script1 /path/to/temp/script2 ... /opt/aspera/var

6. Import connections

If you exported connections from your previous machine (step 1), you will need to import them for your users. For each user on the system you would like to import connections for, follow the importing steps in the following Knowledge Base article: How to Export and Import Connections.

7. Modify configurations if necessary

Double check your configurations to ensure that they apply to your new machine. For example, docroot, bandwidth and network settings may need to be modified.

For your transfer users, the docroot path is likely not the same on your new system since you are moving from Windows. You can change this and other settings either through the GUI, the command line tool asconfigurator or directly through aspera.conf.

Note that if your transfer server interacts with a web application, you will need to change the IP address in aspera.conf in the <server> section to the address of your new Linux system.

8. Restart services

Start services with the following commands:

# service asperanoded start
# service asperacentral start

9. (for Connect Server web UI users) Configure Apache and Apache authentication

If you have a Connect Server and will be making use of the Connect Server web interface, make sure Apache is properly configured on your new Linux system. Instructions for configuring Apache for the Connect Server web UI are in the product manual.

You will need to create the web UI access password for your transfer users because this was not done on your Windows system. For each user, create a password with the following command:

# htpasswd /opt/aspera/etc/webpasswd transfer_user

10. You have now finished moving your installation from Windows to a new Linux system

Mac to Linux

1. Export connections

If you make use of the GUI application for your product and would like to transfer the saved connections to the new machine, you will need to export the connections to a file.

For each user on the system you would like to export connections for, follow the exporting and file saving steps in the following Knowledge Base article: How to Export and Import Connections. You can choose to export all or only a chosen selection of connections.

Shared connections do not need to be exported as they are moved with files in a later step. Therefore, you only need to export connections that individual users have saved for themselves.

2. Move files to the new Linux system

You are now ready to move files from your old machine to the new one. Copy over the following files to a temporary directory on your new Linux machine:

  • /Library/Aspera/etc/aspera.conf
  • /Library/Aspera/etc/aspera-license
  • /Library/Aspera/etc/ui.conf
  • the exported connection files
  • (if you use Pre-Post scripts) /Library/Aspera/var/aspera-prepost and any other scripts it calls
  • (if your product is Connect Server) /Library/Aspera/etc/webpasswd

3. Prepare your new Linux system

The rest of the instructions apply to the new Linux machine. On the new Linux machine, make sure of the following:

  • The product is installed for which you are moving files.
  • Your new Linux system has the same system users that your previous system had and used as transfer users

For example, if your original installation of ES used transfer users janedoe, hpotter and aspera, your new Linux system must also have the users janedoe, hpotter and aspera.

To add a user, you can run the following commands:

# useradd username
# passwd username

If you can’t recall all the transfer users your previous system used, you can look at the aspera.conf file in the <users> section. It can be found in the files you copied to a temporary directory:

  • /path/to/temp/aspera.conf

4. Stop services and transfers

Close the product GUI application if it is open, and make sure any transfers have stopped.

Stop services with the following commands:

# service asperanoded stop
# service asperacentral stop

5. Move the files of the old machine to their proper locations.

You can use the commands below to copy the files to their proper locations:

# cp /path/to/temp/aspera.conf /path/to/temp/aspera-license /path/to/temp/ui.conf /opt/aspera/etc

## if you use Pre-Post ##
# cp /path/to/temp/aspera-prepost /path/to/temp/script1 /path/to/temp/script2 ... /opt/aspera/var

## if you have Connect Server ##
# cp /path/to/temp/webpasswd /opt/aspera/etc

6. Import connections

If you exported connections from your previous machine (step 1), you will need to import them for your users. For each user on the system you would like to import connections for, follow the importing steps in the following Knowledge Base article: How to Export and Import Connections.

7. Modify configurations if necessary

Double check your configurations to ensure that they apply to your new machine. For example, docroot, bandwidth and network settings may need to be modified.

For your transfer users, the docroot path is likely not the same on your new system since you are moving from Mac. You can change this and other settings either through the GUI, the command line tool asconfigurator or directly through aspera.conf.

Note that if your transfer server interacts with a web application, you will need to change the IP address in aspera.conf in the <server> section to the address of your new Linux system.

8. Restart services

Start services with the following commands:

# service asperanoded start
# service asperacentral start

9. (for Connect Server web UI users) Configure Apache

If you have a Connect Server and will be making use of the Connect Server web interface, make sure Apache is properly configured on your new Linux system. Instructions for configuring Apache for the Connect Server web UI are in the product manual.

10. You have now finished moving your installation from a Mac to a new Linux system

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk