IBM System Storage N series Logical Replication (LREP) Tool 2.0

IBM System Storage N series
Logical Replication (LREP) Tool 2.0
GC27-2092-01
NA 210-03836_A0
Copyright and trademark information
Copyright
information
Copyright ©1994 - 2010 Network Appliance, Inc. All rights reserved. Printed in the U.S.A.
Portions copyright © 2006, 2010 IBM Corporation. All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval system—without prior written permission of the copyright owner.
Software derived from copyrighted Network Appliance material is subject to the following license
and disclaimer:
THIS SOFTWARE IS PROVIDED BY NETWORK APPLIANCE “AS IS” AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL NETWORK APPLIANCE BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval system—without prior written permission of the copyright owner.
Portions of this product are derived from the Berkeley Net2 release and the 4.4-Lite-2 release, which
are copyrighted and publicly distributed by The Regents of the University of California.
Copyright © 1980–1995 The Regents of the University of California. All rights reserved.
Portions of this product are derived from NetBSD, copyright © Carnegie Mellon University.
Copyright © 1994, 1995 Carnegie Mellon University. All rights reserved. Author Chris G. Demetriou.
Permission to use, copy, modify, and distribute this software and its documentation is hereby granted,
provided that both the copyright notice and its permission notice appear in all copies of the software,
derivative works or modified versions, and any portions thereof, and that both notices appear in
supporting documentation.
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS “AS IS” CONDITION.
CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES
WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
Software derived from copyrighted material of The Regents of the University of California and
Carnegie Mellon University is subject to the following license and disclaimer:
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
ii
Copyright and trademark information
1. Redistributions of source code must retain the above copyright notices, this list of conditions,
and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notices, this list of
conditions, and the following disclaimer in the documentation and/or other materials provided
with the distribution.
3. All advertising materials mentioning features or use of this software must display this text:
This product includes software developed by the University of California, Berkeley and its
contributors.
4. Neither the name of the University nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software contains materials from third parties licensed to Network Appliance Inc. which is
sublicensed, and not sold, and title to such material is not passed to the end user. All rights reserved
by the licensors. You shall not sublicense or permit timesharing, rental, facility management or
service bureau usage of the Software.
Portions developed by the Apache Software Foundation (http://www.apache.org/). Copyright © 1999
The Apache Software Foundation.
Portions Copyright © 1995–1998, Jean-loup Gailly and Mark Adler
Portions Copyright © 2001, Sitraka Inc.
Portions Copyright © 2001, iAnywhere Solutions
Portions Copyright © 2001, i-net software GmbH
Portions Copyright © 1995 University of Southern California. All rights reserved.
Redistribution and use in source and binary forms are permitted provided that the above copyright
notice and this paragraph are duplicated in all such forms and that any documentation, advertising
materials, and other materials related to such distribution and use acknowledge that the software was
developed by the University of Southern California, Information Sciences Institute. The name of the
University may not be used to endorse or promote products derived from this software without
specific prior written permission.
Portions of this product are derived from version 2.4.11 of the libxml2 library, which is copyrighted
by the World Wide Web Consortium.
Network Appliance modified the libxml2 software on December 6, 2001, to enable it to compile
cleanly on Windows, Solaris, and Linux. The changes have been sent to the maintainers of libxml2.
The unmodified libxml2 software can be downloaded from http://www.xmlsoft.org/.
Copyright © 1994–2002 World Wide Web Consortium, (Massachusetts Institute of Technology,
Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights
Reserved. http://www.w3.org/Consortium/Legal/
Copyright and trademark information
iii
Software derived from copyrighted material of the World Wide Web Consortium is subject to the
following license and disclaimer:
Permission to use, copy, modify, and distribute this software and its documentation, with or without
modification, for any purpose and without fee or royalty is hereby granted, provided that you include
the following on ALL copies of the software and documentation or portions thereof, including
modifications, that you make:
The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a
short notice of the following form (hypertext is preferred, text is permitted) should be used within the
body of any redistributed or derivative code: “Copyright © [$date-of-software] World Wide Web
Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique
et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/”
Notice of any changes or modifications to the W3C files, including the date changes were made.
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED “AS IS,” AND COPYRIGHT
HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR
DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity
pertaining to the software without specific, written prior permission. Title to copyright in this
software and any associated documentation will at all times remain with copyright holders.
Software derived from copyrighted material of Network Appliance, Inc. is subject to the following
license and disclaimer:
Network Appliance reserves the right to change any products described herein at any time, and
without notice. Network Appliance assumes no responsibility or liability arising from the use of
products described herein, except as expressly agreed to in writing by Network Appliance. The use or
purchase of this product does not convey a license under any patent rights, trademark rights, or any
other intellectual property rights of Network Appliance.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
Trademark
information
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. A complete and current list of
other IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation
in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
iv
Copyright and trademark information
NetApp, the Network Appliance logo, the bolt design, NetApp–the Network Appliance Company,
DataFabric, Data ONTAP, FAServer, FilerView, MultiStore, NearStore, NetCache, SecureShare,
SnapLock, SnapManager, SnapMirror, SnapMover, SnapRestore, SnapValidator, SnapVault,
Spinnaker Networks, the Spinnaker Networks logo, SpinAccess, SpinCluster, SpinFS, SpinHA,
SpinMove, SpinServer, SyncMirror, VFM, and WAFL are registered trademarks of Network
Appliance, Inc. in the U.S.A. and/or other countries. gFiler, Network Appliance, SnapCopy,
Snapshot, and The Evolution of Storage are trademarks of Network Appliance, Inc. in the U.S.A.
and/or other countries and registered trademarks in some other countries. ApplianceWatch,
BareMetal, Camera-to-Viewer, ComplianceClock, ComplianceJournal, ContentDirector,
ContentFabric, EdgeFiler, FlexClone, FlexVol, FPolicy, HyperSAN, InfoFabric, LockVault, Manage
ONTAP, NOW, NOW NetApp on the Web, ONTAPI, RAID-DP, RoboCache, RoboFiler,
SecureAdmin, Serving Data by Design, SharedStorage, Simulate ONTAP, Smart SAN, SnapCache,
SnapDirector, SnapDrive, SnapFilter, SnapMigrator, SnapSuite, SohoFiler, SpinAV, SpinManager,
SpinMirror, SpinRestore, SpinShot, SpinStor, vFiler, VFM (Virtual File Manager), VPolicy, and Web
Filer are trademarks of Network Appliance, Inc. in the United States and other countries. NetApp
Availability Assurance and NetApp ProTech Expert are service marks of Network Appliance, Inc. in
the U.S.A.
All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.
Network Appliance is a licensee of the CompactFlash and CF Logo trademarks.
Network Appliance NetCache is certified RealSystem compatible.
Copyright and trademark information
v
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document
in other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe on any IBM intellectual property right
may be used instead. However, it is the user’s responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, N.Y. 10504-1785
U.S.A.
For additional information, visit the web at:
http://www.ibm.com/ibm/licensing/contact/
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES
THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some
states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
web sites. The materials at those web sites are not part of the materials for this
IBM product and use of those web sites is at your own risk.
vi
Notices
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments
may vary significantly. Some measurements may have been made on
development-level systems and there is no guarantee that these measurements
will be the same on generally available systems. Furthermore, some
measurement may have been estimated through extrapolation. Actual results may
vary. Users of this document should verify the applicable data for their specific
environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.
Notices
vii
viii
Notices
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
Chapter 1
Overview of the Logical Replication (LREP) Tool . . . . . . . . . . . . . . 1
Chapter 2
Data Backup Using the LREP Tool . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 3
Data Restore Using the LREP Tool . . . . . . . . . . . . . . . . . . . . . 15
Appendix A
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table of Contents
ix
x
Table of Contents
Preface
About this guide
This guide describes how to use the Logical Replication (LREP) tool on
Windows®, UNIX®, and Linux® platforms.
Audience
This guide is for system administrators who are familiar with operating systems
such as UNIX, Windows 2000 Server, Windows Server 2003, and storage
systems running Data ONTAP® software. It also assumes that you are familiar
with how to configure these systems and how the NFS, CIFS, and HTTP
protocols are used for file sharing or transfers. This guide does not cover basic
system or network administration topics; it emphasizes the characteristics of the
Open Systems SnapVault product and how it is used with storage systems
running Data ONTAP.
Terminology
The term “filer” is used instead of “storage system” at some places in user
interface text in this document.
Supported features
IBM® System Storage® N series storage systems are driven by NetApp® Data
ONTAP® software. Some features described in the product software
documentation are neither offered nor supported by IBM. Please contact your
local IBM representative or reseller for further details. Information about
supported features can also be found at the following Web site:
www.ibm.com/storage/support/nas/
A listing of currently available N series products and features can be found at the
following Web site:
www.ibm.com/storage/nas/
Getting information,
help, and service
Preface
If you need help, service, or technical assistance or just want more information
about IBM products, you will find a wide variety of sources available from IBM
to assist you. This section contains information about where to go for additional
information about IBM and IBM products, what to do if you experience a
problem with your IBM N series product, and whom to call for service, if it is
necessary.
xi
Before you call
Using the
documentation
Before you call, make sure that you have taken these steps to try to solve the
problem yourself:
◆
Check all cables to make sure that they are connected properly.
◆
Check the power switches to make sure that the system is turned on.
◆
Use the troubleshooting information in your system documentation and use
the diagnostic tools that come with your system.
Information about N series hardware products is available in printed documents
and a documentation CD that comes with your system. The same documentation
is available as PDF files on the IBM NAS support Web site:
www.ibm.com/storage/support/nas/
Data ONTAP software publications are available as PDF files on the IBM NAS
support Web site:
www.ibm.com/storage/support/nas/
Web sites
IBM maintains pages on the World Wide Web where you can get the latest
technical information and download device drivers and updates.
◆
For NAS product information, go to the following Web site:
www.ibm.com/storage/nas/
◆
For NAS support information, go to the following Web site:
www.ibm.com/storage/support/nas/
◆
For AutoSupport information, go to the following Web site:
www.ibm.com/storage/support/nas/
◆
For the latest version of publications, go to the following Web site:
www.ibm.com/storage/support/nas/
Accessing online
technical support
For online technical support for your IBM N series product, visit the following
Web site:
www.ibm.com/storage/support/nas/
Hardware service
and support
You can receive hardware service through IBM Integrated Technology Services.
Visit the following Web site for support telephone numbers:
www.ibm.com.planetwide/
xii
Preface
Supported servers
and operating
systems
IBM N series products attach to many servers and many operating systems. To
determine the latest supported attachments, follow the link to the Interoperability
Matrices from the following Web site:
www.ibm.com/storage/support/nas/
Firmware updates
As with all devices, it is recommended that you run the latest level of firmware,
which can be downloaded by visiting the following Web site:
www.ibm.com/storage/support/nas/
Verify that the latest level of firmware is installed on your machine before
contacting IBM for technical support. See the Data ONTAP Upgrade Guide for
your version of Data ONTAP for more information on updating firmware.
Command
conventions
You can enter storage system commands on the system console or from any client
that can obtain access to the storage system by using a Telnet session. In
examples that illustrate commands executed on a UNIX workstation, the
command syntax and output might differ from what you see, depending on the
version of UNIX that you are using.
Formatting
conventions
The following table lists different character formats used in this guide to set off
special information.
Formatting
convention
Type of information
Italic type
◆
Words or characters that require special attention.
◆
Placeholders for information you must supply.
For example, if the guide requires you to enter the
fctest adaptername command, you enter the
characters “fctest” followed by the actual name of
the adapter.
◆
Book titles in cross-references.
◆
Command and daemon names.
◆
Information displayed on the system console or
other computer monitors.
◆
The contents of files.
Monospaced font
Preface
xiii
Formatting
convention
Bold monospaced
font
Keyboard
conventions
Special messages
Type of information
Words or characters you type. What you type is
always shown in lowercase letters, unless your
program is case-sensitive and uppercase letters are
necessary for it to work properly.
This guide uses capitalization and some abbreviations to refer to the keys on the
keyboard. The keys on your keyboard might not be labeled exactly as they are in
this guide.
What is in this guide…
What it means…
hyphen (-)
Used to separate individual keys. For example,
Ctrl-D means holding down the Ctrl key while
pressing the D key.
Enter
Used to refer to the key that generates a carriage
return; the key is named Return on some
keyboards.
type
Used to mean pressing one or more keys on the
keyboard.
enter
Used to mean pressing one or more keys and then
pressing the Enter key.
This guide contains special messages that are described as follows:
Note
A note contains important information that helps you install or operate the
system efficiently.
Attention
An attention notice contains instructions that you must follow to avoid damage to
the equipment, a system crash, or loss of data.
xiv
Preface
How to send your
comments
Your feedback is important in helping us to provide the most accurate and highquality information. If you have comments or suggestions for improving this
document, send us your comments by e-mail to starpubs@us.ibm.com or use the
Readers’ Comments form at the back of this publication. Be sure to include the
following:
◆
Exact publication title
◆
Form number (for example, GC26-1234-02)
If the Readers’ Comments Form in the back of this manual is missing, you can
direct your mail to:
International Business Machines Corporation
Information Development
Dept. GZW
9000 South Rita Road
Tucson, AZ 85744–0001 U.S.A.
When you send information to IBM, you grant IBM a nonexclusive right to use
or distribute the information in any way it believes appropriate without incurring
any obligation to you.
Preface
xv
xvi
Preface
Overview of the Logical Replication (LREP) Tool
1
What the Logical
Replication (LREP)
tool does
The Logical Replication (LREP) tool enables you to create a baseline relation
between an Open Systems SnapVault primary storage system (or a Data ONTAP
primary storage system) and a secondary storage system running Data ONTAP
and vice versa using a portable device (for example, a USB external drive). You
can then ship the portable device to the secondary storage system location (for
example, a data center), transfer the data from the portable device to the
secondary storage system, and modify the relationship between the primary and
secondary storage systems.
Need for the LREP
tool
The baseline transfers can have a crippling effect on the limited bandwidth wide
area network (WAN) connections of remote or branch offices. Using the LREP
tool, no network bandwidth is used.
As shown in the following illustration, the baseline data is transferred from the
primary storage system to the SnapVault secondary storage system using LREP.
After the baseline data has been transferred over to the secondary storage system,
the relationship between the primary and secondary storage systems is
established for incremental transfers to occur directly. For more information, see
“Data Backup Using the LREP Tool” on page 9.
Update over
slow WAN
lrep_reader
lrep_writer
Removable disk
Branch office
Head office
You can also restore data from the secondary storage system to the primary
storage system. For more information, see “Data Restore Using the LREP
Tool”on page 15.
Chapter 1: Overview of the Logical Replication (LREP) Tool
1
Supported
platforms
The LREP tool is supported on the following operating systems:
◆
Windows 2000, Windows Server 2003, and Windows Storage Server 2003
on x86 and x86-64/EM64T platforms
◆
Red Hat Enterprise Linux 4.0 for x86 and x86-64/EM64T
◆
Red Hat Enterprise Linux 5.0 for x86 and x86-64/EM64T
◆
SuSE® Linux Enterprise Server 9 for x86 and x86-64/EM64T
◆
SuSE Linux Enterprise Server 10 for x86 and x86-64/EM64T
◆
Solaris™ 9 and 10 on UltraSPARC systems
◆
AIX 5L™ 5.1, 5.2, and 5.3 on IBM® PowerPC® and IBM POWER™
processor-based systems
◆
HP-UX® 11.23 and HP-UX 11.31 on PA-RISC® based systems.
For example, by using the LREP tool running on Windows 2000, you can write
data from a Data ONTAP primary storage system to a Zip drive that is locally
attached to the Windows 2000 system.
Features
The LREP tool provides the following features:
◆
Compression
The LREP tool enables the compression of data using a zlib library.
Compression of LREP data is done in the memory before the data is written
to the disk. The compression feature described here is not the same as the
compression feature available in the Qtree SnapMirror data transfer protocol.
◆
Encryption
The advanced Encryption Standard algorithm is used to encrypt and decrypt
the LREP data. The supported key sizes are 128 bits, 192 bits, and 256 bits.
The data is compressed prior to encryption.
❖
Password-based encryption—This is used to encrypt the LREP data.
The user enters a password, and a private encryption key is derived from
the password by lrep_reader. The user has to enter the same password
for decryption.
The password should be minimum of 8 characters and a maximum of 64
characters. It should include both alphanumeric and non-alphanumeric
characters.
2
❖
Password verification—During decryption, the password input is
verified by lrep_writer before decrypting the data.
❖
Data authentication—During encryption, a data digest is generated and
stored as part of the file. This data digest authenticates the data during
decryption.
Overview of the Logical Replication (LREP) Tool
Downloading the
LREP tool
The binary files for the LREP tool are packaged with the Open Systems
SnapVault software. You can access the binary files from the same location where
you uncompressed the Open Systems SnapVault software package on the primary
storage system.
Note
Before you download the LREP 2.0 software, delete any earlier versions of LREP
on the system.
Chapter 1: Overview of the Logical Replication (LREP) Tool
3
Installing the LREP
tool
The LREP tool is a stand-alone binary file, and it does not need to be installed
and can be run from the system on which the binary file is located. If Open
Systems SnapVault is installed, the following files are available to run the LREP
operation:
◆
For Windows:
<INSTALL_DIR>\bin\lrep_reader.exe
<INSTALL_DIR>\bin\lrep_writer.exe
◆
For UNIX:
$INSTALL_DIR/bin/lrep_reader
$INSTALL_DIR/bin/lrep_writer
Note
Before installing the LREP 2.0, delete any earlier versions of LREP from the
system.
Versioning
To check the version number of LREP, run the following command from
<INSTALL_DIR>\bin\:
lrep_reader -v
How the LREP tool
works
The LREP tool consists of two utilities:
◆
lrep_reader—Used at the remote office to write data from the primary
storage system to the portable device
◆
lrep_writer—Used at the location of the secondary storage system to write
data from the portable device to the secondary storage system
Note
If lrep_writer needs to be run on a machine on which the Open Systems
SnapVault software is installed, stop the Open Systems SnapVault service before
using this tool.
4
Overview of the Logical Replication (LREP) Tool
LREP command
options
LREP reader:
Following is the script for the lrep_reader utility; the following table shows the
different options that can be used with the lrep_reader utility.
lrep_reader [options] host:path
Options
Description
-c
Enables compression
Default value
Note
Encryption implies compression. The -c
option is redundant for encryption. You
will be prompted to enter a password
consisting of ASCII printable
characters.
-e
Enables encryption, that is, this option
enables compression followed by
encryption.
-k
Specifies the key size (could be 128 bits,
192 bits, or 256 bits)
128 bits
-o
Specifies the output files in the format
outfiles@max_files
lrep_reader.data:0
For example, if your original data set is
4-GB, -o E:\test@0 results in E:\test.0
E:\test.1, each file of 2 GB.
-p
Specifies the protocol for data transfer
(snapvault_start or
snapvault_start
snapvault_restore)
-l
Enables logging of headers
OFF
-f
Specifies the destination host name
lrep_reader
-q
Specifies the destination path
/vol/lrep_reader/lre
p_reader
Chapter 1: Overview of the Logical Replication (LREP) Tool
5
Options
Description
Default value
-O
Specifies the transfer from a Data
ONTAP system
-P
Specifies the pause operation between
files
-v
Specifies the version information
During backup, host:path specifies the following:
IP address or DNS name of the primary storage system:location of primary
source data
During restore, host:path specifies the following:
IP address or DNS name of SnapVault secondary storage system:location of qtree
LREP writer:
Following is the script for the lrep_writer utility; the following table shows the
different options that can be used with the lrep_writer utility.
lrep_writer [options] list of paths
Options
Description
Default value
-p
Specifies the protocol for data transfer
(snapvault_start or
snapvault_start
snapvault_restore)
-O
Specifies the transfer from a Data
ONTAP system
-P
Specifies the pause operation between
files
list of paths specifies the paths to the output files created by lrep_reader.
6
Overview of the Logical Replication (LREP) Tool
The following are the list of variables and their descriptions that can be used later
in this chapter.
◆
prim_host:dirpath is the directory path on the Open Systems SnapVault
primary server from where data is backed up to the Zip drive.
◆
prim_host:prim_vol specifies the qtree on the primary storage system to be
backed up.
◆
Zip_dirpath is the directory path on the Zip drive.
◆
sec is the name of the destination (secondary storage system) to which the
data from the primary storage system qtree is transferred. If no secondary
storage system is specified, the local host’s name is used.
◆
/vol/sec_vol/sec_qtree is the path to and the name of the qtree on the
secondary storage system.
Chapter 1: Overview of the Logical Replication (LREP) Tool
7
8
Overview of the Logical Replication (LREP) Tool
Data Backup Using the LREP Tool
Overview of data
backup using the
LREP tool
2
Assume a Windows server WIN1 is located in a remote office of an enterprise. A
volume vol1 of a SnapVault secondary storage system SEC1 located in the data
center, will be used to back up data from WIN1. The remote office has a WAN
connection of small bandwidth to the data center. So, the system administrator
uses the LREP tool for the baseline transfer. For more information, see
“Overview of the Logical Replication (LREP) Tool” on page 1.
Using lrep_reader, the baseline transfer is done from WIN1 to a Zip drive
(drive letter E) connected to a Windows client CL1. The Zip drive is shipped to
the data center where a second Windows client CL2, uses lrep_writer to write
data from the Zip drive to the secondary storage system SEC1.
Backing up data
from open systems
to a secondary
storage system
At the remote office: Complete the following steps.
Step
1
Action
Enter the following command in the directory of the system (CL1) on
which lrep_reader is installed:
lrep_reader.exe [-c] [-e] [-p snapvault_start] -f sec -q
/vol/sec_vol/sec_qtree -o Zip_dirpath@0 [-l reader.log]
prim_host:dirpath
-l reader.log is the location where the LREP headers are saved.
Note
When the -c option is used, the output files generated at Zip_dirpath
are compressed. When the -e option is used, you are prompted to
enter and reconfirm the encryption password.
Example:
C:\>lrep_reader.exe [-p snapvault_start] -f SEC1 -q
/vol/vol1/backup -o E:\test@0 [-l reader.log]
WIN1:D:\dataset
Transfer started.
Use 'snapvault status' on source to monitor progress.
Transfer done.
Verify by using 'snapvault status' on filer.
Chapter 2: Data Backup Using the LREP Tool
9
At the data center: After the Zip drive arrives at the data center, connect it to
the second Windows client (CL2).
Ensure that the Open Systems SnapVault services are stopped before lrep_writer
is installed.
Step
1
Action
Enter the following command in the directory of the system (CL2) on
which lrep_writer is installed:
lrep_writer.exe Zip_dirpath
Note
If the files at Zip_dirpath are compressed, lrep_writer will internally
uncompress the files. If the files are encrypted, lrep_writer prompts
you to enter the decryption password and internally decrypt the files.
Example:
C:\>lrep_writer.exe E:\test
lrep_writer: Will read 1 files from prefix e:\test
Waiting for connection.
Use snapvault start command on secondary to create a
relationship
E:\test is the source LREP data. If the source LREP data spans
multiple portable drives (for example, drive E contains the first 8-GB
of data and drive F contains the next 4-GB of data) then enter the
following command:
C:\>lrep_writer.exe E:\test F:\test
10
Data Backup Using the LREP Tool
Step
2
Action
Now, to start the data transfer from the secondary storage system
(SEC1), enter the following command in the console of the
secondary storage system:
snapvault start -S CL2:Zip_dirpath /vol/sec_vol/sec_qtree
Example:
SEC1> snapvault start -S CL2:E:\test /vol/vol1/backup
Snapvault configuration for the qtree has been set.
Transfer started.
Monitor progress with 'snapvault status' or the
snapmirror log.
3
Enter the following command to modify the relationship on the
secondary storage system (SEC1):
snapvault modify -S prim_host:dirpath
/vol/sec_vol/sec_qtree
Example:
SEC1> snapvault modify -S WIN1:D:\dataset
/vol/vol1/backup
Configuration for qtree /vol/vol1/backup is:
/vol/vol1/backup source=WIN1:D:\dataset kbs=unlimited
tries=2 back_up_open_files=on,ignore_atime=off
4
To ensure that a relationship between the primary storage system
(WIN1) and SnapVault secondary storage system (SEC1) is
established, force an incremental backup:
snapvault update /vol/sec_vol/sec_qtree
Example:
SEC1> snapvault update /vol/vol1/backup
Transfer started.
Monitor progress with 'snapvault status' or the
snapmirror log.
Chapter 2: Data Backup Using the LREP Tool
11
Step
5
Action
Run the following command on the secondary storage system to
check the status:
snapvault status
Example:
SEC1> snapvault status
Snapvault secondary is ON
Source Destination State
Lag
Status
WIN1:D:\dataset SEC1:/vol/vol1/backup Snapvaulted
00:00:35
Idle
Backing up data
from a SnapVault
primary storage
system to a
secondary storage
system
At the remote office: Here, the source is a Data ONTAP primary storage
system. Complete the following steps.
Step
1
Action
Run the following command in the directory of the system (CL1) on
which lrep_reader is installed:
lrep_reader.exe -O [-c] [-e] [-p snapvault_start] -f sec
-q /vol/sec_vol/sec_qtree -o Zip_dirpath@0 [-l
reader.log] prim_host:prim_vol
Note
When the -c option is used, the output files generated at Zip_dirpath
are compressed. When the -e option is used, you are prompted to
enter and reconfirm the encryption password.
Example:
C:\>lrep_reader.exe -O [-p snapvault_start] -f SEC1 -q
/vol/vol1/backup -o E:\test@0 [-l reader.log]
FAS_PRI:/vol/data/Logic
Transfer started.
Use 'snapvault status' on source to monitor progress.
Transfer done.
Verify by using 'snapvault status' on filer.
12
Data Backup Using the LREP Tool
At the data center: After the Zip drive arrives at the data center, connect it to
the second Windows client, CL2.
Step
1
Action
Enter the following command in the directory of the system (CL2) on
which lrep_writer is installed:
lrep_writer.exe -O Zip_dirpath
Note
If the files at Zip_dirpath are compressed, lrep_writer will internally
uncompress the files. If the files are encrypted, lrep_writer will
prompt you to enter the decryption password and internally decrypt
the files.
Example:
C:\>lrep_writer.exe -O E:\test
lrep_writer: Will read 1 files from prefix e:\test
Waiting for connection.
Use snapvault start command on secondary to create a
relationship
E:\test is the source LREP data. If the source LREP data spans
multiple portable drives (for example, drive E contains the first 8-GB
of data and drive F contains the next 4-GB of data) then enter the
following command:
C:\>lrep_writer.exe -O E:\test F:\test
2
To start the data transfer from the secondary storage system (SEC1),
enter the following command at the console of the secondary storage
system:
snapvault start -S CL2:Zip_dirpath /vol/sec_vol/sec_qtree
Example:
SEC1> snapvault start -S CL2:E:\test /vol/vol1/backup
Snapvault configuration for the qtree has been set.
Transfer started.
Monitor progress with 'snapvault status' or the
snapmirror log.
Chapter 2: Data Backup Using the LREP Tool
13
Step
3
Action
Modify the relationship on the secondary storage system (SEC1) by
entering the following command:
snapvault modify -S prim_host:prim_vol
/vol/sec_vol/sec_qtree
Example:
SEC1> snapvault modify -S FAS_PRI:/vol/data/Logic
/vol/vol1/backup
Configuration for qtree /vol/vol1/backup is:
/vol/vol1/backup source=FAS_PRI:/vol/data/Logic
kbs=unlimited tries=2
back_up_open_files=on,ignore_atime=off
4
To ensure that a relationship between WIN1 and the secondary
storage system (SEC1) is established, force an incremental backup:
snapvault update /vol/sec_vol/sec_qtree
Example:
SEC1> snapvault update /vol/vol1/backup
Transfer started.
Monitor progress with 'snapvault status' or the
snapmirror log.
5
Run the following command on the secondary storage system to
check the status:
snapvault status
Example:
SEC1> snapvault status
Snapvault secondary is ON
Source Destination State
Lag
Status
FAS_PRI:/vol/data/Logic SEC1:/vol/vol1/backup Snapvaulted
00:00:35
Idle
14
Data Backup Using the LREP Tool
Data Restore Using the LREP Tool
Restoring data with
the help of the
LREP tool
3
You can restore data from a secondary storage system to the primary storage
system using the LREP tool, without having to transfer data over the network.
At the data center, using the lrep_reader, the baseline transfer is done from
SEC1 to a Zip drive (drive letter E) connected to a Windows client, CL1. The Zip
drive is shipped to the remote office where a second Windows client, CL2, uses
the lrep_writer to write data from the Zip drive to WIN1.
Complete the following steps to restore and resync a relationship after restoring
the data from the secondary storage system (SEC1) to the Open Systems
SnapVault primary server (WIN1) using the LREP tool.
At the data center: Let us assume that the LREP tool is installed on a
Windows client CL1, and you have to restore the data to the Open Systems
SnapVault primary server WIN1 at the remote office. Complete the following
steps.
Step
Action
1
Run the following command in the directory of the client (CL1) on
which lrep_reader is installed:
lrep_reader [-c] [-e] -p snapvault_restore -o
Zip_dirpath@0 -f WIN1 -q C:\data [-l reader.log]
sec:/vol/sec_vol/sec_qtree
Note
When the -c option is used, the output files generated at
Zip_dirpath are compressed. When the -e option is used, you will
be prompted to enter and reconfirm the encryption password.
Example:
C:\> lrep_reader -p snapvault_restore -o E:\rest@0 -f
WIN1 -q C:\data [-l reader.log] SEC1:/vol/data/Logic
Transfer started.
Use 'snapvault status' on source to monitor progress.
Transfer done.
Verify by using 'snapvault status' on filer.
Chapter 3: Data Restore Using the LREP Tool
15
At the remote office: Let us assume that the LREP tool is installed on a
Windows client (CL2).
Step
Action
1
Connect the Zip drive to the system. Enter the following command
in the directory (CL2) on which lrep_writer is installed:
lrep_writer -p snapvault_restore Zip_dirpath
Note
If the files at Zip_dirpath are compressed, lrep_writer will
internally uncompress the files. If the files are encrypted,
lrep_writer will prompt you to enter the decryption password and
internally decrypt the files.
Example:
C:\> lrep_writer -p snapvault_restore E:\rest
lrep_writer: Will read 1 files from prefix E:\rest
Waiting for connection.
Use snapvault start command on secondary to create a
relationship
2
Now, to start the data transfer, run the following command on the
Open Systems SnapVault primary server (WIN1):
snapvault restore -S CL2:Zip_dirpath prim_dirpath
Note
Enable the restart/resync on restore check box in the Configurator
GUI, before you start the data transfer.
Example:
C:\> snapvault restore -S CL2:E:\rest C:\data
16
Data Restore Using the LREP Tool
Step
Action
3
Run the following command to check the status:
snapvault status
Example:
C:\> snapvault status
Snapvault primary is ON
Source Destination State
Lag
Status
SEC1:/vol/data/Logic CL2:C:\data Broken-off - Idle
4
To resync the relationship on the secondary storage system, run the
following command on the secondary storage system (SEC1):
snapvault start -r -S prim_host:dirpath
/vol/sec_vol/sec_qtree
Example:
SEC1> snapvault start -r -S WIN1:C:\data
/vol/data/Logic
The resync base snapshot will be: snapshot name
Resync may alter the data in this qtree.
Are you sure you want to resync the qtree? y
Wed Mar 21 15:33:33 GMT
[replication.dst.resync.success:notice]: SnapVault
resync of /vol/data/Logic to WIN1:c:\data was
successful.
Snapvault configuration for the qtree has been set.
Transfer started.
Monitor progress with 'snapvault status' or the
snapmirror log.
Restoring data from
a secondary
storage system to
the primary storage
system
Complete the following steps to resync a relationship after restoring the data
from the secondary storage system (SEC1) to the primary storage system (PRI1)
using the LREP tool.
At the data center: Let us assume that the LREP tool is installed on the
Windows client CL1, and you have to restore the data to the remote office PRI1.
Chapter 3: Data Restore Using the LREP Tool
17
Step
Action
1
Run the following command on the directory of the client (CL1) on
which lrep_reader is installed:
lrep_reader -O [-c] [-e] -p snapvault_restore -o
Zip_dirpath@0 -f prim_host -q prim_vol [-l reader.log]
sec:/vol/sec_vol/sec_qtree
Note
When the -c option is used, the output files generated at Zip_dirpath
are compressed. When the -e option is used, you are prompted to
enter and reconfirm the encryption password.
Example:
C:\> lrep_reader -O -p snapvault_restore -o E:\rest@0 -f
PRI1 -q /vol/vol1/backup [-l reader.log]
SEC1:/vol/data/Logic
Transfer started.
Use 'snapvault status' on source to monitor progress.
Transfer done.
Verify by using 'snapvault status' on filer.
18
Data Restore Using the LREP Tool
At the remote office: Let us assume that the LREP tool is installed on the
Windows client CL2 and the Zip drive is connected to CL2. Complete the
following step.
Step
Action
1
Enter the following command in the directory of the system (CL2)
on which lrep_writer is installed:
lrep_writer -O -p snapvault_restore Zip_dirpath
Note
If the files at Zip_dirpath are compressed, lrep_writer will internally
uncompress the files. If the files are encrypted, lrep_writer will
prompt you to enter the decryption password and internally decrypt
the files.
Example:
C:\> lrep_writer -O -p snapvault_restore E:\rest
lrep_writer: Will read 1 files from prefix e:\rest
Waiting for connection.
Use snapvault start command on secondary to create a
relationship
2
Now, run the following command on the primary storage system
(PRI1) to start the data transfer:
snapvault restore -S CL2:Zip_dirpath prim_vol
Example:
PRI1> snapvault restore -S CL2:E:\rest /vol/vol1/backup
Chapter 3: Data Restore Using the LREP Tool
19
Step
Action
3
To resync the relationship on the secondary storage system, run the
following command on the secondary storage system (SEC1):
snapvault start -r -S prim_host:prim_vol
/vol/sec_vol/sec_qtree
Example:
SEC1> snapvault start -r -S PRI1:/vol/vol1/backup
/vol/data/Logic
The resync base snapshot will be: snapshot name
Resync may alter the data in this qtree.
Are you sure you want to resync the qtree? y
Wed Mar 21 15:33:33 GMT
[replication.dst.resync.success:notice]: SnapVault
resync of /vol/data/Logic to PRI1:/vol/vol1/backup was
successful.
Snapvault configuration for the qtree has been set.
Transfer started.
Monitor progress with 'snapvault status' or the
snapmirror log.
20
Data Restore Using the LREP Tool
A
Error Messages
The following table lists the error messages you can encounter while using the
LREP tool, their causes, and actions you can take to remedy these errors.
Error message
Cause
Action to take
Error in bind: No such
file or directory
The LREP writer fails
with this error message.
This indicates that
Open Systems
SnapVault is holding on
to port 10566, which
LREP is also trying to
use.
Stop Open Systems
SnapVault agent or try
another machine that is
not running Open
Systems SnapVault.
Could not connect to
host host_name: No
error
lrep_reader tries to
communicate to Open
Systems SnapVault,
residing on the host,
(when Open Systems
SnapVault is not
running) and fails with
this error message.
Start the Open Systems
SnapVault service.
This indicates that
when Open Systems
SnapVault service is not
running on the host,
which is mentioned in
the lrep_reader
command, this error
occurs.
Appendix A: Error Messages
21
22
Error Messages
Index
C
L
command options 5
commands
lrep_reader 4
lrep_writer 4, 10, 13
LREP tool
downloading 3
installation 4
versioning 4
lrep_reader utility 4
lrep_writer utility 4, 10, 13
D
data authentication 2
F
features
compression 2
encryption 2
Index
P
password verification 2
password-based encryption 2
portable device 1
23
NA 210-03836_A0, Printed in USA
GC27-2092-01
Download PDF
Similar pages