TimeFinder FS NearCopy and FarCopy

7/21/2019 TimeFinder FS NearCopy and FarCopy

1/116

EMC VNXSeries

Release 7.1

Using TimeFinder/FS, NearCopy, and FarCopy on VNX

P/N 300-013-504 Rev 01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000

www.EMC.com


2/116

Copyright 1998 - 2012 EMC Corporation. All rights reserved.

Published July 2012

EMC believes the information in this publication is accurate as of its publication date.Theinformation is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATIONMAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TOTHE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date regulatory document for your product line, go to the TechnicalDocumentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks onEMC.com.

All other trademarks used herein are the property of their respective owners.

Corporate Headquarters: Hopkinton, MA 01748-9103

2 Using TimeFinder/FS, NearCopy, and FarCopy on VNX 7.1


3/116

Contents

Preface.....................................................................................................7

Chapter 1: Introduction...........................................................................9

System requirements..................................................................................11

Restrictions..................................................................................................12

User interface choices.................................................................................12

Related information.....................................................................................12

Chapter 2: Concepts.............................................................................15

TimeFinder..................................................................................................16

TimeFinder/FS.............................................................................................16

TimeFinder/FS NearCopy..................................................................17TimeFinder/FS FarCopy.....................................................................18

Summary of TimeFinder/FS usage.............................................................20

Planning considerations..............................................................................20

TimeFinder/FS, NearCopy, FarCopy and VNX FileMover............................21

Comparison of VNX high-availability and replication products....................21

TimeFinder/FS, NearCopy, and FarCopy tasks overview............................24

Chapter 3: Configuring.........................................................................27

Create a TimeFinder/FS snapshot..............................................................28

Create a snapshot..............................................................................28Make the snapshot available..............................................................30

Update a TimeFinder/FS snapshot..............................................................33

Verify that a snapshot is in mirror mode.............................................33

Unmount the snapshot.......................................................................34

Mirror on and off the TimeFinder/FS snapshot...................................35

Using TimeFinder/FS, NearCopy, and FarCopy on VNX 7.1 3


4/116

Refresh the snapshot (Optional)........................................................39

Restore the PFS..........................................................................................41

Verify file system information before the restore................................41

Restore the file system.......................................................................42Create a NearCopy snapshot......................................................................43

Identify the local and remote VNX systems........................................44

Import the PFS...................................................................................46

Create a NearCopy snapshot of the imported file system..................50

Refresh a NearCopy snapshot of the imported file system................51

Make the NearCopy snapshot available.............................................53

Restore the local PFS from a NearCopy snapshot.....................................56

Verify that the NearCopy snapshot is not in use.................................56

Restore imported FS (R2) from the NearCopy snapshot ..................57

Verify that the PFS is not in use at the source...................................60Restore the PFS from the imported file system (R2).........................61

Mount the PFS on the Data Mover.....................................................63

Create a FarCopy snapshot........................................................................65

Preinitialize the configuration.............................................................65

Create a local snapshot of the PFS....................................................68

Refresh the R2 BCV...........................................................................70

Import the snapshot of the PFS.........................................................72

Create a FarCopy snapshot of the imported file system....................75

Make the FarCopy snapshot copy available.......................................76

Refresh the FarCopy snapshot....................................................................78

Refresh the local snapshot (R1 BCV)................................................78

Refresh the FarCopy snapshot...........................................................82

Restore the PFS from the FarCopy snapshot.............................................84

Unexport and unmount the FarCopy snapshot...................................84

Restore the R2 BCV from the FarCopy snapshot..............................85

Restore the R1 from the R2 BCV.......................................................86

Restore the PFS from the FarCopy snapshot....................................87

Extend a PFS with a FarCopy snapshot......................................................89

Chapter 4: Managing............................................................................93

List information for a specific TimeFinder/FS snapshot...............................94

List information on all file systems...............................................................95

Delete TimeFinder/FS snapshots................................................................96

Chapter 5: Troubleshooting..................................................................97


Contents


5/116

EMC E-Lab Interoperability Navigator.........................................................98

Error messages...........................................................................................98

Known problems and limitations..................................................................99

Example for restoration failure............................................................99Resolution for restoration failure.......................................................100

EMC Training and Professional Services..................................................102

Appendix A: Portfolio of High-Availability Options...........................105

Glossary................................................................................................111

Index.....................................................................................................113


Contents


6/116


Contents


7/116

Preface



8/116


Preface


9/116

1

Introduction

EMC TimeFinder/FS is an EMC VNX-specific implementation of theTimeFinder feature for creating snapshots, which are complete,

independently addressable, point-in-time copies of VNX Production FileSystem (PFS) volumes.TimeFinder/FS snapshots are created on dedicatedlocal or remote EMC Symmetrix business continuance volumes (BCVs)in the background mode.

VNX supports three TimeFinder implementations:

TimeFinder/FS For local source volumes.TimeFinder/FS is the baseproduct.

TimeFinder/FS NearCopy For remote source volumes set up withEMC Symmetrix Remote Data Facility/Synchronous (SRDF/S), acampus-environment disaster recovery configuration.

TimeFinder/FS FarCopy For remote source volumes set up with

SRDF adaptive copy disk-pending mode used in extended-distancereplication.

Chapter 2provides more details.

This document is part of the VNX documentation set and is intended forsystem administrators familiar with installing and managing high-availabilitystorage configurations, and responsible for:

Creating and using TimeFinder/FS snapshots of a PFS on local volumesto maintain business continuance.

Creating and using remote mirror copies of a PFS either to maintainbusiness continuance or to provide disaster recovery protection.

Your local EMC Customer Support Representative performs the Symmetrixstorage system administrative tasks, such as installation and configurationof the BCVs, and is available to help you ensure the proper functionalityas needed.

Topics included are:



10/116

System requirements on page 11 Restrictions on page 12 User interface choices on page 12

Related information on page 12


Introduction


11/116

System requirements

Table 1 on page 11describes the EMC

VNX

software, hardware, network, and storageconfigurations.

Table 1. System requirements

EMC Symmetrix

version 4/4.8 or later with 5265 microcode.

VNX version 7.0

Software

Systems with 507 or later model Data Movers with 512 MB RAM.

Symmetrix storage system. For EMC TimeFinder/FS NearCopy and FarCopy configurations

employing EMC SRDF/S for NearCopy and SRDF adaptive copy disk-pending mode for FarCopy,

each Symmetrix system requires a communications device called a remote adapter (RA) to provide

a connection with the remotely located Symmetrix system.The connection can be over wide-area

channels by using Fibre Channel (FC), Enterprise Systems Connection (ESCON), Dense Wave-

length Division Mult iplexing (DWDM), and IP.

Hardware

For TimeFinder/FS, no specific network requirements.

For TimeFinder/FS NearCopy and FarCopy configurations employing SRDF/S for NearCopy and

SRDF adaptive copy disk-pending mode for FarCopy, the Control Stations of the source and

destination (target) VNX systems must communicate across the IP data network that is required

for multihop configurations or the dedicated SRDF channel (link) in the appropriate SRDF mode.

Network

Storage For TimeFinder/FS: A local Symmetrix system and VNX.

For TimeFinder/FS NearCopy: Using SRDF/S with VNX for Disaster Recoverydescribes how touse SRDF/S.

For TimeFinder/FS FarCopy: The Solutions Enabler Symmetrix SRDF family documentation on

the EMC Online Supportwebsite provides the comprehensive Symmetrix SRDF information. If

necessary, contact your local EMC Customer Support Representative for help with SRDF adaptive

copy disk-pending mode replication setup and management.

To create a snapshot by using automatic volume selection with TimeFinder/FS, a Symmetrix

system attached to a VNX must be configured with STD volumes and BCVs in a one-to-one, equal-

sized relationship.Your local EMC Customer Support Representative typically creates the BCVs

as part of the initial VNX installation process.The BCVs must have the capacity to accommodate

the largest potential file system. If a file system is built on STD volumes of different sizes, then

creating a snapshot becomes a manual process that requires assistance from your local EMC

Customer Support Representative.

TimeFinder/FS requires that the PFS of which you create snapshots is built on local STD Symmetrix

volumes and not slice volumes.

System requirements 11

Introduction
http://support.emc.com/http://support.emc.com/


12/116

Restrictions

For TimeFinder/FS: VNX permits only one TimeFinder/FS local snapshot of a PFS to be in a mirrored-on

state. Attempts to mirror on more than one local snapshot of a PFS causes a failure andresults in an error message, but the active mirror is not affected.

The TimeFinder/FS base product is the only TimeFinder/FS implementation that supportsAutomatic File System Extension.

For TimeFinder/FS NearCopy and FarCopy:

Automatic File System Extension cannot be used for any file system that is part of anSRDF or EMC MirrorView/S configuration (file systems on Data Movers configuredwith an RDF standby, which includes TimeFinder/FS NearCopy and FarCopy

implementations). You cannot use the nas_fs command with the auto_extend option forfile systems associated with SRDF or MirrorView/S. Doing so generates the errormessage: Error 4121: operation not supported for file systems of type SRDF."

General restrictions:

Never use Symmetrix command line interface (SYMCLI) action commands to performSRDF and TimeFinder/FS tasks in a VNX environment. The VNX commands related toTimeFinder/FS run all the relevant SYMCLI commands transparently to create snapshotson the local and remote BCVs. You run these commands at the VNX for file commandline interface (CLI).

After a TimeFinder/FS command is run, processing continues on the Symmetrix systemand cannot be interrupted from the Control Station.

TimeFinder/FS does not support solid state disk (SSD) drives. If you attempt to configurean SSD drive with TimeFinder, VNX health check operations reject the device as anunsupported storage.

User interface choices

This document describes how to configure TimeFinder/FS, NearCopy, and FarCopy by usingthe CLI. You cannot use other VNX management applications to configure TimeFinder/FS,NearCopy, and FarCopy.

