Veritas NetBackup (tm) PureDisk Remote Office Edition 6 Maintenance Patch 1 (MP1) - Symantec Corporation - June 30, 2006


Veritas NetBackup (tm) PureDisk Remote Office Edition 6 Maintenance Patch 1 (MP1) - Symantec Corporation - June 30, 2006


PureDisk Remote Office Edition 6
Maintenance Pack NB_PDE_60_MP1_283808
Installation Instructions

Symantec Corporation
July 17, 2006

Table of Contents:
1.  Maintenance pack description
2.  Installing the maintenance pack
3.  New Features
4.  Known Issues

1. Maintenance Pack Description
Symantec recommends that you install the PureDisk maintenance pack NB_PDE_60_MP1_283808 to address a number of issues that were identified during extensive tests with PureDisk.  Maintenance pack NB_PDE_60_MP1_283808 is a cumulative maintenance pack.  Therefore, you can install this maintenance pack without installing the previous patches, NB_PDE_60_P01_282217 and NB_PDE_60_P02_282729, first.

Apply this maintenance pack to the storage pool authority (SPA) node only.  The PureDisk installation software automatically distributes and installs the PureDisk software on all other nodes in the storage pool.  When you add additional PureDisk nodes to a storage pool upon which this maintenance pack has been installed, the maintenance pack automatically installs on the new nodes.  The installation process differs slightly depending on whether you have existing PureDisk software or whether you are a new customer.  For more information on installation, see "Installing the Maintenance Pack" in this README file.

The maintenance pack creates the following files during the installation:

•  On the SPA:
a.  /Storage/log/NB_PDE_60_MP1/timestamp-main.log is the log file of the installation.
b.  /etc/puredisk/NB_PDE_60_MP1-main-timestamp is an empty file that is created upon successful completion of the installation.  This marker file enables you to verify that MP1 is installed successfully on the whole storage pool.

•  On all nodes, including the SPA:
a.  /Storage/log/NB_PDE_60_MP1/timestamp-node.log is the log file of the installation on a particular node.
b.  /etc/puredisk/NB_PDE_60_MP1-node-timestamp is an empty file that is created upon successful completion of the installation on one particular node.  This marker file enables you to verify that MP1 is installed successfully on the node.
c.  The installation software saves files, settings, and database entries that are changed by the maintenance pack to the following directory:  /Storage/log/NB_PDE_60_MP1/timestamp-backup/.

2. Installing the Maintenance Pack
The following subsections describe the installation procedure and explain the actions performed by the installation software.

2.1  Preparing to Install MP1
The following subsections describe a pre-installation procedure and the installation procedure itself.  The pre-installation procedure prepares your environment for the MP1 patch.  

2.1.1   Procedure to perform prior to installing the PureDisk MP1 software.  These instructions differ depending on whether you are an existing customer or a new customer, as follows:

•  If you are an existing PureDisk customer, take the following steps:

1. Run a disaster recovery backup according to the procedure in the PureDisk Remote Office Edition Administrator's Guide, revision 6.0.2.  This ensures that you can recover your PureDisk environment in the event that something goes wrong with the MP1 installation.  This backup preserves the PureDisk databases.

2. Log out from the PureDisk Web UI and close all browser windows.

•  If you are a new PureDisk customer, the MP1 installation procedure requires that you install the GA release first and then the MP1 release.  Use the instructions in this README file and the instructions in the PureDisk Remote Office Edition Getting Started Guide.  The getting started guide provides more information on this process, but the general installation procedure is as follows:

1. Use the instructions in the getting started guide to install the PureDisk 6.0 release.  As part of the installation process, you run the command.  Make sure that this command has completed successfully.

2. Use the instructions in this README file to install the MP1 release on the storage pool.  The MP1 installation software upgrades the storage pool to the MP1 release.

3. Return to the Getting Started guide and continue the installation with the step "Configuring the SMTP mail server".

2.1.2  Installing MP1
Perform the following procedure to install the MP1 software:

1. Download the maintenance pack using the "Download Now" link, near the bottom of this TechFile.

Use rcp or scp to copy the downloaded file, NB_PDE_60_MP1_283808.tar, to the /root directory of the PureDisk node that is hosting the SPA.

2. Log on to the node that hosts the SPA as user root.

3. Type cd /root to go to the /root directory.

4. Type the following command to verify the integrity of the maintenance pack:

md5sum /root/NB_PDE_60_MP1_283808.tar

