PGP Universal Server 2.1.2 User manual

PGP® Universal Server 2.12

Upgrade Guide

Version Information

PGP Universal Server Upgrade Guide. PGP Universal Server Version 2.12.0. Released October 2009.

Copyright Information

means, electronic or mechanical, for any purpose, without the express written permission of PGP Corporation.

Trademark Information

PGP, Pretty Good Privacy, and the PGP logo are registered trademarks of PGP Corporation in the US and other countries. IDEA is a trademark of

Ascom Tech AG. Windows and ActiveX are registered trademarks of Microsoft Corporation. AOL is a registered trademark, and AOL Instant

Messenger is a trademark, of America Online, Inc. Red Hat and Red Hat Linux are trademarks or registered trademarks of Red Hat, Inc. Linux is a

registered trademark of Linus Torvalds. Solaris is a trademark or registered trademark of Sun Microsystems, Inc. AIX is a trademark or registered

trademark of International Business Machines Corporation. HP-UX is a trademark or registered trademark of Hewlett-Packard Company. SSH and

Secure Shell are trademarks of SSH Communications Security, Inc. Rendezvous and Mac OS X are trademarks or registered trademarks of Apple

Computer, Inc. All other registered and unregistered trademarks in this document are the sole property of their respective owners.

Licensing and Patent Information

The IDEA cryptographic cipher described in U.S. patent number 5,214,703 is licensed from Ascom Tech AG. The CAST-128 encryption algorithm,

implemented from RFC 2144, is available worldwide on a royalty-free basis for commercial and non-commercial uses. PGP Corporation has secured a

license to the patent rights contained in the patent application Serial Number 10/655,563 by The Regents of the University of California, entitled Block

Cipher Mode of Operation for Constructing a Wide-blocksize block Cipher from a Conventional Block Cipher. Some third-party software included in PGP

Universal Server is licensed under the GNU General Public License (GPL). PGP Universal Server as a whole is not licensed under the GPL. If you would