Related information

For specific information related to the features and functionality described in this document:

EMC VNX Command Line Interface Reference for File

Celerra Network Server Error Messages Guide


Introduction


13/116

Problem Resolution Roadmap for VNX

Online VNX for file man pages

Using VNX FileMover

Using SRDF/S with VNX for Disaster Recovery

Using SRDF/Star with VNX

Other EMC publications related to Symmetrix SRDF include:

Symmetrix Remote Data Facility (SRDF) Product Guide

Solutions Enabler Symmetrix SRDF Family CLI Product Guide

EMC VNX documentation on the EMC Online Support website

The complete set of EMC VNX series customer publications is available on the EMC

Online Support website. To search for technical documentation, go tohttp://Support.EMC.com. After logging in to the website, click the VNX Support by Productpage to locate information for the specific feature required.

VNX wizards

Unisphere software provides wizards for performing setup and configuration tasks.TheUnisphere online help provides more details on the wizards.

Related information 13

Introduction


14/116


Introduction


15/116

2

Concepts

TimeFinder/FS, NearCopy, and FarCopy are implementations of the EMCTimeFinder software feature specific to VNX.

Topics included are:

TimeFinder on page 16 TimeFinder/FS on page 16 Summary of TimeFinder/FS usage on page 20 Planning considerations on page 20 TimeFinder/FS, NearCopy, FarCopy and VNX FileMover on page 21 Comparison of VNX high-availability and replication products on page

21 TimeFinder/FS, NearCopy, and FarCopy tasks overview on page 24



16/116

TimeFinder

TimeFinder is a Symmetrix storage system feature that allows you to create complete,independently addressable mirror images, called snapshots, of active production volumes.The snapshots are created in background mode on BCVs for mainframe, UNIX, VNX, andMicrosoft Windows NT systems.

With TimeFinder, backup operations are performed against the BCVs, leaving the productionvolume fully available for regular business needs. TimeFinder commands are run againstthe entire volume.

TimeFinder/FS

TimeFinder/FS is an implementation of the TimeFinder technology specifically tailored forVNX. TimeFinder/FS enables you to create a point-in-time copy, called a snapshot, of aVNX file system onto dedicated Symmetrix BCVs.To create a TimeFinder/FS snapshot, thesource volumes of the VNX file system are usually built on local volumes, including R1volumes.

Figure 1 on page 16shows TimeFinder/FS operation in a local VNX environment.

VNX 1(Local site)

Symmetrix source VNX-000037

Clients

BCV

(PFS)

R1

Mirror ofTimeFinder/FS

snapshot

TimeFinder/FSsnapshotof PFS

Network

Figure 1. TimeFinder/FS

The copy of a file system created by using TimeFinder/FS reflects the state of the fi le systemat the time the copy was completed. You can use the copy as a:


Concepts


17/116

Backup to recover an old version of a file, directory, or complete file system.

Replica of live data for application testing. You can edit the replicated copy.

Continuously updated mirror of an active file system. At any time, you can mirror on an

existing snapshot to resynchronize it and maintain its synchronization with the PFS, sothat an exact mirror of the PFS is available.

The process of mirroring on an existing snapshot is less time-consuming than creatinga new snapshot. When a new point-in-time copy of the PFS is required, you can mirroroff a snapshot that is in mirror mode, and the updated snapshot is available immediatelyfor mounting and exporting.

Source for decision support.

After you create a fi le system copy, the copy is accessible over the network, and networkusers can access it independently of the original file system on the STD volume.The copymaintains the same permissions and inode numbers as the original files, thereby maintaining

the integrity and authorizations of the file system.

TimeFinder/FS includes two distinct functions:TimeFinder/FS NearCopy and TimeFinder/FSFarCopy.

TimeFinder/FS NearCopy

TimeFinder/FS NearCopy allows you to create a NearCopy snapshot of an SRDFimplementation in synchronous mode (SRDF/S), which offers disaster recovery in a campusconfiguration. NearCopy is a BCV snapshot that enables the source volumes to be R2volumes operating in SRDF/S mode.

After an active/passive or active/active SRDF/S campus configuration is established andthen initialized for disaster recovery in the VNX environment, you can use TimeFinder/FSin two ways:

To create a snapshot of the local PFS at the local site with the local R1 as the sourcevolume.

To create a snapshot of the PFS by using TimeFinder/FS NearCopy with R2 as thesource volume.

Both types of snapshots are readily available and can be exported by Data Movers at eachsite. Using SRDF/S with VNX for Disaster Recoverydescribes how to establish SRDF/Swith VNX systems.

TimeFinder/FS 17

Concepts


18/116

Figure 2 on page 18shows TimeFinder/FS NearCopy operation in SRDF/S mode in acampus environment.

VNX 1(Local site)

Symmetrix source

(Mirroredfile

system)

VNX 2(Remote site)

Symmetrix target

VNX-000035

(Remotecopy)

BCV

Client Client

Network

(Local copy)

BCV

(PFS)

R1 SRDF/S

Disasterrecovery

Optionallocal

snapshot

OptionalNearCopysnapshot

R2

Figure 2. TimeFinder/FS NearCopy

TimeFinder/FS FarCopy

TimeFinder/FS FarCopy is similar to NearCopy, except it is used for extended distancesand relies on SRDF adaptive copy mode.With an established SRDF configuration in SRDFadaptive copy disk-pending mode, you can use TimeFinder/FS FarCopy to create a FarCopysnapshot. FarCopy produces a BCV snapshot that enables the source volumes to be R2volumes operating in SRDF adaptive copy disk-pending mode.

FarCopy supports file system replication in an extended-distance SRDF environment, asshown in Figure 3 on page 19. The PFS and FarCopy snapshot are built on local volumes.

Only the BCVs are copied remotely or replicated by using SRDF in adaptive copy disk-pendingmode.The Solutions Enabler Symmetrix SRDF documentation on the EMC Online Supportwebsite provides information about adaptive copy disk-pending mode.


Concepts


19/116

Note: TimeFinder/FS FarCopy is not considered a disaster recovery offering.

VNX 1(Local site)

Symmetrix source

VNX 2(Remote site)

Symmetrix target

VNX-000036

ImportedBCV

snapshot

R2 BCV

San Francisco Atlanta

Client Client

Network

(Localsnapshot)

R1 BCVSRDF

adaptivecopy

(PFS)

Local STD

FarCopysnapshot

Figure 3. TimeFinder/FS FarCopy

TimeFinder/FS 19

Concepts


20/116

Summary of TimeFinder/FS usage

Table 2 on page 20shows when to use TimeFinder/FS and where to find additionalinformation.

Table 2. TimeFinder/FS features and usage

TimeFinder/FS FarCopyTimeFinder/FS NearCopyTimeFinder/FS

Use when the source volumes are R2operating in SRDF adaptive copy disk-pending mode.

Use when the source volumes are R2operating in SRDF/S or campus DRmodes.

Use when the source volumes are localor R1 volumes.

The Solutions Enabler Symmetrix docu-mentation for SRDF provides more in-formation, and is available on the EMCOnline Support website. If necessary,contact your local EMC Customer Sup-port Representative.

Using SRDF/S with VNX for Disaster

Recoverydescribes SRDF/S with VNX.If necessary, contact your local EMCCustomer Support Representative.

For more information, contact your localEMC sales organization. If necessary,contact your local EMC Customer Sup-port Representative.

Planning considerations

If you plan to create a TimeFinder/FS local, NearCopy, or FarCopy snapshot of a PFS,do not use slice volumes created with the nas_slice command when creating the PFS.Instead, use the full disk presented to the VNX system because TimeFinder copies andrestores Symmetrix volumes in their entirety and does not recognize sliced partitionscreated by the host VNX. Managing Volumes and File Systems for VNX Manuallyprovidesmore details on creating a file system.

Each snapshot you plan to create of a PFS requires a BCV that is the same size as thePFS. If these BCVs are unavailable, the snapshot attempt fails. Therefore, as you createeach PFS on a system, decide the total number of TimeFinder/FS snapshots needed toserve future administrative tasks. Create an equal number of BCVs and ensure that theyare the same size as the PFS. Note that if you later extend the PFS, thereby making itbigger than the BCVs you have created for snapshots, the system will fail to automaticallyselect a BCV in the snapshot creation process.This is because it can no longer find aBVC of equal size. You must then specify a volume for the snapshot manually. Contactyour local EMC Customer Support Representative for assistance in the manualvolume-selection process.

If you plan to perform a Unicode conversion, do not perform a TimeFinder/FS restore

operation while the conversion is running. If a TimeFinder/FS backup is mirrored to a PFS when the PFS is extended, then the

TimeFinder/FS backup is automatically extended.The TimeFinder/FS backup and PFSalso undergo an automatic incremental-establish instead of a full-establish. If aTimeFinder/FS backup is not mirrored to a PFS when the PFS is extended, it will not be


Concepts


21/116

recognized as a TimeFinder/FS backup of the PFS. If you want a copy of the extendedPFS, then you must create a new TimeFinder/FS backup through a full-establish.

TimeFinder/FS, NearCopy, FarCopy and VNX FileMover

VNX FileMover supports TimeFinder/FS, NearCopy, and FarCopy.Using EMC VNX FileMoverprovides details on VNX FileMover.

Comparison of VNX high-availability and replication products

Table 3 on page 21lists and compares the different VNX product options for disasterrecovery, high availability, and file system replication or copying.Your local EMC salesorganization can provide information about other configuration options.

Note: In general, file systems should not span multiple storage systems.

Table 3. Comparison of VNX high-availability and replication products

RestrictionsDescriptionStorage platformProduct

Cannot be used in the sameVNX for file configuration asSRDF. Cannot be used withSymmetrix-based products,such as TimeFinder/FS.Cannot be used with the Au-tomatic File System Exten-

