Backing Up/Restoring and Exporting/Importing Data

Solstice Enterprise Manager 4.1 Management Information Server (MIS) Guide

Chapter 5

Backing Up/Restoring and Exporting/Importing Data

This chapter explains the procedures for protecting your data through backing up and restoring.

This chapter describes the following topics:

Section 5.1 Guidelines for Backing up and Restoring Data
Section 5.2 Guidelines for Importing and Exporting Data
Section 5.3 Exporting Network View Data
Section 5.4 Converting Legacy Data

5.1 Guidelines for Backing up and Restoring Data

To protect your system from serious data loss, periodically back up both the database and network views data. There are two ways to do this:

Solstice Backup and Restore
Solstice Enterprise Manager (Solstice EM) preparation procedures and your own backup utility (you can backup data online)

5.1.1 Testing Your Backups

Corrupt data can be transferred from source to destination and can go undetected until you restore the data and try to recover the database. To minimize this problem, test your database backups. Examples of test procedures are included in this section. A suggested schedule is to test backups at least every three months.

5.1.2 Preparing for Backup

The Database Backup/Restore Tool allows you to specify a file to which you can backup database information. Similarly, you can specify a file from which you can restore database information. The database must be up to do a backup. Similarly, the database must be down to restore it.

Use the Database Backup/Restore Tool to prepare for backups. During a backup, users can continue to make entries into the database. The entries are queued and then processed after the backup is completed. The Database Backup/Restore Tool can be brought up from either the Network Tools window or the command line.

To Perform a Backup

1. Type the following command:

em [-host <hostname>] &

2. Prepare for online backup by clicking Administration.

Note – The database must be up in order to do a backup.

3. On the Administration window, click Database Backup/Restore.

The Database Backup/Restore window displayed is shown in the following figure. Any data typed at this point is queued until the backup is complete.

FIGURE 5-1 Backup and Restore Window
4. In the File field, specify a file name where the data will be backed up.

5. Click Backup.

Back Up from the Command Line

Type the following command:

em_dbarchive

Restore from the Command Line

Type the following command:

em_dbrestore

5.1.3 Backing up and Restoring Network Views Data and Agents

Network views data are nodes created by users to logically model managed objects (network resources). These nodes point to network resources, which you can see graphically displayed in the Network Views. For instructions on how to view network view nodes and their attributes, refer to the Managing Your Network

Agents are associated with network view nodes. These agents are most commonly CMIP, RPC, and SNMP.

If network views data were lost or corrupted, you would have to recreate all nodes and their hierarchy. For larger networks, this task is a significant effort.

You may want to use the following guidelines for doing backups:

Whenever changes are made (for example, daily, or weekly)
Before changing the configuration of MIS or Solstice EM
Before recreating or rebuilding the database

After backup, you can find your backup files in the directory you specified. In order to change this default location, go to the current path and change the filename. These files must be left accessible to the Solstice EM user.

If your system crashes, MIS is designed to restore to normal condition when the system is rebooted. However, there may be times when you need to restore MIS manually. For example, if the database is damaged, a default installation is performed, or data has been removed and MIS does not restore itself. Under these conditions, you will need to use your latest backup files to restore the database.

5.1.4 Supporting Migration Paths

The migration path from Solstice EM 2.0 and 3.0 is supported in this version of the product. Also, you can import network views and agent data from one MIS to another MIS for data redundancy. Migration is supported for data that was imported in Solstice EM 2.1 using PMI tools. Database related tools cannot be used for migration.

To Restore the Database From the Network Tools Window

1. Prepare for online restore by clicking Administration on the Network Tools window.

Note – The database should be down in order to restore it. Run em_services -stop to halt it.

2. Click Database Backup/Restore.

Any data typed at this point is queued until the data restoration is complete.

3. In the text field, specify a filename where the data will be restored.

From the Command Line

Before restoring, make sure the backup file is located in the directory you specify. To restore a database, do the following:

1. Type the following command:

/opt/SUNWconn/bin/em_dbrestore -file <filename>
Note – If you installed the product in a different directory, substitute your partition name for /opt.
2. To implement the restore, type the following command:

em_services -start
5.1.5 Copying Network Views and Agent Data

If your network views and agent data are damaged, or you want to copy network views and agent data from one MIS to another, you can do this from either the Network Tools or the command line.

Note – Make sure the target MIS is not processing other transactions and requests.

