FAQ

  • Server Administration: Moving collections from one server to another (4/25/2011)

Need assistance for CONTENTdm?

Server Administration: Moving collections from one server to another

Last review: April 25, 2011

Description: Especially when doing a major CONTENTdm Server upgrade, it may be useful to copy all collection data to a new machine that has a clean installation of CONTENTdm.

Resolution

A common upgrade scenario is to do a clean installation of the latest CONTENTdm version (e.g., CONTENTdm 6) on a new machine while keeping the old machine running (e.g., CONTENTdm 5.x) for a period of evaluation. In this scenario, you need to migrate a copy of the collection data files from the original server to the new server, and then build the index.

1. Copy the collection files to the CONTENTdm 6 Server. Set the file permissions on the collection files as follows:

Windows: Web server must have Read; CONTENTdm Administrators group must have Read & Write.
Linux: The Apache user (default is "web") must own the files and have Read, Write & Execute permissions.

2. Import the collection(s) as usual in CONTENTdm Administration (see Importing an Existing CONTENTdm Collection).

NOTE: If there are a large number of collections being migrated, it may be easier to migrate the catalog.txt file and manually update the file paths. To do this, copy docs/catalog.txt from the old server to the new one. Edit the file paths so that they are correct for the new server. If the migration is from Windows to Linux or vice-versa, be sure to update the line breaks in the catalog.txt file to match the target operating system. Resave the file to have line breaks as CR/LF or LF, as appropriate.

3. Build the index as described in the Administration Guide for your server platform. Use the "indexALL" option as follows:

Windows: bin\manageCdmServices.exe -indexALL
Linux: scripts/cdmServices.pl -indexALL