sion feature.Performs LUN or volumecloning, not file systemcloning. Remote volumes areonly accessible after afailover.

Using attached VNX for fileand VNX for block storagesystem pairs, performs syn-chronized, remote mirroringto provide full disaster recov-ery without data loss at alimited distance.

Using MirrorView/Syn-chronous with VNX for file for

Disaster Recoveryprovidesmore details about Mir-rorView/S.

VNX for block only, EMC CX

series (700/600/500/400)MirrorView/S

Cannot be used in the sameVNX for file configuration asMirrorView/S. Cannot beused with the Automatic FileSystem Extension feature.

Performs volume cloning, not

file system cloning. Remotevolumes are only accessibleafter a failover.

Using attached VNX for fileand Symmetrix pairs, per-forms synchronized, remotereplication to provide full dis-aster recovery without dataloss at a limited distance.Using SRDF/S with VNX for

Disaster Recoveryprovidesmore details about SRDF/S.

Symmetrix only (3xxx, 5xxx, 8xxx,or DMX series)

SRDF/S

TimeFinder/FS, NearCopy, FarCopy and VNX FileMover 21

Concepts


22/116

Table 3. Comparison of VNX high-availability and replication products(continued)


Cannot be used in the sameVNX configuration as Mir-rorView/S. Cannot be usedwith the Automatic File Sys-tem Extension feature.

Performs volume cloning, notfile system cloning. Remotevolumes are only accessibleafter a failover.

Using attached VNX andSymmetrix pairs, performsasynchronous, point-in-timereplication at an extendeddistance. Using SRDF/A withVNXprovides more detailsabout SRDF/A.

Symmetrix only, DMX seriesSRDF/A

A single file system shouldoccupy an entire STD vol-ume.TimeFinder/FS does not

perform volume cloning.

Using a business continu-ance configuration with Sym-metrix BCVs, provides local

file system cloning.

Symmetrix onlyTimeFinder/FS

NearCopy is limited to 200km and FarCopy supportsextended distances.

NearCopy relies on SRDF/Sand FarCopy relies on SRDFadaptive copy disk-pendingmode to manage file systemsnapshots.

TimeFinder/FS NearCopyand FarCopy do not workwith Automatic File System

Extension.

These products do not per-form volume cloning.

Using a business continu-ance configuration with Sym-metrix BCVs, provides re-mote file system cloning, cre-ating a point-in-time copy(snapshot) of a VNX PFS.

A remote file system can bemounted and used duringnormal operation, that is, it isgenerally accessible.

Symmetrix onlyTimeFinder/FSNearCopy and FarCopy

For TimeFinder/FS,NearCopy, or FarCopy, aBCV cannot be a source or adestination file system forreplication. Can replicate theunderlying source file system,but not the BCV.

Cannot use the TimeFind-er/FS -Restore option for a

replicated source file system.Replication is unaware of anychanges because thesechanges occur at the volumelevel.

Produces a read-only, point-in-time copy of a source filesystem and periodically up-dates this copy, making itconsistent with the source filesystem.The read-only copycan be used by a Data Moverin the same VNX cabinet, orby a Data Mover at a remote

site for content distribution,backup, and application test-ing.

Using VNX Replicatorpro-vides more details.

VNX-supported storage with oneSymmetrix or VNX for block pair

VNX Replicator


Concepts


23/116

Table 3. Comparison of VNX high-availability and replication products(continued)


Not intended to be a mirror,disaster recovery, or high-availability tool. Because it ispartially derived from realtimePFS data, a checkpoint mightbecome inaccessible or un-readable if the PFS becomesinaccessible. Only check-points and a PFS saved totape or to an alternate stor-age location can be used toprovide disaster recovery.

In version 5.6, SnapSure

supports 112 checkpoints, 96in 5.5, 64 in 5.4, and 32 priorto 5.4.

Provides point-in-time logicalcopies, also known ascheckpoints, of a PFS on aVNX system.

VNX-supported storageEMC SnapSure

Comparison of VNX high-availability and replication products 23

Concepts


24/116

TimeFinder/FS, NearCopy, and FarCopy tasks overview

Table 4 on page 24provides an overview of the basic TimeFinder/FS, NearCopy, andFarCopy tasks and their associated VNX commands.

Table 4. TimeFinder/FS basic task overview

DescriptionCommand usedTask

For basic TimeFinder/FS andNearCopy, run the command with thePFS name and the Snapshot option.A snapshot name is assigned auto-matically.

If you want to keep the snapshot inmirror mode, you can specify the op-

tion mirror=on.For systems with local and R1 BCVs,such as in FarCopy, you can run thecommand with an option to specifythe type of BCV volume to use whencreating a snapshot. For example,fs_timefinder ufs1-Snapshot -optiondisktype=R1BCV.

fs_timefinder

-Snapshot

or

fs_timefinder {|id=} | [

-name ] -Snapshot [-volume]

[-option ]

Create a TimeFinder/FSsnapshot.

Use either method to update a snap-shot, which must be unmounted.

The mirroring options control mirror-ing mode.When you turn mirroring

on, it synchronizes the unmountedfile system copy with the original filesystem. In mirroring mode, anychanges made to the original filesystem are propagated to the copy.Clients can access the PFS whilemirroring is on, but cannot access thesnapshot file system. After mirroringis turned off, clients can access thesnapshot.

fs_timefinder

-Mirror on | off

or

fs_timefinder

-Mirror refresh [-Force]

Update a TimeFinder/FSsnapshot.


Concepts


25/116

Table 4. TimeFinder/FS basic task overview(continued)


The refresh option mirrors on and offthe snapshot, which must be un-mounted, to automatically resynchro-nize it with the PFS. When the syn-chronization completes, the snapshotis immediately available for mountingand exporting. If the file system copyis mounted read/write, the Force op-tion can be used to force a refresh ifthe metavolume is an STD type. TheForce option requires root privilegesand must be run by using/nas/sbin/rootfs_timefinder.

Restores or writes over the PFS datawith the data from the snapshot.

You should unmount the file systembefore the restore.The -Force optionis required if the file system ismounted, but this is generally notrecommended.

To perform the restore, run the com-mand by using/nas/sbin/rootfs_timefinder.

You can specify mirror=on as an op-tion to place the file system copy inmirror mode.

/nas/sbin/rootfs_timefinder

-Restore[-Force][-option

]

Restore a PFS from aTimeFinder/FS snapshot.

Does an immediate mirror on and offto refresh the R2 BCV.

Synchronizes the local R1 BCV withthe remote R2 BCV.

Other available fs_rdf options enableyou to control mirroring of the SRDFdrives of a file system, such as mirroron and off.The -info option displaysinformation about the SRDF relation-ships.

fs_rdf

-Mirror refresh

Update the imported filesystem by synchronizingthe R1 BCV with the R2BCV in a FarCopy configu-ration with SRDF.

Restores the R1 or source volumes

from the imported R2 volumes or filesystem.

Applies to TimeFinder/FS NearCopyand FarCopy configurations.

/nas/sbin/rootfs_rdf

-Restore

Restore the source vol-

umes from the imported filesystem in a NearCopy orFarCopy configuration withSRDF.

TimeFinder/FS, NearCopy, and FarCopy tasks overview 25

Concepts


26/116

Table 4. TimeFinder/FS basic task overview(continued)


The info and list options provide infor-mation about the snapshot, such asthe file system type.

File system types are as follows:

1 uxfs; default

5 rawfs; unformatted file system

6 mirrorfs; mirrored file system

7 ckpt; checkpoint

8 mgfs; migration file system

100 group file system

102 nmfs; nested mount file sys-tem

The nas_fs -list -all command can beused to identify checkpoints that needto be deleted before a restore.

The -delete option deletes a file sys-tem, such as a checkpoint you needto delete for a restore.

Other VNX commands useful in per-forming management operations in-clude cel_fs, nas_cel, server_mount-point, server_mount, server_export,server_df, and server_umount. For

implementations involving SRDF, themain VNX SRDF configuration com-mand is nas_rdf.

nas_fs -info

or

nas_fs-list -all

or

nas_fs -delete

Manage TimeFinder/FSsnapshots.


Concepts


27/116

3

Configuring

The tasks to configure TimeFinder/FS, NearCopy, and FarCopy are:

Create a TimeFinder/FS snapshot on page 28 Update a TimeFinder/FS snapshot on page 33 Restore the PFS on page 41 Create a NearCopy snapshot on page 43 Restore the local PFS from a NearCopy snapshot on page 56 Create a FarCopy snapshot on page 65 Refresh the FarCopy snapshot on page 78 Restore the PFS from the FarCopy snapshot on page 84 Extend a PFS with a FarCopy snapshot on page 89



28/116

Create a TimeFinder/FS snapshot

Creating a TimeFinder/FS snapshot is a full-establish process that synchronizes the BCVwith data from the PFS to create a point-in-time copy. At any time, you can update orresynchronize a snapshot with the PFS by unmounting it and performing a mirror-on andmirror-off sequence, or by simply refreshing the snapshot.

The tasks to create a TimeFinder/FS snapshot and make it available are:

1. Create a snapshot on page 28

2. Make the snapshot available on page 30

Note: Creating a TimeFinder/FS snapshot can be a time-consuming process, depending on the sizeof the PFS.

Create a snapshot

Action

To create a TimeFinder/FS snapshot of a PFS, use this command syntax:

$ fs_timefinder -Snapshot

where:

= name of the PFS to copy

Example:

To create a TimeFinder/FS snapshot of the PFS ufs3, type:

$ fs_timefinder ufs3 -Snapshot


Configuring


29/116

Output

operation in progress (not interruptible)...remainder(MB) =