like a copy of the source code for the GPL software included in PGP Universal Server, contact PGP Support (

https://pgp.custhelp.com). PGP

Corporation may have patents and/or pending patent applications covering subject matter in this software or its documentation; the furnishing of this

software or documentation does not give you any license to these patents.

Acknowledgments

This product includes or may include:

• The Zip and ZLib compression code, created by Mark Adler and Jean-Loup Gailly, is used with permission from the free Info-ZIP implementation,

developed by zlib (

http://www.zlib.net). • Libxml2, the XML C parser and toolkit developed for the Gnome project and distributed and copyrighted

under the MIT License found at

http://jakarta.apache.org/), web

server (

http://www.apache.org/), Jakarta Commons (http://jakarta.apache.org/commons/license.html) and log4j, a Java-based library used to parse

HTML, developed by the Apache Software Foundation. The license is at

www.apache.org/licenses/LICENSE-2.0.txt. • Castor, an open-source, data-

binding framework for moving data from XML to Java programming language objects and from Java to databases, is released by the ExoLab Group

under an Apache 2.0-style license, available at

http://www.castor.org/license.html. • Xalan, an open-source software library from the Apache Software

Foundation that implements the XSLT XML transformation language and the XPath XML query language, is released under the Apache Software

License, version 1.1, available at

http://xml.apache.org/xalan-j/#license1.1. • Apache Axis is an implementation of the SOAP ("Simple Object Access

Protocol") used for communications between various PGP products is provided under the Apache license found at

http://www.apache.org/licenses/LICENSE-2.0.txt. • mx4j, an open-source implementation of the Java Management Extensions (JMX), is released

under an Apache-style license, available at

http://mx4j.sourceforge.net/docs/ch01s06.html. • jpeglib version 6a is based in part on the work of the

Independent JPEG Group. (

http://www.ijg.org/) • libxslt the XSLT C library developed for the GNOME project and used for XML transformations is

distributed under the MIT License

http://www.opensource.org/licenses/mit-license.html. • PCRE version 4.5 Perl regular expression compiler,

http://www.pcre.org/license.txt. • BIND Balanced

Binary Tree Library and Domain Name System (DNS) protocols developed and copyrighted by Internet Systems Consortium, Inc. (

http://www.isc.org) •

http://net-snmp.sourceforge.net/about/license.html. • NTP version 4.2

developed by Network Time Protocol and copyrighted to various contributors. • Lightweight Directory Access Protocol developed and copyrighted by

The OpenLDAP Foundation. The license agreement is at

http://www.openldap.org/software/release/license.html. Secure shell OpenSSH version 4.2.1

developed by OpenBSD project is released by the OpenBSD Project under a BSD-style license, available at

http://www.openbsd.org/cgi-

bin/cvsweb/src/usr.bin/ssh/LICENCE?rev=HEAD. • PC/SC Lite is a free implementation of PC/SC, a specification for SmartCard integration is released

under the BSD license. • Postfix, an open source mail transfer agent (MTA), is released under the IBM Public License 1.0, available at

http://www.opensource.org/licenses/ibmpl.php. • PostgreSQL, a free software object-relational database management system, is released under a

BSD-style license, available at

http://www.postgresql.org/about/licence. • PostgreSQL JDBC driver, a free Java program used to connect to a

BSD-style license, available at

http://jdbc.postgresql.org/license.html. • PostgreSQL Regular Expression Library, a free software object-relational

database management system, is released under a BSD-style license, available at

http://www.postgresql.org/about/licence. • 21.vixie-cron is the Vixie

• JacORB, a Java object used to facilitate communication between processes written in Java and the data layer, is open source licensed under the

GNU Library General Public License (LGPL) available at

is an open-source implementation of a CORBA Object Request Broker (ORB), and is used for communication between processes written in C/C++ and

Vanderbilt University. The open source software license is available at

http://www.cs.wustl.edu/~schmidt/ACE-copying.html. • libcURL, a library for

downloading files via common network services, is open source software provided under a MIT/X derivate license available at

under a BSD-style license, available at

libpopt, a library that parses command line options, is released under the terms of the GNU Free Documentation License available at

to communicate with the Intel Corporation AMT chipset on a motherboard, is distributed under the GNU Public License, available at

http://www.cs.fsu.edu/~engelen/soaplicense.html. • Windows Template Library (WTL) is used for developing user interface components and is

distributed under the Common Public License v1.0 found at

http://opensource.org/licenses/cpl1.0.php. • The Perl Kit provides several independent

utilities used to automate a variety of maintenance functions and is provided under the Perl Artistic License, found at

http://www.perl.com/pub/a/language/misc/Artistic.html. • rEFIt - libeg, provides a graphical interface library for EFI, including image rendering, text

rendering, and alpha blending, and is distributed under the license found at

reserved. • Java Radius Client, used to authenticate PGP Universal Web Messenger users via Radius, is distributed under the Lesser General Public

License (LGPL) found at

http://www.gnu.org/licenses/lgpl.html.

Export Information

Export of this software and documentation may be subject to compliance with the rules and regulations promulgated from time to time by the Bureau

of Export Administration, United States Department of Commerce, which restricts the export and re-export of certain products and technical data.

Limitations

The software provided with this documentation is licensed to you for your individual use under the terms of the End User License Agreement provided

with the software. The information in this document is subject to change without notice. PGP Corporation does not warrant that the information meets

your requirements or that the information is free of errors. The information may include technical inaccuracies or typographical errors. Changes may be

made to the information and incorporated in new editions of this document, if and when made available by PGP Corporation.

4

1

Contents

Introduction

What is PGP Universal Server? 1

PGP Universal Server Product Family 2

Who Should Read This Guide 2

Common Criteria Environments 2

Symbols Used in This Guide 3

Getting Assistance 3

Getting product information 3

Contact information 4

Upgrading the PGP Universal Server 5

Overview 5

Best Practices for Upgrade 8

Supported Client and PGP Universal Server Version Combinations 9

Licensing the Upgrade 9

Upgrading Clusters 10

Backing Up the Data and Organization Key 10

Configuring the PGP Universal Server 11

Restoring Configuration and Data 11

Migrating Settings from PGP Universal Server 2.0.6 17

Migrating Policy and Proxy Settings from Version 2.0.6 17

Supporting Legacy Client Software 18

Handling Confidential Messages for Legacy Clients 18

Upgrading Clusters 19

Mail Policy Best Practices 19

Reproducing 2.0.6 Proxy Settings 24

Setting: Always Encrypt Internal Mail 25

Setting: Applying Mail Policy for Authenticated Connections Only 25

Setting: Decrypting Email upon Receipt 29

Migrating a PGP Keyserver 31

Overview 31

PGP Keyserver and PGP Universal Server Feature Comparison 32

Extracting the PGP Keyserver Data 34

Stopping the PGP Keyserver Service 34

Locating the Database Directory 34

Locating the PGP Export Utility 35

Running the PGP Export Utility on the PGP Keyserver Database 35

i

PGP® Universal Server 2.12 Contents

Configuring the PGP Universal Server During Setup 37

Migrating Key Data During Setup 37

Migration of Keyserver Data 44

Migration and Key Reconstruction Blocks 51

Upgrading from Plug-ins to Proxies in PGP Desktop 9.x 52

Index 53

ii

1

Introduction

This Upgrade Guide describes how to upgrade PGP Universal Server software,

and how to migrate your data to new versions. It explains how to upgrade

previous versions of PGP Universal Server to version 2.12.0, and how settings

from PGP Universal Server 2.0.6 migrate to the mail policy settings of PGP

Universal Server 2.5 and later. It also describes how to migrate the keys and

key reconstruction blocks on a PGP Keyserver to the PGP Verified Directory

feature of a new PGP Universal Server.

This section provides a high-level overview of PGP Universal Server.

In This Chapter

What is PGP Universal Server? ..................................................................1

PGP Universal Server Product Family ........................................................2

Who Should Read This Guide ....................................................................2

Common Criteria Environments.................................................................2

Symbols Used in This Guide ......................................................................3

Getting Assistance .....................................................................................3

What is PGP Universal Server?

PGP Universal Server provides multiple encryption solutions managed from a

single console.

PGP Universal Server with PGP Universal Gateway Email gives you secure

messaging: it transparently protects your enterprise messages with little or no

user interaction.

The PGP Universal Server also replaces the PGP Keyserver product with a built-

in keyserver, and the PGP Admin product with PGP Desktop configuration and

deployment capabilities.

It automatically creates and maintains a Self-Managing Security Architecture

(SMSA) by monitoring authenticated users and their email traffic. You can also

send protected messages to addresses that are not part of the SMSA. The PGP

Universal Server encrypts, decrypts, signs, and verifies messages automatically,

providing strong security through policies you control.

1

PGP® Universal Server 2.12 Introduction

PGP Universal Satellite, a client-side feature of PGP Universal Server, extends

PGP security for email messages all the way to the computer of the email user,

it allows external users to become part of the SMSA, and it gives end users the

option to create and manage their keys on their own computer (if allowed by

the PGP administrator).

PGP Universal Server Product Family

PGP Universal Server functions as a management console for a variety of

encryption solutions. You can purchase any of the PGP Desktop applications or

bundles and use PGP Universal Server to create and manage client installations.

You can also purchase a license that enables PGP Gateway Email to encrypt

email in the mailstream.

The PGP Universal Server can manage any combination of PGP encryption

applications. PGP encryption applications are:

 PGP Universal Gateway Email provides automatic email encryption in the

gateway, based on centralized mail policy. This product requires

administration by the PGP Universal Server.

 PGP Desktop Email provides encryption at the desktop level for mail, files,

and AOL Instant Messenger traffic. This product can be managed by the

PGP Universal Server.

 PGP Whole Disk Encryption provides encryption at the desktop level for

an entire disk. This product can be managed by the PGP Universal Server.

 PGP NetShare provides transparent file encryption and sharing among

desktops. This product can be managed by the PGP Universal Server.

Who Should Read This Guide

This Upgrade Guide is for the person or persons who will be upgrading the

software or migrating the data of your organization’s PGP Universal Server

environment. These are the PGP administrators.

This guide is also intended for anyone else who wants to learn about how PGP

Universal Server works.

Common Criteria Environments

To be Common Criteria compliant, please refer to the best practices shown in

PGP Universal Server 2.9 Common Criteria Supplemental. Note that these best

practices supersede recommendations made elsewhere in this and other

documentation.

2

PGP® Universal Server 2.12 Introduction

Symbols Used in This Guide

Notes, Cautions, and Warnings are used in the following ways.

Note: Notes are extra, but important, information. A Note calls your attention

to important aspects of the product. You will be able to use the product

better if you read the Notes.

Caution: Cautions indicate the possibility of loss of data or a minor security

breach. A Caution tells you about a situation where problems can occur

unless precautions are taken. Pay attention to Cautions.

Warning: Warnings indicate the possibility of significant data loss or a major

security breach. A Warning means serious problems will occur unless you

take the appropriate action. Please take Warnings very seriously.

Getting Assistance

For additional resources, see these sections.

Getting product information

The following documents and online help are companions to the PGP Universal

Server Administrator’s Guide. This guide occasionally refers to information that

can be found in one or more of these sources:

 PGP Universal Upgrade Guide—Describes the process of upgrading your

PGP Universal Server.

 PGP Universal Mail Policy Diagram—Provides a graphical representation

of how email is processed through mail policy. You can access this

document via the PGP Universal Server online help.

 Tutorials—Provides animated introductions on how to manage the mail

policy feature in PGP Universal Server 2.5 and later, and how upgraded

PGP Universal Server settings migrate into the new mail policy feature.

You can also access all the documentation and tutorials by clicking the

online help icon in the upper-right corner of the PGP Universal Server

screen.

 The administrative interface and PGP Universal Satellite for Windows and

Mac OS X include online help.

 PGP Universal Server and PGP Satellite release notes are also provided,

which can have last-minute information not found in the product

documentation.

3

PGP® Universal Server 2.12 Introduction

Once PGP Universal Server is released, additional information regarding the

product is added to the online Knowledge Base available on PGP Corporation’s

Support Portal (

https://pgp.custhelp.com).

Contact information

All PGP customers have access to the comprehensive set of tools and

discussion forums available on the PGP Support Portal.

The PGP Support Portal provides access to tutorials, recent support briefs, the

Knowledge Base, and other valuable technical information.

Contacting Technical Support

 To learn about PGP support options and how to contact PGP Technical

Support, please visit the PGP Corporation Support Home Page

(

https://pgp.custhelp.com).

 To access the PGP Support Knowledge Base or request PGP Technical

Support, please visit PGP Support Portal Web Site

(

https://pgp.custhelp.com). Note that you may access portions of the

PGP Support Knowledge Base without a support agreement;

however, you must have a valid support agreement to request

Technical Support.

 For any other contacts at PGP Corporation, please visit the PGP Contacts

Page (

http://www.pgp.com/about_pgp_corporation/contact/index.html).

 For general information about PGP Corporation, please visit the PGP Web

Site (

http://www.pgp.com).

 To access the PGP Support forums, please visit PGP Support

(

http://forum.pgp.com). These are user community support forums hosted

by PGP Corporation.

4

2

Upgrading the PGP

Universal Server

This chapter describes how to upgrade previous versions of PGP Universal

Server to version 2.12.0.

In This Chapter

Overview ....................................................................................................5

Licensing the Upgrade ...............................................................................9

Upgrading Clusters...................................................................................10

Backing Up the Data and Organization Key .............................................10

Configuring the PGP Universal Server .....................................................11

Restoring Configuration and Data ............................................................11

Overview

The upgrade process deletes all data on the system. If you want to preserve

your existing user data and configuration settings, you will need to create a

backup to an external location before upgrading, and then restore the backup to

the new installation after upgrade. You will need both the backed up data file

and the Organization Key used to encrypt and decrypt the backup file.

Caution: It is not possible to upload backups of 2GB or larger through the

PGP Universal Server web interface. Contact PGP Support (PGP Corporation

Support Home Page (https://pgp.custhelp.com)) for help restoring your data.

The only supported upgrade path to PGP Universal Server software version 2.12

is from version 2.5.3 or later. You will not be able to restore data directly to

2.12.0 from any version older than 2.5.3. If you are running a version older than

that, you must first upgrade to version 2.5.3.

Before you upgrade to PGP Universal Server 2.12.0, you must back up your

data. Restore the data after upgrade. You can migrate directly to PGP Universal

Server version 2.12.0 from any of the following previous versions:

 2.5.3

 2.6.0

 2.6.1

5

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

 2.6.2

 2.6.3

 2.7.0

 2.7.1

 2.7.2

 2.8.0

 2.8.1

 2.8.2

 2.8.3

 2.9.0

 2.9.1

 2.10.0

Note: On PGP Universal Server 2.12.0, you can only restore backed-up data

from version 2.5.3 and later.

 To upgrade from a version of PGP Universal Server prior to 2.5.3:

1 Back up your version 2.0.x system data to an external location. (See the

PGP Universal Administrator's Guide for installation and backup and restore

instructions and best practices.)

2 Upgrade to version 2.0.6 using the 2.0.6 CD. Restore your backed-up data.

3 Back up your version 2.0.6 data to an external location.

4 Upgrade to version 2.5.0 using the 2.5.0 CD. Restore your backed-up data.

5 Go to

http://www.pgp.com/downloads/updates/index.html.

6 One at a time, download and install PUP updates for versions 2.5.1, 2.5.2,

and 2.5.3.

Note: You do not need to back up and restore data when upgrading using

a PUP file. However, it is always a good idea to have a current backup

when performing maintenance tasks on PGP Universal Server.

Note: When installing multiple PUP updates, download and install them

one at a time. If you download multiple PUP updates before you begin

installing them them, only the first installation succeeds.

7 Back up your version 2.5.3 data to an external location.

8 Upgrade to version 2.12.0 using the 2.12.0 CD.

9 Restore your backed-up data.

6

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

 To upgrade from PGP Universal Server 2.5.3 or 2.6.x:

1 Back up your data to an external location.

2 Upgrade to version 2.12.0 using the 2.12.0 CD.

3 Restore your backed-up data.

 To upgrade from PGP Universal Server 2.9.x or 2.10.x (on a computer

with Internet access):

1 Log in to PGP Universal Server administrative interface.

2 Select the System tab, and then click Updates.

3 Click Check for Updates and wait for the check to complete. This may

take several minutes. If an available update is available, it appears in the

list.

4 Click the Install icon, and then follow the on-screen instructions.

Note: If you are upgrading from a version prior to 2.9.1, you must perform

the procedure twice, first to upgrade to 2.9.1, and then again to upgrade to

2.12.0.

Note: You do not need to back up and restore data when upgrading using a

PUP file. However, it is always a good idea to have a current backup when

performing maintenance tasks on PGP Universal Server.

Note: You must have a valid maintenance agreement with PGP Corporation

to access PUP updates. For more information, see

http://www.pgp.com/products/upgrade.

 To upgrade from PGP Universal Server 2.7.x, 2.8.x, 2.9.x, or 2.10.x (on a

computer without Internet access):

If you are upgrading to 2.12.0 from 2.7.x, 2.8.x, 2.9.x, or 2.10.x (on a computer

without Internet access), then download the PUP file updates from the

Licenses and Entitlement Manager System (LEMS) at

https://lems.pgp.com. If

you don't have access to LEMS, request the update using a link in your order

fulfillment email.

Note: If you are upgrading from a version prior to 2.9.1, you must perform

the procedure twice, first to upgrade to 2.9.1, then again to upgrade to 2.12.

Note: For upgrades (from versions 2.7.x or 2.8.x) to take effect on computers

with more than 4GB of RAM, you must manually restart them after the

upgrade completes.

Once you have downloaded (and extracted if necessary) the PUP update and

copied it to the computer running PGP Universal Server:

7

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

1 Log in to PGP Universal Server administrative interface.

2 Select the System tab, and then click Updates.

3 Click Upload Update Package.

4 Click Browse, select the PUP update file, and then click Open. The update

appears in the list.

5 Click the Install icon, and then follow the on-screen instructions.

Note: You do not need to back up and restore data when upgrading using a

PUP file. However, it is always a good idea to have a current backup when

performing maintenance tasks on PGP Universal Server.

Note: You must have a valid maintenance agreement with PGP Corporation

to access PUP updates. For more information, see

http://www.pgp.com/products/upgrade.

Best Practices for Upgrade

 PGP Corporation recommends that you install and test the upgrade in a lab

or staging environment before integrating the upgrade into your network.

 Back up the Organization Key and all the data from your PGP Universal

Server before you upgrade. Make sure you back up your data to an external

location, because the upgrade process will delete all data stored on your

PGP Universal Server. For more information, see the documentation you

received with your version of PGP Universal Server. If you do not or cannot

use FTP to back up your data to an external location, contact PGP Support (

PGP Corporation Support Home Page (

https://pgp.custhelp.com)).

 Remember to keep a copy of the installation media saved, in case you

need to revert back to the previous version.

 During upgrade, the PGP Universal Server does not process email. Before

you upgrade your PGP Universal Server, make sure it has been temporarily

removed from the mailflow.

 If your network includes an MTA, reconfigure the MTA to stop routing

email through the PGP Universal Server.

a If all your company’s email routes through your PGP Universal

Server, configure your MTA to halt outbound email processing.

Or

If email that matches criteria in your MTA content filter routes through

the PGP Universal Server, configure the MTA to queue email that

matches the criteria.

b Configure the MTA to queue incoming email that normally

passes through the PGP Universal Server; for example, signed

and/or encrypted email.

8

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

c Examine the PGP Universal Server log files to make sure that no

email is passing through the PGP Universal Server.

d Upgrade your PGP Universal Server and restore your user data.

e After your PGP Universal Server has been successfully upgraded,

reconfigure your MTA to resume routing email to the PGP

Universal Server.

Note: You can find more information online about moving to PGP Universal

Server 2.12.0 at the PGP Corporation website (http://www.pgp.com).

Supported Client and PGP Universal Server Version Combinations

PGP Corporation supports backward compatibility for clients only. For example,

PGP Universal Server 2.0 is not supported for use with PGP Desktop 9.9.

PGP Universal Server 2.12 supports managing policy of these versions (and

subsequent maintenance releases of each) of PGP Desktop:

 9.5.3

 9.6.3

 9.7.1

 9.8.2

 9.9.0

PGP Universal Server 2.12 supports managing policy of these versions (and

subsequent maintenance releases of each) of PGP Universal Satellite:

 2.5.3

 2.6.3

 2.7.1

 2.8.2

 2.9.0

Note: Policy options for features that are non-existent in supported legacy

versions are ignored by those installations.

PGP Universal Server 2.12 provides limited management support (without

policy) back to PGP Desktop version 9.0 and PGP Universal Satellite version 2.0.

For more information, see Supporting Legacy Client Software (on page

18).

Licensing the Upgrade

If you have a valid subscription license or Perpetual 2.0 License, you will not

need a new license to use PGP Universal Server 2.12.0.

9

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

Upgrading Clusters

All members of a PGP Universal Server cluster must be running the same

software version. Secondary servers will not inherit the software upgrade from

the Primary; you have to upgrade each server individually. You should upgrade

all the clustered servers at the same time. However, remember that email will

not be moving through your network if you have all the servers down at the

same time.

Before you upgrade you cluster members, remove your PGP Universal Servers

from the network, so that no email or port traffic is moving through them. Do

not break the cluster. Upgrade your Primary first, then upgrade your

secondaries. After all cluster members are upgraded, restore your cluster to

your network.

Some of the features in PGP Universal Server 2.0.0 were set through mail proxy

settings, but are set through mail policy in PGP Universal Server 2.5 and later.

Because you can control proxy settings independently for each cluster member,

the settings can be different for each cluster member. However, policy is set on

the Primary cluster member and replicated across the cluster. The only settings

recreated on the Primary are specific to the Primary. These settings will not be

applied to the Secondaries. If you had different proxy settings across your

cluster, these will also not be recreated. Upgrading your cluster from 2.0.6 to

2.5 and later is more complicated than a simple installation. For more

information on upgrading clusters, see Migrating Settings from PGP Universal

Server 2.0.6 (on page

17).

Backing Up the Data and Organization Key

Warning: Back up the Organization Key and all the data from your PGP

Universal Server before you upgrade. Make sure you back up your data to an

external location, because the upgrade process will delete all data stored on

your PGP Universal Server. For more information, see the documentation you

received with your version of PGP Universal Server.

Caution: If you do not or cannot use FTP to back up your data to an external

location, contact PGP Support (PGP Corporation Support Home Page

(https://pgp.custhelp.com)).

1 Export the entire keypair of the Organization Key. From

Organization/Organization Keys, select the Organization Key.

The Organization Key Info dialog appears.

2 Click Export.

The Export Key dialog appears.

10

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

3 Select Export Keypair and type the passphrase. Click Export to save the

Organization Keypair to your desktop.

4 Back up the server data and configuration to an external server location.

From System/Backups, click Backup Location.

The Backup Location dialog appears.

5 Specify the remote location where you want the data to be saved, and click

Save. It is important that you save the data somewhere other than the PGP

Universal Server itself, because all data on the PGP Universal Server will be

erased during upgrade.

The Backups card appears.

6 Click Backup Now to back up the data.

Configuring the PGP Universal Server

Now that you have the data from the previous version saved, it can be brought

into a PGP Universal Server during configuration using the Setup Assistant.

This procedure describes how to upgrade to the latest version of the software

and restore all the data and configuration information to the PGP Universal

Server.

 To upgrade and restore your data and configuration information:

1 Install the upgrade software as described in the PGP Universal Server

Administrator’s Guide.

2 Begin configuration of the PGP Universal Server using the Setup Assistant.

For more information on setting up the PGP Universal Server, see the PGP

Universal Server Administrator’s Guide.

3 Continue setting up the PGP Universal Server.

Restoring Configuration and Data

 To restore backed-up data during the configuration of a server:

1 Access the Setup Assistant for the new server.

2 On the Welcome screen, read the text and then click Forward.

The End User License Agreement screen appears.

3 Read the text, click I Agree at the end, then click Forward.

The Setup Type screen appears.

11

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

4 Select Restore, then click Forward.

12

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

The Import Organization Key screen appears.

5 Upload a file containing your Organization Key, then click Forward.

13

PGP® Universal Server 2.12 Upgrading the PGP Universal Server

The Upload Current Backup File screen appears.

6 Click Choose File, select the backup file from which you want to restore,

then click OK. When the Upload Current Backup File screen appears again,

click Forward.

Caution: It is not possible to upload backups of 2GB or larger through the

PGP Universal Server web interface. Contact PGP Support(PGP

Corporation Support Home Page (https://pgp.custhelp.com)) for help

restoring your data.

The backup will install.

14

Page is loading ...

PGP Universal Server 2.1.2 User manual

PGP Universal Server 2.1.2 User manual

Related papers

Other documents