This command computes the md5 checksum of the maintenance pack file.  The md5 checksum of the maintenance pack file must match:
md5sum: 2e836edd3bf6878ed5a120e64a5690eb  
If you obtain a different checksum, the maintenance pack was corrupted during download. Try to download the maintenance pack again.

5. Type the following command to unpack the maintenance pack software:

tar -C / -xf /root/NB_PDE_60_MP1_283808.tar ./opt

6. Type the following command to run and install the maintenance pack software:


If the topology.ini file is encrypted, the software prompts you for the password to decrypt this file.

The maintenance pack automatically pushes the software to all nodes in the storage pool and all clients.

At the end of a successful installation, the software prompts you to encrypt the topology.ini file.

If you are an existing PureDisk customer, your system and the Web User Interface (UI) might be noticeably slower after you install MP1.  This is a temporary situation, and it is due to the following factors:

• The MP1 installation software restarts the content routers.  This action reloads the fingerprint cache, and this takes a long time if you have a lot of data (segments).

• The MP1 installation software restarts the controller.  After this, the client agents reconnect to the controller, more or less simultaneously, to upgrade each client's agent software.  This activity takes longer if you have many clients.

7. (Conditional)   Monitor the client agent upgrade jobs.

Perform this step if you are an existing PureDisk customer.

Take the following actions to monitor the client agent upgrade jobs:

A. Invoke the Web UI.
B. Click the Workflows tab.
C. Select the Agent update workflow.

Due to the heavy load on the system, some of the agent update jobs can fail.  If any jobs fail, that agent becomes deactivated.  When you activate these agents again, PureDisk schedules a new upgrade job.  If the client is connected to the network, the PureDisk schedules the job within 15 minutes.  To determine which agents are deactivated, take the following actions:

A. Invoke the Web UI.
B. Click the Data management tab.
C. Select the Deactivated client agents by storage pool view, which is the third view from the left.

8. Perform a disaster recovery backup, which preserves both the databases and the content router data.

Use the instructions in the PureDisk Remote Office Edition Administrator's Guide: .
Updates to this Administrator's Guide are posted in the following TechNote:

9. (Conditional)  Verify that all the agent upgrade jobs completed.

Perform this step if you are an existing PureDisk customer.

The upgrade jobs time out after 14 days.  If a client does not connect to the storage pool within that 14 day period, start another upgrade job for that client.  For information about how to upgrade an agent manually, see the PureDisk Remote Office Edition Getting Started Guide.

2.2  Notes on Actions Performed by ""
Read this section if you are an existing PureDisk customer.  The following list describes how the installation software affects an active storage pool.

•  Before the MP1 patch begins processing, the installer checks for running jobs and takes the following actions:

•  If critical jobs are running, such as rerouting jobs, the patch stops.

•  If noncritical jobs are running, the installer notifies the user.  The user can choose to stop the patch or to let the patch kill all the running jobs.  The patch does not proceed until all running jobs are finished.

•  During installation of the maintenance pack on an already deployed system, some services are stopped and restarted.  This can cause running jobs to fail.  Symantec recommends that you keep system activity minimal during the maintenance pack installation, for example, by disabling backup policies, and so on.

•  The installation software overwrites all the server configuration files.  This removes all configuration file settings that were made manually, with one exception.  The exception is that it preserves all changes in the [mail] section of the agent.cfg file on the storage pool authority.  It preserves the smtpserver, mailfrom, and other fields that pertain to escalations.

If you made any changes to the configuration files, go to the Configuration tab in the Web UI after you install MP1.  Enter your changes in the configuration file editor.  Then, go to the Workflows tab, and run the update configuration files workflow to push the changes to all agents.

3. New Features
The following sections describe the major new features that PureDisk 6.0 MP1 supports.  For more information on these features and for information on smaller features, see the PureDisk Remote Office Edition Getting Started Guide or the PureDisk Remote Office Edition Administrator's Guide.

3.1 Solaris Client Support
PureDisk 6.0 MP1 now includes a Solaris client for Solaris versions 8, 9, and 10.

3.2 Network Drive Backup Capability
PureDisk 6.0 MP1 enables you to back up a network drive on Windows clients.

3.3  Additional Parameters for Unattended Installs on Windows Clients
The installation command for installing Windows clients now includes the following parameters:

/INSTALL=option, which installs or upgrades clients according to the option specified.
/CONNECTTIMEOUT=value, which specifies an upper limit on Web service connection times.
/TIMEOUT=value, which specifies an upper limit on Web service request times.
/NOREGISTER, which installs the agent software on the client but does not register the agent software with the storage pool authority.