68062..62214..56301..50942..45510..39688..33858..28063..22437..18293..14073..9859..5734..2372..0operation in progress (not interruptible)...id = 20name = ufs3acl = 0in_use = Truetype = uxfsvolume = mv3pool =rw_servers= server_2ro_servers=rw_vdms =ro_vdms =backups = ufs3_snap1ckpts = ufs3_ckpt1stor_devs = 000185500440-0040, 000185500440-0041,000185500440-044,0000185500440-0045,000185500440-0046,

000185500440-0047, 000185500440-0048, 000185500440-0049disks = d49, d50, d53, d54, d55, d56, d57, d58disk=d49 stor_dev=000185500440-0040 addr=c0t3l14-03-0server=server_2disk=d49 stor_dev=000185500440-0040 addr=c16t3l14-30-0server=server_2disk=d50 stor_dev=000185500440-0041 addr=c0t3l15-03-0server=server_2disk=d50 stor_dev=000185500440-0041 addr=c16t3l15-30-0server=server_2disk=d53 stor_dev=000185500440-0044 addr=c0t4l2-03-0server=server_2disk=d53 stor_dev=000185500440-0044 addr=c16t4l2-30-0server=server_2disk=d54 stor_dev=000185500440-0045 addr=c0t4l3-03-0server=server_2

disk=d54 stor_dev=000185500440-0045 addr=c16t4l3-30-0server=server_2disk=d56 stor_dev=000185500440-0047 addr=c0t4l5-03-0server=server_2disk=d56 stor_dev=000185500440-0047 addr=c16t4l5-30-0server=server_2disk=d57 stor_dev=000185500440-0048 addr=c0t4l6-03-0server=server_2disk=d57 stor_dev=000185500440-0048 addr=c16t4l6-30-0server=server_2disk=d58 stor_dev=000185500440-0049 addr=c0t4l7-03-0server=server_2disk=d58 stor_dev=000185500440-0049 addr=c16t4l7-30-0server=server_2id = 26name = ufs3_snap1

acl = 0in_use = Falsetype = uxfsvolume = v321pool =rw_servers=

Create a TimeFinder/FS snapshot 29

Configuring


30/116

Output

ro_servers=rw_vdms =

ro_vdms =backup_of = ufs3 Tue Jun 15 14:04:51 EDT 2004stor_devs = 000185500440-00D2,000185500440-00D3,000185500440-00D4,000185500440-00D5,000185500440-00D6,000185500440-00D7,000185500440-00D8,000185500440-00D9disks = rootd67, rootd68, rootd69, rootd70, rootd71, rootd72,rootd73,rootd74

Note

In the example, no snapshot name or metavolume is specified. Therefore the system uses defaults.The default nameassigned to a snapshot is _snap, where n is a sequential number indicating the existing number of PFSsnapshots. By default, the snapshot is created on the next available BCV that is the same size as the PFS. The onlineVNX for file man pages or the EMC VNX Command Line Interface Reference for Filedescribes how to specify a customname or metavolume for a snapshot.

Make the snapshot available

When the snapshot creation process completes, the system detaches the snapshot fromthe PFS.

The tasks to make the snapshot available for use are:

1. Create a mount point on page 31

2. Mount the TimeFinder/FS snapshot on page 31

3. List the mounted file systems on page 55

4. Export the file system copy on page 55


Configuring


31/116

Create a mount point

Action

To create a mount point on the local Data Mover, use this command syntax:

$ server_mountpoint -create

where:

= name of the local Data Mover

= pathname preceded by a forward slash (/)

Example:

To create a mount point with the pathname ufs3_snap1 on the local Data Mover server_2, type:

$ server_mountpoint server_2 -create /ufs3_snap1

Output

server_2 : done

Mount the TimeFinder/FS snapshot

Action

To mount the TimeFinder/FS snapshot on the local Data Mover, use this command syntax:

$ server_mount

where:


= name of the file system= the mount point

Example:

To mount the TimeFinder/FS snapshot ufs3_snap1 on the local Data Mover server_2, type:

$ server_mount server_2 ufs3_snap1 /ufs3_snap1

Output

server_2 : done

Note

By default, BCV snapshots are mounted as read-only. However, you can mount them as read/write, if necessary.

Create a TimeFinder/FS snapshot 31

Configuring


32/116

List the mounted file systems

Action

To list the mounted file systems, including the NearCopy snapshot, on the local Data Mover, use this command syntax:

$ server_mount

where:


Example:

To list the mounted file systems, including the NearCopy snapshot, on the local Data Mover server_4, type:

$ server_mount server_4

Output

server_4 :root_fs_4 on / uxfs,perm,rwroot_fs_common on /.etc_common uxfs,perm,roufs1_snap1 on /ufs1_snap1 uxfs,perm,ro

Export the file system copy

The NearCopy snapshot is a complete replica of a PFS, including all security andauthorization credentials for NFS and CIFS.

Action

To export the file system copy, use this command syntax:

$ server_export -option

where:


= the chosen option (for root privileges, root=)


Example:

To export the file system copy on local Data Mover server_2 by using the root privileges option root=192.168.96.79, type:

$ server_export server_2 -option root=192.168.96.79 /ufs1_snap1

Output

server_2 : done

Note

A BCV snapshot is a complete replica of a PFS, including all security and authorization credentials for NFS and CIFS.


Configuring


33/116

Update a TimeFinder/FS snapshot

At any time after creating a TimeFinder/FS snapshot of a PFS and making it available, youcan update or resynchronize an unmounted snapshot with the PFS.

To update or resynchronize:

Mirror on and mirror off a TimeFinder/FS snapshot, which causes the system tosynchronize the snapshot with the PFS immediately. The synchronization persistsindefinitely until the mirroring is stopped, that is, until you mirror off the snapshot.

Note: Before you mirror on or refresh a snapshot, unmount it. The mirroring process cannot beinterrupted. When you mirror on a snapshot, it is considered to be in mirror mode or mirrored on.Only one snapshot of the PFS can be in mirror mode at a time.

Refresh a TimeFinder/FS snapshot, which starts the mirroring and then immediately

stops, thereby updating the snapshot with the latest PFS data and making it immediatelyavailable for mounting or exporting. Using the refresh option has the same effect asmirroring on, and then mirroring off the snapshot. The refresh option offers flexibility insnapshot management. For example, keep one snapshot mirrored on to remainsynchronized with the PFS for business continuance protection while you refresh anothersnapshot to capture a specific point-in-time view of the PFS.

The tasks to update a TimeFinder/FS snapshot are:

1. Verify that a snapshot is in mirror mode on page 33

2. Unmount the snapshot on page 34

3. Mirror on and off the TimeFinder/FS snapshot on page 35

4. Refresh the snapshot (Optional) on page 39

Verify that a snapshot is in mirror mode

Action

To verify that a snapshot is currently mirrored on by listing snapshot-specific information, use this command syntax:

$ nas_fs-info

where:

= name of the specific TimeFinder/FS snapshot to view

Example:

To verify the status of the snapshot ufs3_snap1, type:

$ nas_fs -info ufs3_snap1

Update a TimeFinder/FS snapshot 33

Configuring


34/116

Output

id = 26name = ufs3_snap1

acl = 0in_use = Falsetype = uxfsvolume = v321pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = ufs3 Tue Jun 15 14:04:51 EDT 2004stor_devs = 000185500440-00D2,000185500440-00D3,000185500440-00D4,000185500440-00D5,000185500440-00D6,000185500440-00D7,000185500440-00D8,000185500440-00D9disks = rootd67,rootd68,rootd69,rootd70,rootd71,rootd72,rootd73,rootd74

Note

Check the values in the output. If the file system type = uxfs, the snapshot is not in mirror mode. If the file system type =mirrorfs, the snapshot is in mirror mode.You cannot restore a PFS from a snapshot that is in mirror mode. If in_use =False, the snapshot is unmounted. If in_use = True, the snapshot is mounted. To determine if the PFS has any SnapSureor VNX Replicator checkpoints associated with it that need to be deleted before a restore, use the nas_fs -list -all command.You can also use the nas_fs -list command to verify the status of all snapshots. List information on all file systems on page95provides more details.

Unmount the snapshot

Action

To unmount the snapshot, use this command syntax:

$ server_umount-perm [ ]

where:


= name of the file system

= the mount point

Example:

To unmount the snapshot at the mount point ufs3_snap1 on the local Data Mover server_2, type:

$ server_umount server_2 -perm ufs3_snap1

Output

$ server_2 : done


Configuring


35/116

Mirror on and off the TimeFinder/FS snapshot

When you perform the mirror-on procedure on the snapshot, the system immediatelysynchronizes the snapshot with the PFS.The synchronization persists indefinitely until youdecide to stop the mirroring, that is, mirror off the snapshot.

The steps to mirror on and off the TimeFinder/FS snapshot are:

1. Mirror on the TimeFinder/FS snapshot on page 35

2. Mirror off the TimeFinder/FS snapshot on page 37

Mirror on the TimeFinder/FS snapshot

Action

To mirror on the TimeFinder/FS snapshot, use this command syntax:$ fs_timefinder -Mirror on

where:

= name of the TimeFinder/FS snapshot to synchronize with the PFS

Example:

To mirror on the TimeFinder/FS snapshot ufs3_snap1, type:

$ fs_timefinder ufs3_snap1 -Mirror on


Configuring


36/116

Output

operation in progress (not interruptible)...id = 20name = ufs3

a c l = 0in_use = Truetype = uxfsvolume = mv3pool =rw_servers= server_2ro_servers=rw_vdms =ro_vdms =backups = ufs3_snap1ckpts = ufs3_ckpt1stor_devs = 000185500440-0040,000185500440-0041,000185500440-0044,000185500440-0045, 000185500440-0046,000185500440-0047,000185500440-0048,000185500440-0049disks = d49,d50,d53,d54,d55,d56,d57,d58disk=d49 stor_dev=000185500440-0040 addr=c0t3l14-03-0