The import operation does not correct inconsistencies that may occur due to ongoing MIS activity during the import.

To Copy Network Views and Agent Data

1. On the Network Tools window, click Administration \xd4 Network View
Import/Export.

2. Enter the name of the file to which your network view objects will be imported.

Optionally, you can type a container name and a parent name.

3. Click the Object menu.

4. Select Import.

From the Command Line
1. Start the Topology Export/Import Tool from the command line by typing the following command:

em_topoimex -file <filename> -import [options]
2. In place of the filename variable, type the following command:

em_topoimex -file topo_db_info -import
To import all network view-related information from a file called topo_db_info. Refer to the following table.

TABLE 5-1 Commands for Exporting Data
Option Description

-file <filename>
Specify the name of file to export to or import
from.

-clear
Clears network views and agents from MIS.

-export
Exports network views from the MIS. -file <filename>
option is required when using this option.

-container <container>
Exports a container. Must be used in conjunction with export.

-debug
Turns on debugging messages.

-help
Prints a list of options (with descriptions) for the <em_topoimex> command.

-host <host>
Specifies a remote MIS server.

-import
Imports network views to the MIS. -file <filename> option is required when using this option.

-parent <view name>
Imports a previously exported container under <view name>. Must be used in conjunction with -import.

-remote <MIS server>
Specifies a remote MIS to clear, export, or import.

-quiet
Specifies quiet mode. No question asked for -clear and
-import options.

3. When prompted, type your password.

When the export is complete, the system prompt returns,
4. type ls <filename>.

CODE EXAMPLE 5-1 Sample Export File

### Exported data for topoType

CREATE

{

OC=topoType

OI='topoTypeDBId=NULL/topoTypeId="Device"'

topoTypeAllBaseOf='{

"Interface",

"OMC",

"BTS",

"Hub",

"Router",

"Printer",

"VLR",

"Host",

"Pc",

"Sunws",

"HLR",

"BSC",

"Server",

"XCDR",

"Bridge"

}'

topoTypeAllDerivedFrom='{

}'

topoTypeAllLegalArcs='{

"Link",

"LinkContainer"

}'

topoTypeAllLegalChildren='{

}'

topoTypeBaseOf='{

"Router",

"Bridge",

"Hub",

"Host",

"XCDR",

"BTS",

"BSC",

"OMC",

"VLR",

"HLR",

"Interface",
5.1.6 Using Solstice Backup and Restore

Another way to backup and restore data is to use the Solstice Backup product. This is a standalone product that can be used to backup all types of data. The Solstice product not only has backup and restore capabilities, but it allows you to specify the following:

Incremental backup and restore
Point restore

Solstice^TM Backup^TM Solaris Data Backup Utility, Solstice Backup, and Solstice Backup Turbo software form a product family that delivers heterogeneous data protection available for enterprise computing environments. This enterprise-wide backup and recovery solution supports virtually every network operating system, desktop operating system, and storage device on the market. Solstice Backup provides consistent, reliable data protection, reduces the costs of administration and minimizes backup time.

To use the Solstice Backup Configuration Utility

1. Indicate the various client system types running in the network.

2. Use the scroll bar to choose the total number of clients in the network.

3. Check any desired application options.

The "SunSoft part nos." window indicates the products which are necessary to protect your storage management environment.

5.2 Guidelines for Importing and Exporting Data

To back up all or part of your network views data for your MIS, use the Network Views Import/Export. Using this tool, you export Sun's data to an ASCII formatted file. Later, if you need to restore network views data, you import the latest backup (export) file.

When exporting the entire network views database, you can use a "container export" feature. This feature exports the network view nodes within and beneath the container in the view hierarchy. With the network view nodes, all the associated agent objects and FDN tables are also exported.

Later when you import a file of network views data that was exported using the container feature, you assign a "parent" node for the container that you want to import.

You'll need Solstice Backup J.1 and Solstice Backup Database Module for InformixTM 1.0.

5.2.1 What is Exported?

The attributes within specified object types are exported. This data includes all objects within the following branches of MIS:

