Transferring the Archive to Another Computer

From Ara Irititja KMS Wiki

Jump to: navigation, search

This section describes the process of moving an established Archive's database and media to another computer/server or to creating a 'read-only' copy of the Archive from a master Archive. These instructions are not to be confused with importing archive content from the FileMaker version of the Ara Irititja software, these instructions can be found here.

If you are receiving your Archive preprepared by Ara Irititja or your archive was previously hosted on an Ara Irititja server, the database and media files for your Archive will be supplied to you on disc or external drive. If this is the case, proceed to Setting up a new Archive Instance suitable for Import.


Contents

Exporting Database and Media Files

Archive content consists of a database and media files. The archive's Backup function within the Administrative pages of the Archive allows for the creation of a zip file containing a complete 'dump' of the database. However, media files must be manually copied from the server where the Archive software is installed.

Before commencing an export, it would be advisable to deal with any unconfirmed Archive Items that remain outstanding in the System.

Below are instructions to create export files from a WAMPStack or MAMPStack installation. If you are not using either of these Apache/MySQL/PHP configurations, you will need to amend these instructions to suit your own configuration.

  1. Login to the Archive using the Super Administrator account.
  2. Navigate to Administration Home → Backup. In the 'Archive Backup Wizard' ensure that the 'Database Only' radio button is selected and click 'Next'.
  3. Once the Archive has finished creating the database zip file, it will begin downloading. You may be asked to specify a location to save the file, otherwise the file will be downloaded and saved to the browsers default downloads directory. You will need to copy the downloaded zip file to an external hard-drive for later use.
  4. On the computer/server where the Archive software files reside, open the DocumentRoot directory.
    MAMPStack DocumentRoot: /Applications/mampstack/apache2/htdocs/
    WAMPStack DocumentRoot: C:\Program Files\BitNami WAMPStack\apache2\htdocs\

  5. Copy the 'media' directory inside the DocumentRoot to an external hard-drive for later use.


Importing Database and Media Files

Before you can import the database and media files into another Archive instance, you must ensure that:


Database Incompatibility Issues:
The database software (MySQL) is, by default, case-insensitive on Windows operating systems, but case-sensitive on Mac/Unix/Linux operating systems. Unfortunately, this means an export from a Windows system can only be imported into another Windows system. However this is not true for Mac/Unix/Linux, which can be imported into all operating systems.

For further information see the Identifier Case Sensitivity section of the MySQL User Manual.


Setting up a new Archive Instance suitable for Import

Configuring an Archive to accept the database and media of another requires minor deviation from the normal installation process. Below is a summary of the installation process. It includes links to the complete instructions, as well as additional steps to allow the database and media of the source archive to be installed.

  1. Installation of Required Server Software
  2. Configuring the Server's Root Directory
  3. Installing and Configuring Red5 Media Server
  4. Archive Software Configuration and Initial Import
    These instructions have been written for users who are upgrading from the FileMaker Archive, instead you will skip the import process to create an empty Archive installation. It is extremely important that the Archive Identifier and Profiles Receive Archive Numbers properties of the new Archive instance are identical to the source Archive.
    As you work through the configuration process, ensure that:
    • In step 2 you have entered the same Archive Identifier code and Profiles Receive Archive Numbers value as the source Archive.
    • In step 5 you have selected 'Don't import anything, leave as empty shell.' as the import source.

  5. Once you have completed the Archive Setup and successfully run the Software Diagnostic Tool, you may need to upgrade the Archive software to the same version as the source Archive. To install any upgrades, you will need to refer to the Release Notes for specific instructions on upgrading the software. You should have received these update packages on disc, however Ara Irititja can supply them upon request.
  6. Proceed to Installing Database and Media Files.


Note: If your installation is being used as a 'read-only' copy of the master archive, then setting up a new archive instance only needs to occur once. Any subsequent content update made to the 'read-only' archive can be achieved by installing the database and media files. However, you must continue to ensure that the versions of Archive software are the same.


Installing Database and Media Files

The process of installing the database and media files is the inverse of the export process. You must reinstate the database and copy the media directory into the Archive software. It would be wise to ensure that no one else is accessing the archive while the import process is being carried out.

  1. On the computer/server where the Archive software resides, open the DocumentRoot directory.
    MAMPStack DocumentRoot: /Applications/mampstack/apache2/htdocs/
    WAMPStack DocumentRoot: C:\Program Files\BitNami WAMPStack\apache2\htdocs\

  2. Copy the 'media' directory from the external hard-drive to replace the media directory inside the DocumentRoot.
  3. Change the permissions of the 'media' directory (inside the DocumentRoot directory) and all its enclosed files and folders so that Apache is the owner and has read, write and execute permission enabled.

    To do this with MAMPStack:
    Open a Terminal window and enter the following two commands:
    sudo chown -R daemon:admin /Applications/mampstack/apache2/htdocs/media
    sudo chmod -R 755 /Applications/mampstack/apache2/htdocs/media
    You may need to enter your password when prompted.

    To do this with WAMPStack:
    Check that the 'Administrators' group has read, write and execute permissions enabled for the C:\Program Files\BitNami WAMPStack\apache2\htdocs\media directory. It is likely that these permissions have already been enabled.

  4. Copy the database zip file from the external hard-drive to the Archive's 'public' directory.
    MAMPStack Public: /Applications/mampstack/apache2/htdocs/public/
    WAMPStack Public: C:\Program Files\BitNami WAMPStack\apache2\htdocs\public\

  5. Login to the Archive using the Super Administrator account.
  6. Navigate to Administration Home → Restore. In the 'Archive Restore Wizard', ensure that the 'Database Only' radio button is selected. In the 'Restore Zip File' popup list, select the database zip file that you previously copied into the 'public' directory. Click 'Next'.
  7. Logout of the Archive once the database restoration process has finished. You can remove the database zip file from the 'public' directory.
Personal tools
Namespaces
Variants
Actions
Getting Started...
User Manual
Components
Discussion
Development
Toolbox