server=server_2disk=d49 stor_dev=000185500440-0040 addr=c16t3l14-30-0server=server_2disk=d50 stor_dev=000185500440-0041 addr=c0t3l15-03-0server=server_2disk=d50 stor_dev=000185500440-0041 addr=c16t3l15-30-0server=server_2disk=d53 stor_dev=000185500440-0044 addr=c0t4l2-03-0server=server_2disk=d53 stor_dev=000185500440-0044 addr=c16t4l2-30-0server=server_2disk=d54 stor_dev=000185500440-0045 addr=c0t4l3-03-0server=server_2disk=d54 stor_dev=000185500440-0045 addr=c16t4l3-30-0server=server_2disk=d55 stor_dev=000185500440-0046 addr=c0t4l4-03-0

server=server_2disk=d55 stor_dev=000185500440-0046 addr=c16t4l4-30-0server=server_2disk=d56 stor_dev=000185500440-0047 addr=c0t4l5-03-0server=server_2disk=d56 stor_dev=000185500440-0047 addr=c16t4l5-30-0server=server_2disk=d57 stor_dev=000185500440-0048 addr=c0t4l6-03-0server=server_2disk=d57 stor_dev=000185500440-0048 addr=c16t4l6-30-0server=server_2disk=d58 stor_dev=000185500440-0049 addr=c0t4l7-03-0server=server_2disk=d58 stor_dev=000185500440-0049 addr=c16t4l7-30-0server=server_2


Configuring


37/116

Output

i d = 2 6name = ufs3_snap1

a c l = 0in_use = Falsetype = mirrorfsvolume = v321pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = ufs3 Tue Jun 15 14:04:51 EDT 2004remainder = 0 MB (0%)stor_devs = 000185500440-00D2,000185500440-00D3,000185500440-00D4,000185500440-00D5, 000185500440-00D6,000185500440-00D7,000185500440-00D8,000185500440-00D9disks = rootd67,rootd68,rootd69,rootd70,rootd71,rootd72,rootd73,rootd74

Mirror off the TimeFinder/FS snapshot

At any time, you can mirror off a TimeFinder/FS snapshot that is in mirror mode. Mirroringoff the snapshot stops synchronization of the snapshot with the PFS. Thus it captures thelatest point-in-time data of the PFS, and then makes the copy immediately available formounting and exporting.

Action

To mirror off the TimeFinder/FS snapshot, use this command syntax:

$ fs_timefinder -Mirror off

where:

= name of the TimeFinder/FS snapshot to mirror off from the PFS

Example:

To mirror off the TimeFinder/FS snapshot ufs3_snap1, type:

$ fs_timefinder ufs3_snap1 -Mirror off


Configuring


38/116

Output

operation in progress (not interruptible)...remainder(MB) = 0

operation in progress (not interruptible)...id = 20name = ufs3a c l = 0in_use = Truetype = uxfsvolume = mv3pool =rw_servers= server_2ro_servers=rw_vdms =ro_vdms =backups = ufs3_snap1ckpts = ufs3_ckpt1

stor_devs = 000185500440-0040,000185500440-0041,000185500440-0044,000185500440-0045, 000185500440-0046,000185500440-0047,000185500440-

0048,000185500440-0049disks = d49,d50,d53,d54,d55,d56,d57,d58disk=d49 stor_dev=000185500440-0040 addr=c0t3l14-03-0server=server_2disk=d49 stor_dev=000185500440-0040 addr=c16t3l14-30-0server=server_2disk=d50 stor_dev=000185500440-0041 addr=c0t3l15-03-0server=server_2disk=d50 stor_dev=000185500440-0041 addr=c16t3l15-30-0server=server_2disk=d53 stor_dev=000185500440-0044 addr=c0t4l2-03-0server=server_2disk=d53 stor_dev=000185500440-0044 addr=c16t4l2-30-0server=server_2disk=d54 stor_dev=000185500440-0045 addr=c0t4l3-03-0server=server_2

disk=d54 stor_dev=000185500440-0045 addr=c16t4l3-30-0server=server_2disk=d55 stor_dev=000185500440-0046 addr=c0t4l4-03-0server=server_2disk=d55 stor_dev=000185500440-0046 addr=c16t4l4-30-0server=server_2disk=d56 stor_dev=000185500440-0047 addr=c0t4l5-03-0server=server_2disk=d57 stor_dev=000185500440-0048 addr=c0t4l6-03-0server=server_2disk=d57 stor_dev=000185500440-0048 addr=c16t4l6-30-0server=server_2disk=d58 stor_dev=000185500440-0049 addr=c0t4l7-03-0server=server_2disk=d58 stor_dev=000185500440-0049 addr=c16t4l7-30-0server=server_2

i d = 2 6name = ufs3_snap1a c l = 0in_use = Falsetype = uxfsvolume = v321


Configuring


39/116

Output

pool =rw_servers=

ro_servers=rw_vdms =ro_vdms =backup_of = ufs3 Tue Jun 15 14:20:30 EDT 2004stor_devs = 000185500440-00D2,000185500440-00D3,000185500440-00D4,000185500440-00D5, 000185500440-00D6,000185500440-00D7,000185500440-00D8,000185500440-00D9disks = rootd67,rootd68,rootd69,rootd70,rootd71,rootd72,rootd73,rootd74

Refresh the snapshot (Optional)

As an alternative to mirroring on and off a snapshot, you can refresh the snapshot with asingle command.

Refreshing a TimeFinder/FS snapshot causes mirroring to start and then immediately stop,thereby updating the snapshot with the latest PFS data and making it immediately availablefor mounting or exporting. The snapshot file system must be unmouted before you canrefresh it. Unmount the snapshot on page 34provides details to unmount a snapshot.

Action

To refresh an unmounted TimeFinder/FS snapshot, use this command syntax:

$ fs_timefinder -Mirror refresh

where:

= name of the TimeFinder/FS snapshot to update with PFS data.Example:

To refresh TimeFinder/FS snapshot ufs3_snap1, type:

$ fs_timefinder ufs3_snap1 -Mirror refresh


Configuring


40/116

Output


operation in progress (not interruptible)...id = 20name = ufs3acl = 0in_use = Truetype = uxfsvolume = mv3pool =rw_servers= server_2ro_servers=rw_vdms =ro_vdms =backups = ufs3_snap1ckpts = ufs3_ckpt1stor_devs = 000185500440-0040,000185500440-0041,000185500440-0044,000185500440-0045,000185500440-0046,000185500440-0047,000185500440-0048,000185500440-0049

disks = d49,d50,d53,d54,d55,d56,d57,d58

disk=d49 stor_dev=000185500440-0040 addr=c0t3l14-03-0 server=server_2disk=d49 stor_dev=000185500440-0040 addr=c16t3l14-30-0 server=server_2disk=d50 stor_dev=000185500440-0041 addr=c0t3l15-03-0 server=server_2disk=d50 stor_dev=000185500440-0041 addr=c16t3l15-30-0 server=server_2disk=d53 stor_dev=000185500440-0044 addr=c0t4l2-03-0 server=server_2disk=d53 stor_dev=000185500440-0044 addr=c16t4l2-30-0 server=server_2disk=d54 stor_dev=000185500440-0045 addr=c0t4l3-03-0 server=server_2disk=d54 stor_dev=000185500440-0045 addr=c0t4l3-03-0 server=server_2disk=d54 stor_dev=000185500440-0045 addr=c16t4l3-30-0 server=server_2disk=d55 stor_dev=000185500440-0046 addr=c0t4l4-03-0 server=server_2disk=d55 stor_dev=000185500440-0046 addr=c16t4l4-30-0 server=server_2disk=d56 stor_dev=000185500440-0047 addr=c0t4l5-03-0 server=server_2disk=d56 stor_dev=000185500440-0047 addr=c16t4l5-30-0 server=server_2disk=d57 stor_dev=000185500440-0048 addr=c0t4l6-03-0 server=server_2

disk=d57 stor_dev=000185500440-0048 addr=c16t4l6-30-0 server=server_2disk=d58 stor_dev=000185500440-0049 addr=c0t4l7-03-0 server=server_2disk=d58 stor_dev=000185500440-0049 addr=c16t4l7-30-0 server=server_2

id = 26name = ufs3_snap1acl = 0in_use = Falsetype = uxfsvolume = v321pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = ufs3 Tue Jun 15 14:22:30 EDT 2004

stor_devs = 000185500440-00D2,000185500440-00D3,000185500440-00D4,000185500440-00D5,000185500440-00D6,000185500440-00D7,000185500440-00D8,000185500440-00D9disks = rootd67,rootd68,rootd69,rootd70,rootd71,rootd72,rootd73,rootd74


Configuring


41/116

Restore the PFS

You can restore a PFS by using the data in a mirrored-off TimeFinder/FS snapshot. Restoringoverwrites the data in the PFS.

The tasks to restore the PFS by using a TimeFinder/FS snapshot are:

1. Verify file system information before the restore on page 41

2. Restore the file system on page 42

Note: The restore operation cannot be interrupted and is irreversible.

Verify file system information before the restore

List the file systems and make sure that:

The TimeFinder/FS snapshot you plan to use as the source for the restore is unmountedand not in mirror mode.

The PFS has no SnapSure or VNX Replicator (including internal) checkpoints on it. Ifthese checkpoints exist, delete the checkpoints by using the nas_fs -delete command before proceeding, as shown in Delete TimeFinder/FSsnapshots on page 96.

Action

To list general information about all file systems on the VNX system, type:

$ nas_fs -list -all |tail

Output

id inuse type acl volume name server.14 n 1 0 224 root_fs_1415 n 1 0 226 root_fs_1516 y 1 0 228 root_fs_common 4,3,2,117 n 5 0 277 root_fs_ufslog18 y 1 0 292 ufs1 119 y 1 0 293 ufs2 120 y 1 0 294 ufs3 124 n 7 0 301 ufs3_ckpt1

