Cisco Systems 1 manual Importing the archived files, Gunzip -c archivefilenamecpio -icvB *switch

Page 58

$archive –p <tadwop password> -f <archive file location> [-I] [-[{TH}]C] {startstop}

The I flag runs the archive process immediately instead of scheduling it. If the I flag is not specified, the archive process will be scheduled as a cron job which runs daily at 3:00 AM.

The H flag indicates to Cisco PVM to include historical information in the archive.

The T flag indicates to Cisco PVM to include transactional (raw statistics) information in the archive.

The C flag indicates to Cisco PVM to include configuration information in the archive.

Note:

1.To archive the NAM and DSG configurations, use the flag TC, and to archive the OLAP configuration information use the flag HC. Specifying just the C flag is equivalent to specifying both.

2.The archive is done using the standard Oracle export utility. The exported data is compressed for data storage.

Importing the archived files

Data that has been archived can be re-imported. To import the archive, you have to first unzip it using the command:

gunzip -c archive_filenamecpio -icvB “[switch]”

where the switch is the type of archive.

Once unzipped, the archive can be imported using the command:

imp tadwop@{cnam spdw} file=/directory/filename ignore=y full=y

where:

–cnam is used for transaction archives

–spdw is used for historical archives

–the directory is the location used for the original backup

–the file name is from the unzipped list of files containing.dmp extensions

Example:

If you want to re-host PVM from Host A to Host B, the following procedure would enable you to export and import the configuration information:

On Host A:

$ su – pvmadm

$ cd /<PVM_INSTALL_DIR>/server/bin

$ archive –p <Operator password> -f < filename> -TCI start

On Host B:

$ su – pvmadm

$ imp file=<filename> userid=tadwop/tadwop@CNAM ignore=y full=y

For more information about database related information, see the Cisco PVM User Guide.

Cisco Internal Use Only

Copyright © 2006 Cisco Systems, Inc. All rights reserved.

Page 58 of 66

Image 58

Contents Corporate Headquarters USA Cisco Performance Visibility Manager ART Monitoring Data Collection and Traffic AnalysisTraffic Analysis including Top-N Analysis Historical InformationNAM GUI Drill down CiscoWorks and Ldap IntegrationSample Deployment Scenario PVM in LAN and WAN Basic questions about the Problems to be addressed Placing Cisco NAM in Your NetworkTypical workflow for deploying Cisco PVM Configure the NAMs in Your NetworkDeploy PVM and add the NAMs in Cisco PVM Start monitoring your network using Cisco PVM Create the Datasource Groups DSGs in Cisco PVMNAM Setup Usage ScenariosUser Setup Cisco PVM Initial SetupUser Management through the GUI User management through Ldap Mapping Ldap users to PVM roles Adding a NAM through the GUICisco Internal Use Only Importing Multiple Devices DCR Export File Import File FormatsUser created CSV file Datasource Group DSG Creation Cisco Internal Use Only Scenario 1 Traffic Profiling Contd Cisco Internal Use Only Cisco Internal Use Only Cisco Internal Use Only Contd Scenario 2 Proactive Monitoring Create an ART Group that carries traffic you are interestedContd Click the Setup tab Click the Thresholds menu item Click Add Contd Cisco Internal Use Only PVM displays the details of the threshold violation Scenario 3 Troubleshooting Verify the link utilization on the client Branch Router Click RefreshClick Connect Cisco Internal Use Only Overview of PVM functionality Traffic Analysis using Cisco PVMMonitoring Cisco Internal Use Only Aggregation Schemes Real-Time and Trend Charts Report ViewsDrill-downs Report Name Drill-Down Reports Available ReportingCisco Internal Use Only Art Setup Application Response Time Analysis in Cisco PVMArt Reports Cisco Internal Use Only ART Report Archives Baselining and Alerts in Cisco PVM Cisco Internal Use Only Generating Snmp Traps Alerts in Cisco PVM Cisco Internal Use Only Software Cisco PVM Requirements and SizingMinimum Server Requirements Hardware Minimum Client Requirements HardwareMaximum NAMs CPUs Cisco PVM Installation and UninstallationDisk Space Required Install Procedure Cd PVMINSTALLDIR/j2sdk142/binUninstall Procedure Start and Stop Procedure $su pvmadm $pvm stopTroubleshooting Tips Maintaining and Troubleshooting Cisco PVMArchiving Database ManagementPurging and retention period $su pvmadmGunzip -c archivefilenamecpio -icvB *switch Importing the archived filesConclusion Appendix Deployment Q&ACisco Internal Use Only Cisco Internal Use Only Deployment Troubleshooting Cisco Internal Use Only For More Information USA