Legacy System Upgrades

Posted on December 7, 2011 by newbrandmedia

The Path to an Upgrade

Migrating From SAFEnet 5.6.3 (sp3) to SAFEnet 6.2.16 (sp4)

I. Comprehensive Site Survey

  • a. Meet to MonDyn System Engineer to discuss options, process flow, path forward
  • b. Review process with MonDyn Engineering Team
  • c. Perform detailed system diagnostic, analysis and asset discovery (report)
  • d. Create Plan of Action with Milestones for Implementation (Based on Discovery)
  • e. Create Final Upgrade Price Quote (Based on Discovery)
  • f. Review and Receive Upgrade Sign-off from MonDyn Engineering Team

II. Purchase New Servers (Database and Application) and Workstations*

  • a. Install 2008 Server
  • b. Install 2008 SQL Server
  • c. Install MS Windows 7
  • d. Install SAFEnet 6.2.16 sp4 on New Servers
  • e. Configure Disaster Recovery and Backup

III. Purchase SAFEnet 5.6.3 sp3 to 6.2.16 sp4 Upgrade Software*

IV. Acquire the existing SAFEnet 5.6.3 sp3 Database Information from Customer*

  • a. Perform Database Conversion (conversions can be performed on-site, depending on the information security needs of the client due to sensitivity or classification level of the data being converted)

V. Install Converted Database to New Servers (with customer release)*

VI. Test Servers and Configurations*

  • a. Change Server Names to Match Sites
  • b. Change IP Addresses to Match Sites

VII. Setup New Workstations*

  • a. Synchronize with New Upgraded Servers

*Performed at Factory – unless otherwise required by customer Synchronize

VIII. Create System Cut-Over Plan (based on customer site specifics and requirements)

IX. Install on Network and Cut-Over to New Servers (as detailed in plan)

X. Test all Alarm Points and Access Control Functionality

XI. Train Users on Changes – SOFTWARE UPGRADE COMPLETE

The new SAFEnet 6.2.16 sp4 System and Related Hardware

I. All Legacy SAFEnet Hardware is 100% Compatible with new SAFEnet Software Versions

  • a. While not necessary, it is recommended that any client running legacy PPU hardware (175 & 180 processor boards), convert to PB2000 hardware, as PPU hardware is no longer manufactured

II. If the client site is running on legacy hardware, we recommend upgrading the field panels at the time of upgrade. This is primarily due to the risk that parts availability issues may arise from unforeseen end-of-life announcements from our suppliers on any hardware older than the IDC (Integrated Digital Controller) Line.

III. A Phased Implementation Plan for the installation of new SAFEnet Hardware can be created with assistance from the Monitor Dynamics “Blue Team”. This Implementation can be modified to meet the budgetary and operational needs of the client.

IV. Hardware Conversions can be phased-in during the SAFEnet 6.2.16 sp4 Software Upgrade for best results.

Be the first to leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Centra Security Services