3.4  Command Line Options for Linux and Solaris Unattended Installs
PureDisk supports several options to the command for unattended installs on Linux and Solaris clients.

3.5  Conversion Scripts
This release installs conversion scripts in the /opt/pdconfigure/scripts/support directory.  The following scripts enable you to convert the topology.ini file from using IP addresses to DNS host names, or vise versa:

The previous scripts convert the topology.ini file, the configuration files, and the PureDisk databases in your running installation.

You can use another new script,, during the process of changing the IP address of a PureDisk node.

NOTE:  Use these conversion scripts only when consulting with a Symantec Enterprise Technical Support staff person.

3.6  Scripts for Starting and Stopping Services
The MP1 release includes the following script that enables you to stop and start services:

/etc/init.d/puredisk action [service] [service] ...

For action, specify one of the following:  start, stop, status, reload, or restart.  If no service is specified, the script stops all services.  You can specify one or more individual services if instructed to do so in a documented PureDisk procedure or when working with a Symantec technical support staff person.

3.7  New Permissions and Permission Changes
The following additional permissions have been added:

• Reroute
• Update_agents
• Replicate
• Report

Members currently in the Administrators group will see these permissions added automatically to that group.

New users are now added automatically to the Users group.

3.8  New Reporters Group
A new group, Reporters, was added at the World level.  Members in this group can run reports and view dashboards.

3.9  New Facility to Log Information About Files Changing During a Backup
The Parameters tab of the backup policy configuration screens includes the Enable change detection field.  You can select Yes or No.  The default is No.  When enabled, this field detects and logs information about files that undergo size changes while the backup is being performed.

3.10  Garbage Collection Policies
Garbage consists of unreferenced or expired data on content routers or the metabase engine.  You can create garbage collection policies to remove these unneeded files from your PureDisk nodes.

3.11  Ability to Set Parameters as Default
In the Parameters tabs of the dialog boxes that you complete when you define a policy, you can specify that you want to save the parameters you specified as defaults.  Subsequent policies that you create inherit these parameters.

3.12  Changes to File Restores
When you click Find files in the Web UI, PureDisk invokes the restore wizard, which lets you restore to alternate clients and alternate directories.  

When you select files to restore, you can now select more than one file to restore.

3.13  Dashboards
Dashboards provide a quick status on a PureDisk component.  PureDisk provides the following dashboards:

• The capacity dashboard, which shows information about total and used capacity on the content router and metabase engine.

• The activity dashboard, which shows information about the PureDisk components that are running on all the nodes in your storage pool.

• The server agent dashboard, which shows information about running jobs and the jobs that completed most recently on the storage pool nodes (server agents).

• The client agent dashboard, which shows information about running jobs and the jobs that completed most recently on a selected department or a selected client agent.

3.14  Web Service Report Enhancements
The Web service reports have been redesigned.  These reports now generate information in XML format.  You can import the XML output into a spreadsheet.

3.15  Audit Trail
The audit trail is a log of the last 1000 actions performed by users.  It shows their user IDs and what actions they performed.  This information also appears in the /Storage/log/SPA_GUI.log.

3.16  Event Escalation Enhancements
You can configure PureDisk to use Simple Network Management Protocol (SNMP) to trap events.  You must preconfigure your SNMP server with the NetBackup MIB, which is included in the software distribution.

You can specify a range of severities for events.  For example, you can specify that PureDisk send a message when it logs error, critical, or bug events.

3.17  Monitor Workflow Changes
By default, the monitor workflow now runs every 8 hours at 45 minutes after the hour.  In addition, it monitors the software RAID configuration.  When the disks get too full, it sends an event.

3.18  Maintenance Workflow
By default, a maintenance workflow runs weekly on Saturday mornings.  This workflow cleans up old jobs and events.  In addition, it cleans the databases.  On client agents, this workflow removes old temporary files.

3.19  Statistics for Replication Jobs and the Restore Workflow
The statistics tab for replication jobs and for the restore workflow shows statistics that pertain to a replication or restore job run.

3.20  Backups for Network Shared Drives on Windows
PureDisk allows you to back up and restore a network shared drive on Windows platforms.

3.21  Configuration File Changes Propagated to Storage Pool
The Web UI allows you to make configuration changes in the Configuration tab and push the changes to all components.  All components in a storage pool should have the same configuration.

4. Known Issues
For the complete list of PureDisk 6.0 MP1 known problems, see the PureDisk Remote Office Edition Getting Started Guide that is included with this release: .

Updates to the Getting Started Guide are posted in the following TechNote:

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)