EMC® Ionix™
Network Configuration Manager
Version 4.1.1
Backup and Recovery Guide
P/N 300-013-083
REV A01
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 2009-2012 EMC Corporation. All rights reserved.
Published January, 2012
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION,
AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section
on EMC Powerlink.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.
2
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
Contents
Preface
Chapter 1
Backup and Recovery
Overview..................................................................................................................
Network Configuration Manager distributed architecture ..............................
Data locations ..........................................................................................................
Backup utilities........................................................................................................
Customer responsibilities ......................................................................................
Hot spare scenario ..................................................................................................
Backing up clustered and distributed database environments........................
10
11
12
14
16
17
18
Glossary
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
3
Contents
4
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
Preface
.
As part of an effort to improve and enhance the performance and capabilities of its product
lines, EMC periodically releases revisions of its hardware and software. Therefore, some
functions described in this document may not be supported by all versions of the software or
hardware currently in use. For the most up-to-date information about product features, refer
to your product release notes.
If a product does not function properly or does not function as described in this document,
please contact your EMC representative.
Revision History
Audience
Related
documentation
Date
Revision
Description
January 6, 2012
A01
GA release
This document is part of the EMC Ionix Network Configuration Manager
documentation set, and is intended for use by individuals who have the
responsibility of installing Network Configuration Manager.
Related documents include:
◆
EMC Ionix Network Configuration Manager Release Notes
◆
EMC Ionix Network Configuration Manager Integration Modules Installation and
Configuration Guide
◆
EMC Ionix Network Configuration Manager System Management Console Guide
◆
EMC Ionix Network Configuration Manager Applicaton Program Interface (API)
Programmer’s Guide
◆
EMC Ionix Network Configuration Manager Applicaton Program Interface (API)
Javadoc Reference Guide
◆
EMC Ionix Network Configuration Manager Device Access Scripting Language (DASL)
Specifications Guide
◆
EMC Ionix Network Configuration Manager Documentation Portfolio
◆
EMC Ionix Network Configuration Manager Non-EMC Software Read Me
◆
EMC Ionix Network Configuration Manager Online User Guide
◆
EMC Ionix Network Configuration Manager Security Configuration Guide
◆
EMC Ionix Network Configuration Manager Backup and Recovery Guide
◆
EMC Ionix Network Configuration Manager Regular Expressions (RegEx) Guide
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
5
Preface
Conventions used in
this document
◆
EMC Ionix Network Configuration Manager RSA Token Service Installation Guide
◆
EMC Ionix Network Configuration Manager Troubleshooting Guide
◆
EMC Ionix Network Configuration Manager Cluster Installation Guide
◆
EMC Ionix Network Configuration Manager Geo Diverse Installation Guide
◆
EMC Ionix Network Configuration Manager Installation Guide for Red Hat Enterprise
Linux 4 and 5
◆
EMC Ionix Network Configuration Manager Migration Guide for Red Hat Enterprise
Linux 4 and 5
◆
EMC Ionix Network Configuration Manager Installation Guide for Windows Server
2003
◆
EMC Ionix Network Configuration Manager Migration Guide for Windows Server 2003
◆
EMC Ionix Network Configuration Manager Installation Guide for Windows Server
2008 R2
◆
EMC Ionix Network Configuration Manager Migration Guide for Windows Server 2008
R2
◆
EMC Ionix Network Configuration Manager Installation Guide for Solaris 10
◆
EMC Ionix Network Configuration Manager Migration Guide for Solaris 10
EMC uses the following conventions for special notices.
Note: A note presents information that is important, but not hazard-related.
!
CAUTION
A caution contains information essential to avoid data loss or damage to the system
or equipment.
!
IMPORTANT
An important notice contains information essential to software or hardware
operation.
WARNING
A warning contains information essential to avoid a hazard that can cause severe
personal injury, death, or substantial property damage if you ignore the warning.
DANGER
A danger notice contains information essential to avoid a hazard that will cause
severe personal injury, death, or substantial property damage if you ignore the
message.
6
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
Preface
Typographical conventions
EMC uses the following type style conventions in this document:
Normal
Used in running (nonprocedural) text for:
• Names of interface elements (such as names of windows, dialog boxes, buttons,
fields, and menus)
• Names of resources, attributes, pools, Boolean expressions, buttons, DQL
statements, keywords, clauses, environment variables, functions, utilities
• URLs, pathnames, filenames, directory names, computer names, filenames, links,
groups, service keys, file systems, notifications
Bold
Used in running (nonprocedural) text for:
• Names of commands, daemons, options, programs, processes, services,
applications, utilities, kernels, notifications, system calls, man pages
Used in procedures for:
• Names of interface elements (such as names of windows, dialog boxes, buttons,
fields, and menus)
• What user specifically selects, clicks, presses, or types
Where to get help
Italic
Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis (for example a new term)
• Variables
Courier
Used for:
• System output, such as an error message or script
• URLs, complete paths, filenames, prompts, and syntax when shown outside of
running text
Courier bold
Used for:
• Specific user input (such as commands)
Courier italic
Used in procedures for:
• Variables on command line
• User input variables
<>
Angle brackets enclose parameter or variable values supplied by the user
[]
Square brackets enclose optional values
|
Vertical bar indicates alternate selections - the bar means “or”
{}
Braces indicate content that you must specify (that is, x or y or z)
...
Ellipses indicate nonessential information omitted from the example
EMC support, product, and licensing information can be obtained as follows.
Product information — For documentation, release notes, software updates, or for
information about EMC products, licensing, and service, go to the EMC Powerlink
website (registration required) at:
http://Powerlink.EMC.com
Technical support- For technical support, go to Powerlink and choose Support. On
the Support page, you will see several options, including one for making a service
request. Note that to open a service request, you must have a valid support
agreement. Please contact your EMC sales representative for details about obtaining a
valid support agreement or with questions about your account.
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
7
Preface
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and
overall quality of the user publications. Please send your opinion of this document to:
[email protected]
If you have issues, comments, or questions about specific information or procedures,
please include the title and, if available, the part number, the revision (for example,
A01), the page numbers, and any other details that will help us locate the subject you
are addressing.
8
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
in
Backup and Recovery
This document contains the following information:
◆
◆
◆
◆
◆
◆
◆
Overview ........................................................................................................................ 10
Network Configuration Manager distributed architecture ..................................... 11
Data locations ................................................................................................................ 12
Backup utilities .............................................................................................................. 14
Customer responsibilities............................................................................................. 16
Hot spare scenario......................................................................................................... 17
Backing up clustered and distributed database environments .............................. 18
Backup and Recovery
9
Backup and Recovery
Overview
The first and most important part of any good disaster recovery plan is to ensure
your critical application data is completely backed up on a regular basis, and the data
is ready for restoration in the event of data loss, data corruption, or disaster recovery.
Your installation of Network Configuration Manager comes with a set of backup and
restoration utilities pre-configured to backup the critical data in your environment.
These utilities are set up during installation on your application server to create
nightly backups consisting of all information within the Network Configuration
Manager application needed to fully recover your environment.
Information contained here introduces you to these utilities, their use in the Network
Configuration Manager distributed architecture environment, and their integration
into your overall corporate disaster recovery plan.
Note: It is not within the scope of this document to discuss the backup or disaster recovery for
the operating systems or any application software within the Network Configuration Manager
server environment(s). Your corporate disaster recovery processes are unique to your
environment, and are based on your overall IT process needs. The Network Configuration
Manager back up and restore utilities are constructed to compliment your existing sever OS
and application software restoration processes, and not attempt to replace them.
10
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
Backup and Recovery
Network Configuration Manager distributed architecture
Your implementation of Network Configuration Manager is designed to scale to the
needs of your network environment, supporting a separate Application Server and
one or more Device Servers. Depending on the size of your network, your application
server and device server may exist on a single hardware platform, or be dispersed
geographically across multiple hardware platforms.
Regardless of your environment, the data management capabilities of Network
Configuration Manager will ensure that the backup and restore utilities collect all the
data required to fully recreate your network environment in the case of data loss.
While both your Application Server and Device Servers store data about your
network environment, only the Application Server needs to be part of your data
backup strategy, saving untold hours and resources required to backup Device
Servers that may be distributed across your network and the globe.
This is accomplished by storing configuration data about your Device Servers within
the Application Server itself. In the unforeseen instance when a Device Server is lost
or corrupted, a clean Device Server can download the identity of the lost Device
Server from your Application Server, and take over all device management for the
lost Device Server.
Information about your Device Servers is stored in the Network Configuration
Manager Application Server Database, and is captured along with all other
application data using your pre-installed Network Configuration Manager backup
and restore utilities.
Network Configuration Manager distributed architecture
11
Backup and Recovery
Data locations
The Network Configuration Manager back up and restoration utilities gather all your
critical application data to be stored in a preset backup location. This frees you from
worrying about which data files within the Application Server are important to back
up, and which data files can be ignored.
Your network configuration data is stored essentially in three forms:
◆
Relational database tables
◆
XML data
◆
Flat file data
All files needed for a successful backup of your Application Server data are stored
under the [Product Home] and $JBOSS_HOME directories, and include:
$VOYENCE_HOME/data
$VOYENCE_HOME/db
$JBOSS_HOME/server/vc-server/conf/config.properties
When a backup of your system takes place, the files in these directories are copied
into a backup bundle, compressed, given a time-stamped name, and stored in a
separate directory within your application environment, [Product
Home]/data-image. By default, the data-image directory is on a filesystem local to the
Application Server.
When integrating the Network Configuration Manager backup process into your
existing corporate backup, it is imperative that this backup data be stored off of the
Application Server (on a daily basis) to prevent an Application Server hardware
failure from corrupting both the application data and the backups.
12
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
Backup and Recovery
There are several options to transfer your backup files onto a system other than the
Network Configuration Manager Application Server. The best option for your
environment depends on your corporate IT backup, and your disaster recovery
policy, but can include installing a third-party storage backup utility on the Network
Configuration Manager Application Server. Follow these steps:
1. Use the UNIX® cron utility to rcp, scp, or ftp the backup file to a different server
other than the Network Configuration Manager Application Server.
2. Create an NFS mount point for the [Product Home]/data-image directory that
resides on a remote server.
3. Copy the backup file to a removable storage device installed on the Network
Configuration Manager Application Server, such as tape or CD.
Data locations
13
Backup and Recovery
Backup utilities
The installation process for the Network Configuration Manager Application Server
automatically installs the utilities required to perform a nightly backup of your
network data, placing them in the [Product Home]/tools directory. These tools are:
◆
[Product Home]/tools/backup.pl — Creates a compressed backup bundle of all
critical data files on an active server, storing the resulting backup file in
$VOYENCE_HOME/data-image
◆
[Product Home]/tools/restore.pl — Given a name of a backup bundle in [Product
Home]/ data-image, restores the network image on the Network Configuration
Manager Application Server
◆
[Product Home]/ tools/rotate-backups.pl — Given an integer, such as 7,
maintains a list of the seven most recent backup files in the [Product
Home]/data-image directory, based of file timestamps
These utilities provide full backup and full restoration. Since the Network
Configuration Manager application is not transactional in nature, there is no
provision for incremental backups or transaction rollback. This greatly simplifies the
restoration process and management of backups in your environment.
In addition to installing the backup utilities in the [Product Home]/tools directory,
the installation process also creates two nightly tasks within the root user’s crontab
entry. (Cron is a UNIX system scheduler that automatically executes commands from
the ‘cron table’ or crontab of each system user.) On Windows, the nightly scheduled
backup tasks must be configured manually.
Refer to your application server’s Solaris/Linux/Windows Systems Administration Guide
for the proper use of the cron, crontab, and scheduled task commands on your server.
An example of the default crontab entry for root on a Network Configuration
Manager Application Server after installation of Network Configuration Manager
would appear as:
0 1 * * * [Product Home]/tools/rotate-backups.pl 8
0 2 * * * [Product Home]/tools/backup.pl -f
Deciphered into English, the first line of the crontab will cause the application server
to execute the rotate-backups command at 1 a.m. each night to maintain the most
recent eight backup files in the [Product Home]/data-image directory. If there are
more than eight backups, this command will remove all but the newest eight.
The second command will cause the system to run the backup utility each night at 2
a.m. adding the backup to the [Product Home]/data-image directory. The -f forces
the backup.pl utility to run in non-interactive mode and returns just the file name of
the backup created.
14
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
Backup and Recovery
There is nothing sacred about the time that these utilities run. You can customize
them to fit the backup needs of your environment, as well as augment these utilities
with other scheduled jobs, such as copying the backups off to a remote system. It is
only recommended that you provide a one hour delay between each backup task to
allow the previous task to complete.
The [Product Home]/tools/restore.pl utility is run manually in the event that a full
data restore of the Network Configuration Manager Application Server is required.
To run the command, you must log in to the Network Configuration Manager server
as user ‘root’ and execute the following command:
# $VOYENCE_HOME/tools/restore.pl
$VOYENCE_HOME/data-image/<filename>
<filename> indicates the name of the backup file to be restored from the [Product
Home] /data-image directory.
Backup utilities
15
Backup and Recovery
Customer responsibilities
While the Network Configuration Manager installation will automatically create a
nightly rotation and backup of your network data, this is merely the first step of your
complete data backup and disaster recovery plan.
As discussed earlier in the “Data locations” on page 12 the next step in the backup
process is to ensure the safekeeping of your backup data by sending the data to a
remote corporate storage device or a server as dictated by your IT backup policy.
Finally, your data backup, application software restoration, and server OS imaging
requirements all need to be documented in a corporate disaster recovery plan to
guarantee business continuity in the event of a major outage or failure. These tasks,
while important, are beyond the scope of this document.
16
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
Backup and Recovery
Hot spare scenario
Many customers have expressed an interest in maintaining a hot spare application
server in case of a catastrophic hardware failure in their Network Configuration
Manager production application server. Because of the distributed architecture of
Network Configuration Manager software, and hot backup capabilities of the backup
utilities, a hot spare server can be maintained in a ready standby state, able to take
over the production application role in a matter of minutes.
To set up a hot spare scenario, two identical application servers are required to be
installed with unique IP addresses on the same subnet. Both servers should have
identical versions of the Network Configuration Manager Application (or
combination) Server software installed. However, only the primary, or production
server, is configured to communicate with any distributed device servers.
Once the primary and hot spare application servers are configured and running, the
root crontab can be edited on the primary server to copy the nightly backup bundle to
the [Product Home] /data-image directory on the hot spare server using rcp or scp
commands. (Note that there are a variety of ways you can copy the backup file from
one server to the other, originating the command from either the primary or the hot
spare server. This is only one example).
Once the backup bundle is on the hot spare server, it can be restored using the
[Product Home] /tools/restore command (see the “Backup utilities” on page 14)
making the network environment on the hot spare identical to the production server.
This process can be repeated nightly through the use of cron, so that the two servers
stay in sync.
The refresh rate of the sync process is up to your requirements. You may choose to
sync the network data every four hours, or more frequently. There is a performance
penalty on the production server during a backup, and large environments should
take care when determining the frequency of backups.
Once the sync process is in place, if the primary server ever goes down, it is a simple
process of executing a ‘takeover’ script on the hot spare sever that will change its IP
address to that of the primary, and restart network services. Once the hot spare
server has successfully obtained the IP address of the primary, it will communicate
with all device servers and user clients.
Hot spare scenario
17
Backup and Recovery
Backing up clustered and distributed database environments
For customers that have very high availability (HA) requirements, the Network
Configuration Manager software supports operations in clustered and distributed
database environments. In general, the backup and recovery utilities in such
environments will work as described in this document.
However, due to the custom requirements of HA clustered and distributed
environments, it is recommended that you contact Customer Support before
implementing a backup and disaster recovery plan for your Network Configuration
Manager HA environment.
18
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
Glossary
This glossary contains terms and acronyms used within this guide.
F
FTP
File Transfer Protocol. Application layer protocol that uses TCP and Telnet services to
transfer bulk-data files between machines or hosts.
I
IP
IP address (Internet
Protocol address)
Internet Protocol. This is a network layer protocol in the Internet protocol suite and is
encapsulated in a data link layer protocol (for example, Ethernet).
A unique address for a device or logical unit on a network that uses the IP standard.
S
SCP
Secure Copy Protocol (from the SSH suite of computer applications for secure
communication).
R
RCP
Remote Copy Protocol (Cisco)
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide
19
Glossary
20
EMC Ionix Network Configuration Manager Version 4.1.1 Backup and Recovery Guide