topoTypeDB--all topoTypeNodes
topoNodeDB--topoNodes (Each topoNode is identified within the export data by its topoNodeId.)
topoViewDB--all topoNodes (This data must be associated with its corresponding topoNode within the export data.)
topoViewNodeDB--all topoViewNodes (This data must be correctly associated with its parent topoView and with its corresponding topoNode.)
internetClassId--SNMP agent objects (This object must be associated with each topoNode object that references it.)
agentTableType="RPC"--RPC agent objects (This object must be associated with each corresponding topoNode object.)
agentTableType="CMIP"--CMIP agent objects (This object must be associated with each topoNode object that references it.)
subsystemId="EM-MIS"--FDN table

5.2.2 What is Not Exported?

The following information is not exported:

Request data--emApplicationType="Collection" and emApplicationType="NerveCenter"
Log data
User-defined managed objects

5.3 Exporting Network View Data

When you back up network view data, it is placed in an ASCII file. The exported MIS information will:

be editable so that scripts can generate it.
be interchangeable between different hardware platforms.
Note – Make sure the target MIS is not processing other transactions and requests.

The export operation does not correct inconsistencies that may occur due to ongoing MIS activity during the export.

To Export Network View Data

1. Click Administration \xd4 Network View Import/Export.

2. Enter the name of the file where your network view objects will be exported.

Refer to the following figure. You may also use the browse button to navigate to a specific directory or file. Optionally, you can type a container name and a parent name.

3. Click Object \xd4 Export.

FIGURE 5-2 Network View Import and Export Window
From the Command Line
You can start Network View Import/Export by typing the following command:

em_topoimex -file <filename> -export [options]

1. In place of the filename variable, type the name of the file where you want to export data.
If you are not in the target directory, remember to type the full path name. For example, to export all network view-related information in MIS to a file called topo_db_info, use the following command:

em_topoimex -file topo_db_info -export
The following table lists the optional parameters for exporting data.
2. When you are prompted, type your <login ID> and <password>.

Your access to the Network View Export/Import functions depends on the permissions granted to you.

3. When the export is complete, the system prompt returns. To ensure the file to which you exported has been created, type ls <filename>.< /blockquote>

If more than one network view database exists (due to MIS-MIS communication), then the export operation provides the following options:

Export network views branches from an MIS that can be reached from the local MIS.
Export a container within a network views branch from a specified MIS. (All objects under that node are exported.)

In situations where a non-unique topoNodeName container object is specified, the export tool prompts you to select the proper one.

5.3.1 Exporting and Importing Log Records

The em_imex command can be used to import or export log objects from or to an ASCII file. This command is invoked from the Event Logs application by selecting either:

File \xd4 Import File
File \xd4 Export to File from the Event Logs menu bar
Invoke the em_imex by typing em_imex [options] &

The optional parameters for the em_imex command are described in the following table.

TABLE 5-2 Command Line Options for em_imex
Option Description

-type <log|em_topoimex>
Type of operation.

-host server
Specify the <server> of a remote MIS.

-c
Specify "-c" when using the "-import" option to include the "object creation" events for the corresponding objectCreation events found in the log.

-e <moi> or export <moi>
Specify the managed object to export.

-f <filename>
Specify the name of the file to read or create.

-i or -import
Import operation (by default).

5.4 Converting Legacy Data

To convert legacy data, refer to the Installation Guide

In addition to converting data from a previous version of Solstice EM, you may want to convert network views data and agent objects to the new MIS.

Sun Microsystems, Inc.
Copyright information. All rights reserved.
Doc Set | Contents | Previous | Next | Index

Option	Description
-file <filename>	Specify the name of file to export to or import from.
-clear	Clears network views and agents from MIS.
-export	Exports network views from the MIS. -file <filename> option is required when using this option.
-container <container>	Exports a container. Must be used in conjunction with export.
-debug	Turns on debugging messages.
-help	Prints a list of options (with descriptions) for the <em_topoimex> command.
-host <host>	Specifies a remote MIS server.
-import	Imports network views to the MIS. -file <filename> option is required when using this option.
-parent <view name>	Imports a previously exported container under <view name>. Must be used in conjunction with -import.
-remote <MIS server>	Specifies a remote MIS to clear, export, or import.
-quiet	Specifies quiet mode. No question asked for -clear and -import options.

Option	Description
-type <log\|em_topoimex>	Type of operation.
-host server	Specify the <server> of a remote MIS.
-c	Specify "-c" when using the "-import" option to include the "object creation" events for the corresponding objectCreation events found in the log.
-e <moi> or export <moi>	Specify the managed object to export.
-f <filename>	Specify the name of the file to read or create.
-i or -import	Import operation (by default).