25 n 1 0 319 ufs1_snap126 n 1 0 321 ufs3_snap1

Restore the PFS 41

Configuring


42/116

Note

In the example, you cannot restore ufs3_snap1 until you delete the SnapSure or Replicator checkpoint ufs3_ckpt1 by usingthe nas_fs -delete ufs3_ckpt1 command. However, you can restore PFS ufs1 by using its TimeFinder/FS snapshot,ufs1_snap1, because ufs1 does not have any SnapSure or Replicator checkpoints associated with it that need to bedeleted. Also, ufs1_snap1 is unmounted (inuse = n), which is another prerequisite to a restore operation. If the file systemtype is 1, the snapshot is not in mirror mode. If the file system type is 6, the snapshot is in mirror mode. You cannot restorea PFS from a snapshot in mirror mode.

Restore the file system

You must have root privileges to restore a file system.

Action

To restore a file system, use this command syntax:$ /nas/sbin/rootfs_timefinder -Restore

where:

= name of the TimeFinder/FS snapshot from which to restore the PFS data

Example:

To restore PFS ufs3 by using the data in snapshot ufs3_snap1 after ensuring that no checkpoints exist, type:

$ /nas/sbin/rootfs_timefinder ufs3_snap1 -Restore


Configuring


43/116

Output


operation in progress (not interruptible)...id = 26name = ufs3_snap1acl = 0in_use = Falsetype = uxfsvolume = v321pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = ufs3 Tue Jun 15 14:22:30 EDT 2004stor_devs = 000185500440-00D2,000185500440-00D3,000185500440-00D4,000185500440-00D5, 000185500440-00D6,000185500440-00D7,000185500440-00D8,000185500440-00D9disks = rootd67,rootd68,rootd69,rootd70,rootd71,rootd72,rootd73,rootd74

id = 20name = ufs3acl = 0in_use = Falsetype = uxfsvolume = mv3pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backups = ufs3_snap1stor_devs = 000185500440-0040,000185500440-0041,000185500440-0044,000185500440-0045, 000185500440-0046,000185500440-0047,000185500440-0048,

000185500440-0049disks = d49,d50,d53,d54,d55,d56,d57,d58

Create a NearCopy snapshot

Before proceeding, make sure that an SRDF/S campus configuration is set up and initializedfor disaster recovery. If not, review the SRDF setup requirements in Using SRDF/S withVNX for Disaster Recovery. If necessary, contact your local EMC Customer SupportRepresentative.

The tasks to create a NearCopy snapshot on the remote BCV are:

1. Identify the local and remote VNX systems on page 44

2. Import the PFS on page 463. Create a NearCopy snapshot of the imported file system on page 50

4. Refresh a NearCopy snapshot of the imported file system on page 51

5. Make the NearCopy snapshot available on page 53

Create a NearCopy snapshot 43

Configuring


44/116

Note: For information about the options for an SRDF extended-distance or other high-availabilitystorage configuration, contact your local EMC sales organization.Appendix Aprovides illustrations ofEMC high-availability offerings. When using SRDF/S, do not shut down or reboot any of the

SRDF-protected or non-SRDF Data Movers while the SRDF nas_rdf -restore command is running.Doing so might interrupt the VNX systems communication with the storage system and cause thecommand to fail.

Identify the local and remote VNX systems

Identifying the local and remote VNX systems involves listing the file systems on the localand remote systems that are linked through SRDF channels. In this example, VNX1 andVNX2 represent the local and remote VNX systems, respectively.

The tasks to identify the local and remote VNX systems are:

1. List the SRDF-linked VNX systems seen by VNX2 on page 44

2. List the file systems local to VNX1 on page 44

3. List the file systems local to VNX2 on page 45

List the SRDF-linked VNX systems seen by VNX2

Action

To list the SRDF- linked VNX systems recognized by VNX2, type:

$ nas_cel -list

Output

id name owner mount_dev channel net_path CMU0 VNX2 0 192.168.96.79 00018550034100081 VNX1 500 /dev/sdj1 /dev/sdg 192.168.96.78 0001855004400000

List the file systems local to VNX1

Action

To list the file systems local to VNX1, on the destination VNX, use this command syntax:

$ cel_fs -list

where:

= name of the specified VNX

Example:

To list the file systems local to VNX1, from VNX2, type:

$ cel_fs VNX1 -list


Configuring


45/116

Output

id inuse type acl volume name server1 n 1 0 282 root_fs_1

2 y 1 0 284 root_fs_2 13 y 1 0 286 root_fs_3 24 y 1 0 288 root_fs_4 35 y 1 0 290 root_fs_5 46 n 1 0 292 root_fs_67 n 1 0 294 root_fs_78 n 1 0 296 root_fs_89 n 1 0 298 root_fs_910 n 1 0 300 root_fs_1011 n 1 0 302 root_fs_1112 n 1 0 304 root_fs_1213 n 1 0 306 root_fs_1314 n 1 0 308 root_fs_1415 n 1 0 310 root_fs_1516 y 1 0 312 root_fs_common 1,4,217 n 5 0 361 root_fs_ufslog

22 y 1 0 388 ufs1 124 y 1 0 390 ufs2 231 y 7 0 402 ufs2_ckpt1 252 n 1 0 419 mc154 n 1 0 420 mc1_snap155 n 1 0 421 mc1_snap256 n 1 0 422 mc1_snap357 n 1 0 423 mc258 n 1 0 424 mc359 n 1 0 425 mc460 n 1 0 426 mc561 n 1 0 427 mc662 n 1 0 428 mc763 n 1 0 429 mc864 n 1 0 431 mc2_snap165 n 1 0 432 mc5_snap1

66 n 1 0 433 mc4_snap167 n 1 0 434 mc3_snap168 n 1 0 435 mc6_snap169 n 1 0 436 mc8_snap170 n 1 0 437 mc7_snap171 n 100 0 0 g173 n 7 0 440 ufs1_ckpt177 n 100 0 0 76_000185500440000078 n 7 0 440 ufs1_ckpt279 n 1 0 454 ufs3

List the file systems local to VNX2

Action

To display information about the file systems currently local to VNX2, type:

$ nas_fs -list


Configuring


46/116

Output

id inuse type acl volume name server1 n 1 0 134 root_fs_1

2 y 1 0 136 root_fs_2 13 y 1 0 138 root_fs_3 24 y 1 0 140 root_fs_4 35 y 1 0 142 root_fs_5 46 n 1 0 144 root_fs_67 n 1 0 146 root_fs_78 n 1 0 148 root_fs_89 n 1 0 150 root_fs_910 n 1 0 152 root_fs_1011 n 1 0 154 root_fs_1112 n 1 0 156 root_fs_1213 n 1 0 158 root_fs_1314 n 1 0 160 root_fs_1415 n 1 0 162 root_fs_1516 y 1 0 164 root_fs_common 4,3,2,117 n 5 0 213 root_fs_ufslog

Import the PFS

Importing the PFS creates a replica of the source PFS on the remote VNX2 by using theR2 volumes.TimeFinder/FS uses this imported file system as the base to create a remotesnapshot of the PFS. After you import a file system, it becomes a local file system to VNX2,and can be used as a source file system to create a NearCopy snapshot.

The tasks to import the PFS are:

1. Import the PFS from VNX1 to VNX2 on page 46

2. Verify that the imported file system is now local to VNX2 on page 47

3. Verify the contents of the imported file system on page 48

4. View the R2 volumes on page 48

Import the PFS from VNX1 to VNX2

Action

To import or create a replica of the PFS at the remote site, use this command syntax:

$ cel_fs -Import

where:

= name of the local VNX

= name of the file system to be imported into the remote site

Example:

To create a replica of ufs1 on VNX2, type:


Configuring


47/116

Action

$ cel_fs VNX1 -Import ufs1

Output

i d = 1 8name = ufs1a c l = 0in_use = Falsetype = uxfsworm = offvolume = v388pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = 22@1 Thu Feb 24 18:03:18 EST 2005remainder = 0 MB (0%)

stor_devs = 000185500341-0031,000185500341-0032,000185500341-0033,000185500341-0034,000185500341-0035,000185500341-0036,000185500341-0037,000185500341-0038disks = dd38,dd39,dd40,dd41,dd42,dd43,dd44,dd45

Verify that the imported file system is now local to VNX2

Action

To verify that the imported file system ufs1 is now a local file system to VNX2, type:

$ nas_fs -list

Output

id inuse type acl volume name server1 n 1 0 134 root_fs_12 y 1 0 136 root_fs_2 13 y 1 0 138 root_fs_3 24 y 1 0 140 root_fs_4 35 y 1 0 142 root_fs_5 46 n 1 0 144 root_fs_67 n 1 0 146 root_fs_78 n 1 0 148 root_fs_89 n 1 0 150 root_fs_910 n 1 0 152 root_fs_1011 n 1 0 154 root_fs_1112 n 1 0 156 root_fs_12

13 n 1 0 158 root_fs_1314 n 1 0 160 root_fs_1415 n 1 0 162 root_fs_1516 y 1 0 164 root_fs_common 4,3,2,117 n 5 0 213 root_fs_ufslog18 n 1 0 249 ufs1


Configuring


48/116

Verify the contents of the imported file system

Action

To display information about the imported file system ufs1, type:

$ nas_fs -info ufs1

Output

i d = 1 8name = ufs1a c l = 0in_use = Falsetype = uxfsworm = offvolume = v388pool =rw_servers=

