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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

28<strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> <strong>Enterprise</strong> <strong>Edition</strong><strong>User</strong> <strong>Manual</strong>Upgrade version 4.0 to <strong>4.6</strong> with no spare serversOnce all item listed under Prerequisites are in place, follow the steps below to upgrade your <strong>Picture</strong><strong>Perfect</strong> 4.0 <strong>Enterprise</strong> system to version <strong>4.6</strong>.Note:The nethost server must be the first server to be upgraded to the new version.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 if 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, re-using thesame servers requiring OS installation, we can calculate a downtime between 4 to 6 hours perserver. For a server experiencing network latency, add two to four hours to this time. For AIXservers, add at least one 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.0 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 references 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.0 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.0 Installation <strong>Manual</strong>, Chapter 3, “Back upDatabase, Configuration, and Custom Files".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 instructions in <strong>Picture</strong> <strong>Perfect</strong> 4.0 Installation <strong>Manual</strong>, Chapter 3, “Back upDatabase, Configuration, and Custom Files”, section “Archive History and ForceRollover".

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

Saved successfully!

Ooh no, something went wrong!