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.

26<strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> <strong>Enterprise</strong> <strong>Edition</strong><strong>User</strong> <strong>Manual</strong>IntroductionThe purpose of the process described in the following sections is to upgrade a <strong>Picture</strong> <strong>Perfect</strong><strong>Enterprise</strong> <strong>Edition</strong> version 4.0 or 4.5.1 to version <strong>4.6</strong>. At the end of the process, all servers areinstalled with the new version, are communicating, and are synchronizing global data records withthe network host server (also referred to as nethost, top level host, or master server).PrerequisitesThe following items have to be in place before proceeding with the upgrade of <strong>Picture</strong> <strong>Perfect</strong> 4.0/4.5.1 to <strong>4.6</strong> (also refer to <strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> Installation <strong>Manual</strong>, Chapter 3, “Upgrade checklist for<strong>Picture</strong> <strong>Perfect</strong> v4.0 to v<strong>4.6</strong>”):1 Media kit <strong>Picture</strong> <strong>Perfect</strong> media kit <strong>4.6</strong>.2 Licenses Save a copy of the <strong>Picture</strong> <strong>Perfect</strong> 4.0 or 4.5.1 licenses (/cas/.PP.key) for those serversthat need to be upgraded and request new <strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> licenses from UTC Fire &Security. If you are currently running <strong>Picture</strong> <strong>Perfect</strong> 4.5.1, you can re-use the licenses for<strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong>; no new licenses are required.3 Database table sizes Keep a copy of the database sizes as a reference and to serve as a foundation to grow thesystem. The table size information can be found in the following files:/cas/db/backup/table_size.dat (table sizes with reference to table IDs)/cas/db/backup/table_desc.dat (table names with reference of table IDs).4 Database and microcontroller dataintegrity5 Target server OSinstallationTo expedite the upgrade and avoid any inconvenience during the database conversionprocess, we recommend running the following utilities:/cas/bin/chkchars.sh This utility reports any <strong>Picture</strong> <strong>Perfect</strong> illegal characters./cas/bin/vmicroThis utility reports any micro table misconfigurations.If you are planning to reuse or provide new servers to install <strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong>, make surethe operating system version installed is Linux Red Hat 5.6 for Dell servers or AIX version 6.1TL6 for IBM RISC servers.6 Server connectivity Make sure all servers participating in the upgrade process are connected to the network andreachable from each other.If optional spare servers are used, make sure they can connect to the source (old version)and target (new version) servers, since we will be transferring data files back and forth.7 Database freeze Once the upgrade process has begun, we strongly recommend to stop making changes tothe database servers. This assures minimum impact to database synchronization between allservers during the installation. If, however, database changes (not related to Historytransactions) are required during the upgrade time, these changes must be written down sothat they can be applied in the new system with replication and synchronization.Note: Please see section FAQs on page 97 for more detail.8 Micro controllermaintenanceThe minimum micro firmware versions required with <strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> are as follows:Micro 5/PXN: 4.0.3Micro 5/PXN+: R113Direct Door: R113Note: We strongly recommend using the currently shipped micro controller hex codeversion.

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

Saved successfully!

Ooh no, something went wrong!