ro_servers=rw_vdms =ro_vdms =backup_of = 22@1 Thu Feb 24 18:03:18 EST 2005remainder = 0 MB (0%)stor_devs = 000185500341-0031,000185500341-0032,000185500341-0033,000185500341-0034,000185500341-0035,000185500341-0036,000185500341-0037,000185500341-0038disks = dd38,dd39,dd40,dd41,dd42,dd43,dd44,dd45

View the R2 volumes

Action

To list the disks on the remote VNX2 and see the R2 volumes, type:

$ nas_disk -list


Configuring


49/116

Output

id inuse sizeMB storageID-devID type name servers1 y 4153 000185500341-0008 R1STD root_disk 1,2,3,4

2 y 4153 000185500341-0009 R1STD root_ldisk 1,2,3,43 n 8631 000185500341-0092 STD d3 1,2,3,44 n 8631 000185500341-0093 STD d4 1,2,3,45 n 8631 000185500341-0094 STD d5 1,2,3,46 n 8631 000185500341-0095 STD d6 1,2,3,47 n 8631 000185500341-0096 STD d7 1,2,3,48 n 8631 000185500341-0097 STD d8 1,2,3,49 n 8631 000185500341-0098 STD d9 1,2,3,410 n 8631 000185500341-0099 STD d10 1,2,3,411 n 8631 000185500341-009A STD d11 1,2,3,412 n 8631 000185500341-009B STD d12 1,2,3,413 n 8631 000185500341-009C STD d13 1,2,3,414 n 8631 000185500341-009D STD d14 1,2,3,415 n 8631 000185500341-009E STD d15 1,2,3,416 n 8631 000185500341-009F STD d16 1,2,3,417 n 8631 000185500341-00A0 STD d17 1,2,3,4

18 n 8631 000185500341-00A1 STD d18 1,2,3,419 n 8631 000185500341-00A2 STD d19 1,2,3,420 n 8631 000185500341-00A3 STD d20 1,2,3,421 n 8631 000185500341-00A4 STD d21 1,2,3,422 n 8631 000185500341-00A5 STD d22 1,2,3,423 n 8631 000185500341-00A6 STD d23 1,2,3,424 n 8631 000185500341-00A7 STD d24 1,2,3,425 n 8631 000185500341-00A8 STD d25 1,2,3,426 n 8631 000185500341-00A9 STD d26 1,2,3,427 n 8631 000185500341-00AA STD d27 1,2,3,428 n 8631 000185500341-00AB STD d28 1,2,3,429 n 8631 000185500341-00AC STD d29 1,2,3,430 n 8631 000185500341-00AD STD d30 1,2,3,431 n 8631 000185500341-00AE STD d31 1,2,3,432 n 8631 000185500341-00AF STD d32 1,2,3,433 n 8631 000185500341-00B0 STD d33 1,2,3,4

34 n 8631 000185500341-00B1 STD d34 1,2,3,435 n 8631 000185500341-00B2 STD d35 1,2,3,436 n 8631 000185500341-00B3 STD d36 1,2,3,437 n 8631 000185500341-00B4 STD d37 1,2,3,438 n 8631 000185500341-00B5 STD d38 1,2,3,4...129 n 8631 000185500341-0110 BCV rootd129 1,2,3,4130 n 8631 000185500341-0111 BCV rootd130 1,2,3,4131 y 8631 000185500341-0031 R2STD dd38132 y 8631 000185500341-0032 R2STD dd39133 y 8631 000185500341-0033 R2STD dd40134 y 8631 000185500341-0034 R2STD dd41135 y 8631 000185500341-0035 R2STD dd42136 y 8631 000185500341-0036 R2STD dd43137 y 8631 000185500341-0037 R2STD dd44138 y 8631 000185500341-0038 R2STD dd45

Note

The disks shown in the nas_fs -info ufs1 output in Verify the contents of the imported file system on page 48 correspondto the disks shown in the output in View the R2 volumes on page 48. In the output, "..." indicates a continuation of thedisks because not all disks are listed in this excerpt.


Configuring


50/116

Create a NearCopy snapshot of the imported file system

Creating a copy might be time-consuming depending on the size of the file system. Uponcreation, full synchronization of volumes occurs. After that, only incremental changes aresynchronized during refreshes.

Action

To create a NearCopy snapshot of an imported file system at the remote site, use this command syntax:

$ fs_timefinder -Snapshot

where:

= name of the imported file system

Example:

To create a NearCopy snapshot of ufs1, type:

$ fs_timefinder ufs1 -Snapshot


Configuring


51/116

Output

operation in progress (not interruptible)...remainder(MB) = ..67742..36538..5977..0

operation in progress (not interruptible)...id = 18name = ufs1acl = 0in_use = Falsetype = uxfsworm = offvolume = v388pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = 22@1 Thu Feb 24 18:03:18 EST 2005backups = ufs1_snap1remainder = 0 MB (0%)

stor_devs = 000185500341-0031,000185500341-0032,000185500341-0033,000185500341-0034,000185500341-0035,000185500341-0036,000185500341-0037,000185500341-0038disks = dd38,dd39,dd40,dd41,dd42,dd43,dd44,dd45id = 19name = ufs1_snap1acl = 0in_use = Falsetype = uxfsworm = offvolume = v251pool =rw_servers=ro_servers=rw_vdms =

ro_vdms =backup_of = ufs1 Thu Feb 24 18:22:21 EST 2005stor_devs = 000185500341-00D2,000185500341-00D3,000185500341-00D4,000185500341-00D5,000185500341-00D6,000185500341-00D7,000185500341-00D8,000185500341-00D9disks =rootd67,rootd68,rootd69,rootd70,rootd71,rootd72,rootd73,rootd74

Refresh a NearCopy snapshot of the imported file system

Refreshing the NearCopy snapshot of the imported file system updates the snapshot withchanges made to the PFS since its last update. During refresh, clients cannot access thesnapshot. The mirror-refresh command automatically turns mirroring off afterresynchronization. This is equivalent to using the mirror-on and mirror-off commands.

Note: The snapshot must be unmounted before you can refresh it.


Configuring


52/116

Action

To refresh the unmounted NearCopy snapshot, use this command syntax:

$ fs_timefinder -Mirror refresh

where:

= name of the file system copy

Example:

To refresh ufs1_snap1, type:

$ fs_timefinder ufs1_snap1 -Mirror refresh

Output

operation in progress (not interruptible)...remainder(MB) = ..17..0operation in progress (not interruptible)...

id = 18name = ufs1acl = 0in_use = Falsetype = uxfsworm = offvolume = v388pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = 22@1 Thu Feb 24 18:03:18 EST 2005backups = ufs1_snap1remainder = 0 MB (0%)stor_devs = 000185500341-0031,000185500341-0032,000185500341-0033,

000185500341-0034,000185500341-0035,000185500341-0036,000185500341-0037,000185500341-0038disks = dd38,dd39,dd40,dd41,dd42,dd43,dd44,dd45id = 19name = ufs1_snap1acl = 0in_use = Falsetype = uxfsworm = offvolume = v251pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = ufs1 Fri Feb 25 09:55:59 EST 2005stor_devs = 000185500341-00D2,000185500341-00D3,000185500341-00D4,000185500341-00D5,000185500341-00D6,000185500341-00D7,000185500341-00D8,000185500341-00D9disks = rootd67,rootd68,rootd69,rootd70,rootd71,rootd72,rootd73,rootd74


Configuring


53/116

Make the NearCopy snapshot available

The tasks to make the NearCopy snapshot available for use through a Data Mover on thedestination VNX are:

1. Create a mount point on page 53

2. Mount the NearCopy snapshot on page 53

3. List the mounted file systems on page 55

4. Export the file system copy on page 55

Create a mount point

Action

To create a mount point on the local Data Mover, use this command syntax:

$ server_mountpoint -create

where:



Example:

To create a mount point on the local Data Mover server_4, type:

$ server_mountpoint server_4 -create /ufs1_snap1

Output

server_4 : done

Mount the NearCopy snapshot

By default, BCV snapshots are mounted as read-only. However, you can mount them asread/write, if necessary.

Action

To mount the NearCopy snapshot on the local Data Mover, use this command syntax:

$ server_mount

where:



= the mount point

Example:


Configuring


54/116

Action

To mount the NearCopy snapshot on the local Data Mover server_4, type:

$ server_mount server_4 ufs1_snap1 /ufs1_snap1

Ouput

server_4 : done


Configuring


55/116

List the mounted file systems

Action

To list the mounted file systems, including the NearCopy snapshot, on the local Data Mover, use this command syntax:

$ server_mount

where:


Example:

To list the mounted file systems, including the NearCopy snapshot, on the local Data Mover server_4, type:

$ server_mount server_4

Output

server_4 :root_fs_4 on / uxfs,perm,rwroot_fs_common on /.etc_common uxfs,perm,roufs1_snap1 on /ufs1_snap1 uxfs,perm,ro

Export the file system copy

The NearCopy snapshot is a complete replica of a PFS, including all security andauthorization credentials for NFS and CIFS.

Action

To export the file system copy, use this command syntax:

$ server_export -option

where:


= the chosen option (for root privileges, root=)


Example:

To export the file system copy on local Data Mover server_2 by using the root privileges option root=192.168.96.79, type:

$ server_export server_2 -option root=192.168.96.79 /ufs1_snap1

Output

server_2 : done

Note

A BCV snapshot is a complete replica of a PFS, including all security and authorization credentials for NFS and CIFS.


Configuring


56/116

Restore the local PFS from a NearCopy snapshot

The tasks to restore a local PFS from a remote BCV snapshot are:

Verify that the NearCopy snapshot is not in use on page 56

Restore imported FS (R2) from the NearCopy snapshot on page 57

Verify that the PFS is not in use at the source on page 60

Restore the PFS from the imported file system (R2) on page 61

Mount the PFS on the Data Mover on page 63

Note: You must have root access rights at the local and remote sites to restore a PFS.

Verify that the NearCopy snapshot is not in use

