13.07.2015 Views

Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3Upgrading <strong>Picture</strong> <strong>Perfect</strong> version 4.0/4.5.1 to <strong>4.6</strong>41Upgrade version 4.5.1 to <strong>4.6</strong>Once all items listed under Prerequisites are in place, follow the steps below to upgrade your <strong>Picture</strong><strong>Perfect</strong> 4.5.1 <strong>Enterprise</strong> system to version <strong>4.6</strong>.Note 1: The nethost server must be the first server to be upgraded to the new version.Note 2: Remember to back up your <strong>Picture</strong> <strong>Perfect</strong> 4.5.1 licenses. The licenses are valid and can be used in version <strong>4.6</strong>.A. Determine the downtime schedule and inform all operators of the downtime schedule(database freeze schedule)The downtime can be estimated based on the size of the database to be converted and otherfactors, such as the time to reinstall the new OS version, reusing the same servers, and latencybetween nethost and subhost to be configured.In a scenario with a database containing 500K person records, no network latency, and re-usingthe same servers requiring OS installation, we can calculate a downtime between 4 to 6 hoursper server. For a server experiencing network latency, please add 2 to 4 hours to this time. ForAIX servers, add at least 1 hour.Note:This estimate does not include getting the micro controllers back online with the server.B. <strong>Picture</strong> <strong>Perfect</strong> nethostB.1 Database conversion process1. Log in to the current <strong>Picture</strong> <strong>Perfect</strong> 4.5.1 nethost server.2. Record the old server database sizes (person, badge, notes, all history, micro, category,department, and micro_relation tables).This information can be compiled from the following files:/cas/db/backup/table_desc.dat (for reference to table name and id)/cas/db/backup/table_size.dat (for table record sizes based on table id)3. Check the database for illegal characters and fix any reported issues.Follow the instructions in <strong>Picture</strong> <strong>Perfect</strong> 4.5 Installation <strong>Manual</strong>, Chapter 3, “Verify theexisting database".4. Back up the database in the current production system before the upgrade of base, badgeand other packages where applicable (image, tours, graph) with contents verification.Preferably, back up in separate files for each item (for example, one file with base and badge,one file with images, etc.).Follow the instructions in <strong>Picture</strong> <strong>Perfect</strong> 4.5 Installation <strong>Manual</strong>, Chapter 3, “Back updatabase, configuration, and custom files”, section “Back up database”.5. Perform the Backup > History archive to Disk File task and then repeat the same scenariowith Force Roll Over option into another file to capture all existing history data.Follow the instructions in <strong>Picture</strong> <strong>Perfect</strong> 4.5 Installation <strong>Manual</strong>, Chapter 3, “Backing updatabase, configuration, and custom files”, section “Archive history and force rollover".

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!