PHOTO ORGANIZER 2 MIGRATION

 

 

Who Should Migrate?

All users having Photo Organizer version eralier than 2.14 should migrate their Image Repository to maintain compatibility.

 

Why Migrate?

Before 2.14 the Image Repository stored all images (thumbnails, previews and originals) in the same volume, which was a great disadvantage, inhibiting the implementation of certain features that are comming with the 2.16 release.

The 2.14 Image Repostory stores the thumbnails, previews and originals in separate designated sub-volumes. This has two advantages:

  • It's easy to extend the repository to store photos in a large variety of dimensions while keeping the repository structured.
  • It is possible to back up sub-volumes separately, and create an external media library, where originals do not occupy valuable hard drive space but are stored on high capacity removable medias, that are mounted upon request.

Therefore, starting with 2.14 a new Image Repository has been created, one that implements sub-volumes.

 

The 2.6 Image Repository

The 2.6 repository is based on a single layer volume scheme, where volumes are in fact subdirectories in the Image Repository. This repository can be located anywhere on the server, with the restriction that it has to be owned by the user which runs the HTTP server.

The 2.6 repository also featured a completely automatic volume management algorithm, with volume auto increment and auto fill. For more information on these features refer to the Administrator section of Photo Organizer's Help.

The disadvantage of the 2.6 repository is that it stores all photos (original, preview and thumbnail) in the same volume.

 

The 2.14 Image Repository

The 2.14 repository enhances the 2.6 repository by creating sub-volumes, one for each photo format. Therefore in each volume there is a separate sub-volume for the thumbnails, one for the previews and one for the originals. Since most of the storage space will be occupied by the sub-volume that contains the originals, that sub-volume can be moved to a removable media allowing the system administrator to spare some hard drive space.

Once the originals are saved on a removable media, the system stays operational since the preview and thumbnail of each photo is still available. The 2.16 release will implement a feature that allow users to submit "mount requests" to the system administrator to mount a certain removable media that contains the desired original.

 

How to Migrate the Repository

If you install a 2.14 system from scratch, you don't have to migrate. If you upgrade an exisiting system, back it up creating a database dump (using the pg_dump utility) and by creating a copy of your Image Repository. Should anything go wrong, you have a chance to restore your system. After you are on the safe side, run the install script, or follow the manual upgrade instructions.

After you completed the upgrade, visit your PO installation and log in as administrator. Say, your Photo Organizer is accessible under the following url:

http://www.yourhost.com/po

Once you are logged in as administrator, visit the following url:

http://www.yourhost.com/po/migrate.php

It is important to mentiona that while this script is running do not interrupt it by pressing the STOP button on your browser. Depending on how many pictures you have the migration might take quite a long time. Let it run until it says "Done". Once the migration is completed make sure to remove the migrate.php file.

This script will migrate your exsting database and Image Repository, providing you with accurate tracing information for each image file apart. Normally every operation should conclude as OK and you should see not a single trace stating: FAILED

Although, for image entries that have no photo attached (when the PO logo is displayed instead) the migration will fail because no physical image file was found in the repository for that image entry.

 

Comments and corrections are welcome at balint@k-i-s.net.