To ensure that the NearCopy snapshot from which to restore the local PFS is not in use, listthe snapshot to verify if it is mounted. If it is, unexport and unmount it.

The tasks to unexport and unmount a snapshot are:

List the NearCopy snapshot on page 56

Unexport the NearCopy snapshot on page 57

Unmount the NearCopy snapshot on page 57

List the NearCopy snapshot

Action

To list the NearCopy snapshot for verifying if it is mounted on the Data Mover, type:

$ server_df server_4

Output

server_4 :Filesystem kbytes used avail capacity Mounted onufs1_snap1 69626136 64618520 5007616 93% /ufs1_snap1root_fs_common 13624 4728 8896 35% /.etc_common

root_fs_4 114592 96 114496 0% /


Configuring


57/116

Unexport the NearCopy snapshot

Action

To unexport the NearCopy snapshot from the Data Mover server_4, type:

$ server_export server_4 -unexport -perm /ufs1_snap1

Output

$ server_4 : done

Unmount the NearCopy snapshot

Action

To unmount the NearCopy snapshot, use this command syntax:

$ server_umount -perm

where:



= the mount point

Example:

To unmount the NearCopy snapshot on server_4, type:

$ server_umount server_4 -perm ufs1_snap1

Output

$ server_4 : done

Restore imported FS (R2) from the NearCopy snapshot

Restoring imported FS from NearCopy snapshot involves restoring the imported file systemand then querying the status of the SRDF device pairs to verify that they are suspended.

The tasks to restore the imported file system from the NearCopy snapshot are:

Restore the imported file system on page 58

List the SRDF device pairs (R1 and R2) on page 59

Query the SRDF device group on page 59

Restore the local PFS from a NearCopy snapshot 57

Configuring


58/116

Restore the imported file system

Action

To restore the imported file system by using the NearCopy snapshot, use this command syntax:

$ /nas/sbin/rootfs_timefinder -Restore

where:

= name of the file system copy

Example:

To restore the imported file system by using NearCopy snapshot ufs1_snap1, type:

$ /nas/sbin/rootfs_timefinder ufs1_snap1 -Restore

Output

operation in progress (not interruptible)...remainder(MB) = ..0operation in progress (not interruptible)...id = 19name = ufs1_snap1a c l = 0in_use = Falsetype = uxfsworm = offvolume = v251pool =rw_servers=ro_servers=rw_vdms =ro_vdms =backup_of = ufs1 Fri Feb 25 10:28:16 EST 2005stor_devs = 000185500341-00D2,000185500341-00D3,000185500341-00D4,

000185500341-00D5,000185500341-00D6,000185500341-00D7,000185500341-00D8,000185500341-00D9disks =rootd67,rootd68,rootd69,rootd70,rootd71,rootd72,rootd73,rootd74i d = 1 8name = ufs1a c l = 0n_use = Falsetype = uxfsworm = offvolume = v388pool =rw_servers=ro_servers=rw_vdms =ro_vdms =

backup_of = 22@1 Thu Feb 24 18:03:18 EST 2005backups = ufs1_snap1remainder = 1 MB (0%)stor_devs = 000185500341-0031,000185500341-0032,000185500341-0033,000185500341-0034,000185500341-0035,000185500341-0036,000185500341-0037,000185500341-0038disks = dd38,dd39,dd40,dd41,dd42,dd43,dd44,dd45


Configuring


59/116

List the SRDF device pairs (R1 and R2)

When the TimeFinder Restore command is run, the SRDF R1 and R2 device pairs that

comprise ufs1 are automatically suspended on the SRDF link. To verify SRDF device-groupinformation, run informational Solutions Enabler Symmetrix SYMCLI commands, such assymdg. The Solutions Enabler Symmetrix SRDF family documentation on theEMC OnlineSupportwebsite provides more information.

Action

To list the SRDF device groups, type:

$ /nas/symcli/bin/symdg list

Output

D E V I C E G R O U P SNumber of

Name Type Valid Symmetrix ID Devs GKs BCVs VDEVs1R1_1 RDF1 Yes 000185500341 6 0 0 01REG REGULAR Yes 000185500341 64 0 64 0cs_500 RDF2 Yes 000185500341 1 0 0 01R2_500_1 RDF2 Yes 000185500341 55 0 64 0

Query the SRDF device group

Note that symrdf is a SYMCLI command.

Action

To list information for a specific SRDF device group, use this command syntax:

$ /nas/symcli/bin/symrdf -g querywhere:

= name of the SRDF device group

Example:

To verify that the SRDF device pairs in the group 1R2_500_1 have suspended, type:

$ /nas/symcli/bin/symrdf -g 1R2_500_1 query


Configuring
http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/


60/116

Output

Device Group (DG) Name : 1R2_500_1DG's Type : RDF2

DG's Symmetrix ID : 000185500341Target (R2) View Source (R1) View MODES-------------------------------- --------------------- ----- ---------

ST LI STStandard A N ALogical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF PairDevice Dev E Tracks Tracks S Dev E Tracks Tracks MDA STATE------------------------------- - --------------------- --- -------------DEV001 0000 WD 0 0 RW 0000 RW 0 0 S.. SynchronizedDEV002 0001 WD 0 0 RW 0001 RW 0 0 S.. SynchronizedDEV003 0030 WD 0 0 RW 0030 RW 0 0 S.. SynchronizedDEV004 0031 WD 12 0 NR 0031 RW 0 1 S.. SuspendedDEV005 0032 WD 4 0 NR 0032 RW 0 0 S.. SuspendedDEV006 0033 WD 3 0 NR 0033 RW 0 0 S.. SuspendedDEV007 0034 WD 2 0 NR 0034 RW 0 0 S.. SuspendedDEV008 0035 WD 4 0 NR 0035 RW 0 0 S.. Suspended

DEV009 0036 WD 4 0 NR 0036 RW 0 0 S.. SuspendedDEV010 0037 WD 2 0 NR 0037 RW 0 0 S.. SuspendedDEV011 0038 WD 4 0 NR 0038 RW 0 0 S.. SuspendedDEV012 0039 WD 0 0 RW 0039 RW 0 0 S.. SynchronizedDEV013 003A WD 0 0 RW 003A RW 0 0 S.. Synchronize...DEV047 015C WD 0 0 RW 011C RW 0 0 S.. SynchronizedDEV048 015D WD 0 0 RW 011D RW 0 0 S.. SynchronizedDEV049 015E WD 0 0 RW 011E RW 0 0 S.. SynchronizedDEV050 015F WD 0 0 RW 011F RW 0 0 S.. SynchronizedDEV051 0160 WD 0 0 RW 0120 RW 0 0 S.. SynchronizedDEV052 0161 WD 0 0 RW 0121 RW 0 0 S.. SynchronizedDEV053 0003 WD 0 0 RW 0003 RW 0 0 S.. SynchronizedDEV054 0004 WD 0 0 RW 0004 RW 0 0 S.. SynchronizedDEV055 0005 WD 0 0 RW 0005 RW 0 0 S.. SynchronizedTotal -------- -------- -------- --------

Track(s) 35 0 0 1MB(s) 1.1 0.0 0.0 0.0

Legend for MODES:M(ode of Operation): A = Async, S = Sync, E = Semi-sync, C = Adaptive CopyD(omino) : X = Enabled, . = DisabledA(daptive Copy) : D = Disk Mode, W = WP Mode, . = ACp off

Verify that the PFS is not in use at the source

Before restoring the R1 volume from R2, verify that the PFS is not in use at the source. If itis in use, unmount the PFS.

The tasks to verify that the PFS is not in use at the source are:

Verify if the PFS is in use on page 61

Unmount the PFS on page 61


Configuring


61/116

Verify if the PFS is in use

Action

To verify that the PFS ufs1 is not in use, type:

$ server_df server_2

Output

Filesystem kbytes used avail capacity Mounted onufs1 69626136 64544992 5081144 93% /ufs1root_fs_common 13624 4728 8896 35% /.etc_commonroot_fs_2 114592 360 114232 0% /

Note

In the example, PFS ufs1 is in use (mounted) at the source. It must be unmounted to be used in the restore operation.

Unmount the PFS

Action

To unmount the PFS ufs1 on the Data Mover server_2, type:

$ server_umount server_2 ufs1

Output

server_2 : done

Restore the PFS from the imported file system (R2)

Action

To restore the primary R1 volumes from the imported R2 volumes or file system, type:

$ /nas/sbin/rootfs_rdf ufs1 -Restore


Configuring


62/116

Output

remainder(MB) = 1 0

i d = 2 2name = ufs1a c l = 0in_use = Falsetype = uxfsworm = offvolume = v388pool = symm_std_rdf_srcmember_of = root_avm_fs_group_8rw_servers=ro_servers=rw_vdms =ro_vdms =stor_devs = 000185500440-0031,000185500440-0032,000185500440-0033,000185500440-0034,000185500440-0035,000185500440-0036,000185500440-0037,000185500440-

0038disks = d38,d39,d40,d41,d42,d43,d44,d45

RDF Information:remote_symid = 000185500341remote_sym_devname =ra_group_number = 1dev_rdf_type = R1dev_ra_status = READYdev_link_status = READYrdf_mode = SYNCHRONOUSrdf_pair_state = SYNCHRONIZEDrdf_domino = DISABLEDadaptive_copy = DISABLEDadaptive_copy_skew = 65535num_r1_invalid_tracks = 0num_r2_invalid_tracks = 0

dev_rdf_state = READYremote_dev_rdf_state = WRITE_DISABLEDrdf_status = 0link_domino = DISABLEDprevent_auto_link_recovery = DISABLEDlink_config =suspend_state = NAconsistency_state = DISABLEDadaptive_copy_wp_state = NAprevent_ra_online_upon_pwron =

Documents

TimeFinder FS NearCopy and FarCopy