10. Configuration of snapshot methods for disk arrays. Symantec NetBackup 7.5
Symantec NetBackup Snapshot Client 7.5 is a powerful backup and recovery solution that provides a variety of snapshot-based features for NetBackup. It supports clients on UNIX, Linux, and Windows platforms, on Fibre Channel networks (SANs) or traditional LANs. The Snapshot Client provides several features including Instant Recovery, off-host backup, FlashBackup, and RealTime.
Advertisement
Advertisement
Chapter
10
Configuration of snapshot methods for disk arrays
This chapter includes the following topics:
■
About the new disk array snapshot methods
■
Disk array configuration tasks
■
OS-specific configuration tasks
■
About VSS configuration (Windows)
■
■
■
■
About IBM DS6000 and DS8000 arrays
■
■
About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
■
■
About the new disk array snapshot methods
These topics describe NetBackup's disk array snapshot methods. These methods take advantage of high-speed mirroring and other snapshot capabilities that are provided by particular disk arrays.
182 Configuration of snapshot methods for disk arrays
About the new disk array snapshot methods
The following snapshot methods support only English locale. They do not support
I18N (internationalization).
■ EMC_CLARiiON_Snapview_Clone
■ EMC_CLARiiON_Snapview_Snapshot
■ EMC_TimeFinder_Clone
■ EMC_TimeFinder_Mirror
■ EMC_TimeFinder_Snap Hitachi_ShadowImage
■ Hitachi_CopyOnWrite
■ HP_EVA_Vsnap
■ HP_EVA_Snapshot
■ HP_EVA_Snapclone
■ HP_XP_BuisinessCopy
■ HP_XP_Snapshot
■ IBM_DiskStorage_FlashCopy
■ IBM_StorageManager_FlashCopy
About array-specific methods vs array-independent methods
Some snapshot methods are disk array independent. These methods are described in the following topic:
See
“Software-based snapshot methods”
on page 159.
For these methods, the client platform or the presence of a particular file system or volume manager might determine or limit selection of the snapshot method.
However, if the client data resides on an array, the make of the array does not determine the choice of the snapshot method.
The array methods in the current chapter, however, are each written for a particular model of disk array. For instance, the EMC_CLARiiON_SnapView_Clone method is designed for the EMC CLARiiON CX 300/500 and CX3 series arrays.
Regardless of client platform or storage stack, you cannot use
EMC_CLARiiON_SnapView_ Clone on a non-EMC array, or even on a different model of EMC array.
For an up-to-date list of supported disk arrays, refer to the NetBackup Snapshot
Client Configuration document. This document may be accessed from the following link: http://www.symantec.com/docs/TECH51377
Configuration of snapshot methods for disk arrays
About the new disk array snapshot methods
183
Advantages of the new array-specific methods
The snapshot methods that are described in this chapter offer advantages over software-based methods. Note the following when choosing between the array-specific methods in this chapter and the snapshot methods that are described in other chapters of this guide.
The new array-specific methods enable a variety of snapshot capabilities that the disk arrays provide:
■ All data movement is within the array, saving network bandwidth.
■ The Instant Recovery feature of NetBackup Snapshot Client.
See
on page 25.
The legacy array-specific methods (TimeFinder, ShadowImage, BusinessCopy) do not support Instant Recovery.
■ Clone and copy-on-write snapshot methods, in addition to full mirror methods
(depending on the array). The legacy array methods support only mirrors.
■ Automatic provisioning (LUN masking) of snapshot devices on the NetBackup clients. With the legacy array-specific methods, a mirror device had to be manually provisioned before it can be used in a backup. That preconfiguration step is no longer necessary.
About types of disk array methods
Two types of snapshots are designed for each supported disk array. One type creates a full-sized, fully allocated copy (a clone or mirror). Another type uses a copy-on-write system, which is not a full copy and saves disk space. The methods go by various names, depending on the disk array vendor.
All methods are listed in the following topic.
See
“Disk array methods at a glance”
on page 185.
Note: Some disk array vendors use the term snapshot to refer to a certain kind of point-in-time copy made by the array. In other chapters of this guide, however, snapshot refers more generally to all kinds of point-in-time copies, disk-array based or otherwise. Refer to your array documentation for the definition of array vendor terminology.
Important disk array method notes and restrictions
Note the following:
184 Configuration of snapshot methods for disk arrays
About the new disk array snapshot methods
■ The disk array methods support the Veritas File System (VxFS). With a few exceptions, these methods do not support software-based volume managers such as the Veritas Volume Manager (VxVM) or any native Linux or Solaris volume managers. If your client data is configured in Veritas VxVM volumes, use either the legacy array-specific methods for UNIX clients (TimeFinder,
ShadowImage, BusinessCopy) or a software-based snapshot method such as
VxVM or FlashSnap.
Note: The following array methods support Veritas Volume Manager (VxVM) volumes: Hitachi_CopyOnWrite and Hitachi_ShadowImage. The
IBM_DiskStorage_FlashCopy method (on the IBM DS6000) supports VxVM on the AIX platform.
■ Use caution with Instant Recovery rollback. An Instant Recovery point-in-time rollback overwrites the entire LUN (source disk) with the contents of the snapshot or mirror disk. If you have multiple file systems or multiple partitions configured on the hardware array LUN (the source disk), one or more of those file systems or partitions sharing the snapshot disk or mirror disk may have older data that you do not want to write back to the source. When the rollback takes place, any older data on the snapshot disk or mirror disk replaces the newer data on the source.
■ In a clustered environment, Instant Recovery point-in-time rollback is not supported.
■ Except for required preconfiguration as explained in this chapter, do not perform manual operations on any snapshot resources that NetBackup uses.
After the preconfiguration is completed as explained in this chapter, NetBackup automatically manages the required LUNs, snapshots, clones, and mirrors.
Warning: If you make other changes to the snapshot resources, the NetBackup catalog may be invalidated. For instance, restores may fail from backups consisting of the snapshots that have been deleted outside the view of
NetBackup.
For example, DO NOT do the following:
■ Do not remove a snapshot resource that NetBackup created.
■ Do not create a snapshot resource in a storage group.
■ Do not change the state of a snapshot resource, such as by manually resynchronizing it.
Configuration of snapshot methods for disk arrays
About the new disk array snapshot methods
185
■ You should not use array device targets in more than one policy. If you want to reuse devices after destroying an old policy, you need to manually expire the backup images, which exist for that policy.
Disk array methods at a glance
is an alphabetical listing of the disk array snapshot methods.
For up-to-date information on the arrays and on supported software versions, refer to the NetBackup Snapshot Client Configuration document. This document may be accessed from the following link: http://www.symantec.com/docs/TECH51377
Table 10-1 Snapshot methods at a glance
Snapshot method Description and notes
EMC_CLARiiON_Snapview_Clone For full-volume mirror snapshots with EMC
CLARiiON disk arrays with Navisphere. (An EMC
CLARiiON clone is actually a full-volume copy mirror, like a Symmetrix BCV.)
See
on page 198.
EMC_CLARiiON_SnapView_Snapshot For space-optimized, copy-on-write snapshots with EMC CLARiiON disk arrays with Navisphere.
See
on page 198.
EMC_TimeFinder_Clone
EMC_TimeFinder_Mirror
EMC_TimeFinder_Snap
Hitachi_CopyOnWrite
For full-volume copy (clone) snapshots with EMC disk arrays with Solutions Enabler.
See
on page 212.
For full-volume copy (mirror) snapshots with EMC disk arrays with Solutions Enabler.
See
on page 212.
For space-optimized, copy-on-write snapshots with EMC disk arrays with Solutions Enabler.
See
on page 212.
For space-optimized, copy-on-write snapshots with Hitachi SMS/WMS/AMS, USP/NSC, and
USP-V/VM series of arrays.
See
“About Hitachi SMS/WMS/AMS, USP/NSC,
on page 236.
186 Configuration of snapshot methods for disk arrays
About the new disk array snapshot methods
Table 10-1 Snapshot methods at a glance (continued)
Snapshot method
Hitachi_ShadowImage
HP_EVA_Snapclone
Description and notes
For full-volume copy (mirror) snapshots with
Hitachi SMS/WMS/AMS, USP/NSC, and
USP-V/VM series of arrays.
See
“About Hitachi SMS/WMS/AMS, USP/NSC,
on page 236.
For full-volume copy (clone) snapshots with
Hewlett-Packard EVA disk arrays with
CommandView SSSU.
Note: this method is the only EVA disk array method that supports Instant Recovery.
HP_EVA_Snapshot
HP_EVA_Vsnap
IBM_DiskStorage_FlashCopy
IBM_StorageManager_FlashCopy
HP_XP_BusinessCopy
HP_XP_Snapshot
See
on page 218.
For space-optimized, fully allocated copy-on-write snapshots with Hewlett-Packard EVA disk arrays with CommandView SSSU.
See
on page 218.
For space-optimized, on-demand copy-on-write snapshots with Hewlett-Packard EVA disk arrays with CommandView SSSU.
See
on page 218.
For full-volume copy (clone) snapshots on IBM
DS6000 and DS8000 series of arrays with DSCLI version.
See
“About IBM DS6000 and DS8000 arrays”
on page 225.
For full-volume copy (clone) snapshots on the
IBM DS4000 series of arrays (excluding 4100), with SMcli.
See
on page 231.
For mirror-based snapshots with HP-XP arrays
See
on page 240.
For COW-based snapshots with HP-XP arrays
See
on page 240.
Configuration of snapshot methods for disk arrays
Disk array configuration tasks
187
Table 10-1
Snapshot method
OST_FIM
Snapshot methods at a glance (continued)
Description and notes
The name of the snapshot method that is selected in a policy configured for snapshot replication using Replication Director. The name represents
OpenStorage Frozen Image Method.
Refer to the Symantec NetBackup™Replication
Director Solutions Guide for more details.
Disk array configuration tasks
Note the following tasks.
Configuration tasks for the array administrator
Before you configure a backup, your array administrator or network administrator must do several tasks. Assistance with these tasks may be found in your array documentation or Windows documentation.
The array administrator must do the following tasks:
■ Install the disk array and its software (such as Web) interface, including appropriate licenses.
■ Install supported HBAs on the NetBackup primary client and alternate clients.
■ If not already done, zone the client HBAs through the Fibre Channel switch, so the array is visible to the primary client and any alternate clients.
■ Register your NetBackup primary client and any alternate clients with the array.
■ Install NetBackup and array vendor snapshot management software on the
NetBackup primary client and any alternate clients.
■ Configure source and snapshot devices on the array (such as LUNs).
■ For Windows 2003 primary clients and any alternate clients, install the appropriate VSS provider for your array.
Configuration tasks for the NetBackup administrator
The NetBackup administrator must do the following tasks:
■ If necessary, configure target devices on the array.
See the topic for your array.
188 Configuration of snapshot methods for disk arrays
Disk array configuration tasks
See
“Initial configuration of certain arrays”
on page 194.
■ For certain arrays, configure NetBackup disk array host credentials, which are required to access the array snapshot management software.
See the topic for your array.
EMC CLARiiON
EMC Symmetrix
HP EVA
IBM DS6000 and DS8000
IBM DS4000
Hitachi SMS/WMS/AMS, USP/NSC,
USP-V/VM
HP-XP
See
“Configuring NetBackup to access the
on page 202.
See
“About configuring NetBackup to access the Symmetrix array”
on page 214.
See
“Configuring NetBackup to access the
on page 223.
See
“Configuring NetBackup to access the
on page 225.
See
“Configuring NetBackup to access the
on page 234.
See
NetBackup and the Hitachi array”
on page 237.
See
“Determining if the HP-XP command devices are visible”
on page 242.
■ Create a NetBackup Snapshot Client policy for the array.
See the topic on the NetBackup policy for your array.
EMC CLARiiON
EMC Symmetrix
HP EVA
IBM DS6000 and DS8000
IBM DS4000
See
“Configuring a NetBackup policy for a
on page 211.
See
on page 217.
See
“Configuring a NetBackup policy for an HP EVA array method”
on page 224.
See
“Configuring a NetBackup policy for
on page 230.
See
“Configuring a NetBackup policy for
on page 235.
Configuration of snapshot methods for disk arrays
Disk array configuration tasks
189
Hitachi SMS/WMS/AMS, USP/NSC,
USP-V/VM
HP-XP
See
“Configuring a NetBackup policy for
on page 239.
See
“Configuring a NetBackup policy for
on page 242.
Disk array configuration tasks diagram
The following diagram shows the major components and tasks that are required for a snapshot backup of a disk array. Some of these tasks must be performed by the array administrator.
Figure 10-1
NetBackup master server:
Define
NetBackup policy
Components for backup of disk array on Fibre Channel
NetBackup media server
LAN
Zone the client
HBAs; see your hardware documentation
SAN
Fibre Channel SAN
HBA HBA
Disk array:
Configure virtual devices (LUNs) on array; see your array documentation.
Disk array host: Configure
NetBackup login credentials for this host
*
*
Some arrays do not have a separate front-end host; NetBackup credentials must be defined for the array itself. The array validates the NetBackup credentials.
NetBackup client: Install
HBA and array
CLI software; see your hardware documentation
NetBackup alternate client
(optional)
190 Configuration of snapshot methods for disk arrays
OS-specific configuration tasks
OS-specific configuration tasks
This topic describes the configuration tasks that are related to the NetBackup client host operating system.
About dynamic multi-pathing
In a SAN fabric, it is advantageous (for redundancy reasons) for multiple pathways to exist from a host computer to a device on a disk array. The purpose of dynamic multi-pathing software is the following:
■ Manage these pathways so that only one is in use at a time
■ Switch to another pathway if the one in use fails
Snapshot Client supports EMC PowerPath dynamic multi-pathing software on
Solaris and Windows. Due to limitations that prevent the dynamic importing of devices, PowerPath is not supported on Linux.
For certain arrays, Snapshot Client works in a multipath configuration with or without PowerPath installed, because all visible device paths provide equal access to the array device. EMC Symmetrix and HP-EVA arrays behave in this manner.
For other arrays, if multiple device paths exist to an array device, Snapshot Client can use only one of those paths. In this case, PowerPath must be used to ensure that Snapshot Client always uses the active device path. EMC CLARiiON behaves in this manner. If PowerPath is not in use and the disk array is EMC CLARiiON, the Fibre Channel switch must be configured so that only one path is zoned to the
NetBackup client.
HBA configuration
The supported HBAs are Emulex and QLogic. The JNI HBA is not supported.
HBA persistent target bindings
Persistent target bindings must be configured for every HBA. Without persistent bindings, the array’s target number cannot be guaranteed on the host. A persistent device target number ensures that snapshots appear at the same device location if a NetBackup client host restarts. Refer to your HBA vendor documentation for help configuring persistent bindings.
Note: Persistent target bindings are not needed if you use Leadville drivers on
Solaris.
Configuration of snapshot methods for disk arrays
OS-specific configuration tasks
191
About Solaris sd.conf file
The
/kernel/drv/sd.conf
file must have sufficient entries to allow for the dynamic import of snapshot devices. Snapshot devices are created when the backup starts, and must be made visible on the NetBackup client without restarting the operating system. Entries should be added to the sd.conf
file for the persistent target numbers that were configured for the HBA.
Note: The sd.conf
file does not have to be modified if you use Leadville drivers.
Symantec recommends that you add LUNs 0-15 for all disk array targets on which snapshots are to be created. This creates 16 host-side LUNs on each target that can be used for importing the snapshots (clones, mirrors, and copy-on-write snapshots) required for backups. If 16 host-side LUNs are not enough for a particular disk array target, add more LUNs for that target. Note that snapshots are imported to a NetBackup client in sequential order starting with the lowest unused host-side LUN number. The host-side LUN number pool is managed on the disk array. The disk array cannot determine which host-side LUN numbers have been configured in sd.conf. The array can only determine which host-side
LUN number it has not yet assigned to the host. If the array adds a device at a host-side LUN number that has not been configured in sd.conf
, that device is not visible on the host. Also, if alternate client backups are being used, be sure to properly configure sd.conf
on the alternate client.
You must restart after modifying sd.conf
.
Symmetrix arrays pre-assign host-side LUN numbers (that is, the LUN numbers are not set at the time the device is imported). These pre-selected LUN numbers must be entered into sd.conf
for the Symmetrix target number.
Note: If you use EMC Control Center interface (ECC) to determine Symmetrix host-side LUN numbers, note that ECC shows host-side LUN numbers in hexadecimal format. Since the LUN entries in sd.conf
must be in decimal format, convert the hexadecimal value to decimal before adding it to sd.conf
.
If the Symmetrix array was persistently bound at target 5, and the host-side LUN numbers of the Symmetrix devices are 65, 66, 67, then the following entries should be added to sd.conf
.
name="sd" class="scsi" target=5 lun=65; name="sd" class="scsi" target=5 lun=66; name="sd" class="scsi" target=5 lun=67;
192 Configuration of snapshot methods for disk arrays
OS-specific configuration tasks
Solaris sd.conf file (Hitachi arrays only)
Before running backups, you must configure a sufficient number of static devices
(array LUNs) in the
/kernel/drv/sd.conf
file on the client (and any alternate client) to accommodate the number of snapshot devices that backups require.
Note: Hitachi arrays do not support dynamic import of snapshot devices.
Linux modprobe.conf file
The
/etc/modprobe.conf
file must be set to allow the Fibre Channel HBA driver to scan for LUNs greater than 0. Make sure the following line (or something similar) appears in the modprobe.conf
file: options scsi_mod max_luns=255
If the line is not present, add it to the modprobe.conf
and enter the following:
#mv /boot/initrd-linux_kernel_version.img
/boot/initrd-linux_kernel_version.img.bak
#mkinitrd -v /boot/initrd-linux_kernel_version.img
linux_kernel_version where the linux_kernel_version is the value that is returned from uname -r
(for example, 2.6.9-34.ELsmp).
Verifying NetBackup client access, zoning, and LUN masking
You can use the nbfirescan command to verify that the NetBackup clients have access to the array devices and that the arrays are properly zoned and LUNs are
LUN masked. Note that nbfirescan only displays LUNs that have actually been
LUN masked to the host.
To verify NetBackup client access, zoning, and LUN masking
◆ Enter the following on the client:
■ UNIX
/usr/openv/netbackup/bin/nbfirescan
■ Windows
\Program Files\Common Files\Symantec
Shared\VxFI\4\Bin\nbfirescan.exe
Configuration of snapshot methods for disk arrays
OS-specific configuration tasks
193
This command queries the host’s SCSI bus for all the SCSI (or Fibre) attached devices that are visible.
Note the following regarding CLARiiON:
■ If there are LUNs in the client’s CLARiiON storage group, the LUNs are included in the output.
■ If there are no LUNs visible but the array is zoned to allow the host to see it, the output includes the entry DGC LUNZ. This entry is a special LUN that the
CLARiiON uses for communication between the client and the array. The LUNZ entry is replaced by another disk entry as soon as one is put in the storage group which has been presented to the client.
Example Solaris output, followed by a description:
DevicePath Vendor Product ID EnclosureId DeviceId [Ctl,Bus,Tgt,Lun]
---------------------------------------------------------------------------------
/dev/rdsk/c3t4d57s2 EMC
/dev/rdsk/c3t6d10s2 HP
SYMMETRIX
HSV200
000187910258 013C
5000-1FE1-5007-0020
[00,00,00,00]
6005-08B4-0010-5F49-0000-5000-408F-0000 [00,00,00,00]
Note: The last line of output is wrapped.
DevicePath
EnclosureId
DeviceId
Ctl,Bus,Tgt,Lun
Represents the actual access point for the device as it exists on the client host.
Unique for each physical disk array.
Unique for a physical disk or virtual disk in an enclosure. The
Enclosure ID/DeviceID pair constitutes a client host-independent designation of a particular physical or virtual disk within a disk array.
Controller, bus, target, and LUN numbers are the elements that designate a particular physical or virtual disk from the perspective of the client host computer.
Example Linux output (wrapped to fit page):
DevicePath Vendor Product ID EnclosureId DeviceId [Ctl,Bus,Tgt,Lun]
---------------------------------------------------------------------------------
/dev/sdb DGC RAID 5
35:EC:DA:11 [01,00,00,00]
APM00050602951 60:06:01:60:83:B0:11:00:4D:C4:8A:1D:
/dev/sdc DGC RAID 5
35:EC:DA:11 [01,00,00,01]
APM00050602951 60:06:01:60:83:B0:11:00:4C:C4:8A:1D:
194 Configuration of snapshot methods for disk arrays
About VSS configuration (Windows)
/dev/sdd DGC RAID 5
35:EC:DA:11 [01,00,00,02]
/dev/sde DGC RAID 5
35:EC:DA:11 [01,00,00,03]
/dev/sdf HP HSV200
[01,00,01,01]
/dev/sdg HP HSV200
[01,00,01,02]
APM00050602951
APM00050602951
60:06:01:60:83:B0:11:00:4B:C4:8A:1D:
60:06:01:60:83:B0:11:00:4A:C4:8A:1D:
5000-1FE1-5007-0020 6005-08B4-0010-5F49-0000-5000-22F8-0000
5000-1FE1-5007-0020 6005-08B4-0010-5F49-0000-5000-22FF-0000
■ Most of the output lines are wrapped.
■ DGC designates a CLARiiON device.
About VSS configuration (Windows)
On Windows clients, VSS is used during backups to create snapshots on disk arrays. Certain preconfiguration steps may be required as described in these sections.
Note on NetBackup array credentials
For certain disk arrays, you must supply NetBackup with logon credentials so that it can access the array. See the appropriate section in this chapter to configure
NetBackup to access the array.
Note: For backup of a disk array using the Windows VSS snapshot method with
Instant Recovery, be sure to configure NetBackup disk array credentials (if required by the array) before you run the backup. A Point in Time Rollback fails if NetBackup did not have credentials to access the array during the backup.
Initial configuration of certain arrays
Certain arrays require some initial configuration to use the VSS method for a backup.
CLARiiON No VSS-related preconfiguration is needed, except installation of the required array software and the VSS provider.
See
“Symantec support for VSS Snapshot and EMC
on page 199.
Configuration of snapshot methods for disk arrays
About VSS configuration (Windows)
195
HP EVA
Symmetrix
EMC TimeFinder Snap
No VSS-related preconfiguration is needed, except installation of the required array software and the VSS provider. For any other configuration requirements, see the section in this chapter for your array.
You must associate the source device in the array with the target device(s) that are to be used for the differential
(copy-on-write) or plex-based (clone or mirror) backup.
Note: For Symmetrix arrays, NetBackup supports VSS with differential (copy-on-write) backup but not plex-based (clone or mirror) backup.
See
“Creating EMC disk groups for VSS differential snapshots that use EMC TimeFinder Snap”
on page 195.
See
“Verifying that VSS can make a snapshot”
on page 196.
See
“Testing the EMC TimeFinder Snap backup”
on page 198.
Creating EMC disk groups for VSS differential snapshots that use EMC TimeFinder Snap
Use the following procedure.
To create EMC disk groups for VSS differential snapshots that use EMC TimeFinder
Snap
1 Create a disk group to contain any number of primary and secondary disks.
symdg create nbfim_test
Creates a disk group named nbfim_test.
2 Add primary disks to the disk group.
symld -g nbfim_test add dev 02A
Adds a primary disk 02A to disk group nbfim_test.
3 Add a VDEV disk to the disk group.
symld -g nbfim_test add dev 08C -vdev
Adds the VDEV disk 08C to the nbfim_test disk group.
When these commands are successfully entered, NetBackup can make snapshot backups with primary device 02A and its target VDEV 08C.
196 Configuration of snapshot methods for disk arrays
About VSS configuration (Windows)
Verifying that VSS can make a snapshot
Before you finish preconfiguration or run a backup with the Windows VSS method, verify that the Volume Shadow Copy Service can make and delete a snapshot on the array.
The command that is used in the following procedure is available with Microsoft
Volume Shadow Copy SDK 7.2.
On the NetBackup client, you can use the commands in the following procedure.
Note: If these commands do not succeed, consult your Windows documentation or your array administrator.
To verify that VSS can make or delete a snapshot
1 To create a snapshot, enter one of the following commands .
■ For a differential (copy-on-write) snapshot: vshadow.exe -ad -nw -p source_drive
■ For a plex (clone or mirror) snapshot:
Configuration of snapshot methods for disk arrays
About VSS configuration (Windows)
197 vshadow.exe -ap -nw -p source_drive
2 To display information on all existing snapshots on the client, enter the following command: vshadow.exe -q
Example output:
VSHADOW.EXE 2.2 - Volume Shadow Copy sample client
Copyright ©) 2005 Microsoft Corporation. All rights reserved.
(Option: Query all shadow copies)
- Setting the VSS context to: 0xffffffff
Querying all shadow copies in the system ...
* SNAPSHOT ID = {ae445cc3-e508-4052-b0f6-a5f02cf85f1e} ...
- Shadow copy Set: {6665f5f7-6468-4a22-bd73-29ef8a30a760}
- Original count of shadow copies = 1
- Original Volume name:
\\?\Volume{0db3bc15-53b1-4d63-94dc-7c7d28b172cb}\ [K:\]
- Creation Time: 4/10/2007 2:02:13 PM
- Shadow copy device name:
\\?\Volume{55226978-3131-4a12-8246-97ace27cf976}
- Originating machine: oil.fun.com
- Service machine: oil.fun.com
- Not Exposed
- Provider id: {21e5ab69-9685-4664-a5b2-4ca42bddb153}
- Attributes: No_Auto_Release Persistent Hardware
No_Writers
Plex
3 To delete snapshots, do the following:
■ Look in the vshadow.exe -q command output for the
Shadow copy Set
ID of a snapshot that you created above.
■ Enter the following command to delete a particular snapshot: vshadow.exe -dx = {Shadow_copy_set_ID}
■ Enter the following command to delete all snapshots on the client: vshadow.exe -da
198 Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
Testing the EMC TimeFinder Snap backup
After you complete the Symmetrix configuration steps as described in this chapter and run a backup, you can verify that the snapshot was successful.
To test the EMC TimeFinder Snap backup
◆ Enter the following command to verify that the snapshot was successful.
symsnap -g nbfim_test query -multi
The
-multi option shows multiple snapshots.
For example:
C:\Program Files\EMC\SYMCLI\bin\symsnap -g dmx-5D query -multi where dmx-5D is the name of the Symmetrix device group.
Sample output:
Device Group (DG) Name: dmx-5D
DG's Type : REGULAR
DG's Symmetrix ID : 000187910258
Source Device Target Device State Copy
------------------------- ------------------- ---------- ------------ ----
Protected
Logical Sym Tracks Logical Sym
Changed
G Tracks SRC <=> TGT (%)
------------------------- ------------------- ---------- ------------ ----
DEV001 005D 273108 VDEV001 01A8
276208 VDEV002
X
01A9 X
CopyOnWrite 0
2 CopyOnWrite 0
Total
Track(s)
MB(s)
--------
552417
17263.0
----------
3
0.1
If the SRC <=> TGT value reads CopyOnWrite , the snapshot was created successfully.
About EMC CLARiiON arrays
The following sections include background information and configuration tasks for NetBackup Snapshot Client backups using EMC CLARiiON arrays. These tasks must be completed before you run a backup.
Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
199
EMC CLARiiON software requirements for UNIX
shows the required EMC software.
For software versions used in test configurations, see the NetBackup Snapshot
Client Configuration document at: http://www.symantec.com/docs/TECH51377
Table 10-2 Software that is required for EMC CLARiiON
Software
Navisphere Secure CLI
Navisphere Agent
CLARiiON SnapView software
CLARiiON FLARE operating environment
Where to install
NetBackup clients
NetBackup clients
EMC disk array
EMC disk array
Symantec support for VSS Snapshot and EMC CLARiiON
Symantec has an open support policy for VSS Snapshot for NetBackup Snapshot
Client. If a vendor supports a VSS provider for a Windows platform, Symantec provides support for local snapshot, alternate client, FlashBackup local snapshot, and FlashBackup alternate client methods. To use a CLARiiON disk array with
VSS, contact EMC Corporation for the required software and versions. EMC supplies this software as a bundle, to ensure that the software components are at the right level and function correctly.
Note that the open support policy for VSS providers is not applicable to Instant
Recovery. To use VSS along with the NetBackup Instant Recovery feature, refer to the NetBackup 7.x Snapshot Client Compatibility List for the components that
NetBackup supports for Instant Recovery with the array. The compatibility list is available at the following URL: http://www.symantec.com/docs/TECH126901
Diagram of installed software for EMC CLARiiON
shows the software components on the NetBackup clients and the
CLARiiON array for UNIX, and indicates the control function of each.
200 Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
UNIX client
Figure 10-2
NetBackup Snapshot
Client
Create snapshot
Restore data
Navisphere Secure
CLI
Software on NetBackup clients and CLARiiON array
Create snapshot or restore
Navisphere Agent
Register host with array
EMC CLARiiON array
FLARE OS
Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
201
Verifying connectivity from client to array
NetBackup communicates with the array by means of the EMC Navisphere Secure
CLI. To verify that the CLI is installed and that NetBackup can communicate with the EMC CLARiiON array, enter the following command on each NetBackup client.
Note that if a Navisphere security file has been created, the user name, password, and scope do not have to be supplied with the command.
To verify connectivity from client to array
1 Enter the following:
■ On UNIX:
/opt/Navisphere/bin/naviseccli –h CLARiiON_hostname -user
array_admin_username -password array_admin_password -scope 0 getagent
■ On Windows:
Program Files\EMC\Navisphere CLI\naviseccli –h CLARiiON_hostname
-user array_admin_username -password password -scope 0 getagent
Sample output from this command:
Agent Rev:
Name:
Desc:
Node:
Physical Node:
Signature:
Peer Signature:
Revision:
SCSI Id:
Model:
Model Type:
Prom Rev:
SP Memory:
Serial No:
SP Identifier:
Cabinet:
6.19.1 (2.6)
K10
A-APM041147024
K10
1218092
1099522
2.19.500.5.027
0
CX500
Rackmount
3.60.00
2048
APM041147024
A
DPE2
If the command fails, you must address the problem before you do any further array configuration.
This problem could be due to the following:
202 Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
■ The Navisphere Secure CLI or other array interface is not installed.
■ The installed Navisphere Secure CLI is not a supported version.
See
on page 199.
■ The array credentials are invalid.
2 For further troubleshooting information, consult your array documentation.
About resolving host names on the network
All NetBackup clients to be used with Snapshot Client must be resolvable by means of your network naming service (such as DNS). NetBackup uses the network naming service to look up the client’s host name, its fully qualified domain name, and IP address. NetBackup then looks for any of those three in a CLARiiON storage group when attempting to do LUN masking.
Configuring NetBackup to access the CLARiiON array
You must supply logon credentials that allow the NetBackup client to access each storage processor on each EMC CLARiiON array.
IMPORTANT: For single path configurations, you must add credentials for the
CLARiiON storage processor that owns the source LUNs and any clone LUNs. For multipath configurations, you must add credentials for both storage processor A and storage processor B. The storage processor that owns the LUN may be changed by the multipath software. (For single path configurations, all CLARiiON LUNs must be owned by only one storage processor.)
To configure NetBackup to access the CLARiiON array
1 In the NetBackup Administration Console, click the Media and Device
Management > Credentials > Disk Array Hosts node in the NetBackup
Administration Console.
2 Right-click in the Disk Array Hosts pane and select New Disk Array Host.
3 Enter the host name of the EMC CLARiiON array.
4 Select EMC CLARiiON in the Disk Array Host Type pull-down menu.
5 Enter the user name and password for the storage processor.
6 Clear (uncheck) the Connect using port number checkbox.
About using a local scope CLARiiON administrator account
By default, NetBackup uses a global scope CLARiiON administrator account, not a local scope account. To specify a local scope CLARiiON administrator account,
Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
203 you must use the Navisphere security file to supply the account information (see the following note, however). The Navisphere security file contains a user name, password, and scope for the CLARiiON administrator. The CLARiiON snapshot provider uses the Navisphere security file if the file exists. To create the security file, see the EMC Navisphere documentation.
Note: You must also enter credentials by means of the Disk Array Hosts dialog box in the NetBackup Administration Console. The disk array host name is not provided in the Navisphere security file.
Adding clients to a CLARiiON storage group
All NetBackup primary clients and any alternate clients must exist in a CLARiiON storage group. NetBackup does not automatically add clients to a CLARiiON storage group.
Warning: Symantec strongly recommends that every NetBackup client be given its own CLARiiON storage group on the array. Data corruption could result if more than one client (host) exists in a single storage group. If it is necessary to have multiple hosts in a single storage group, you must make certain that only one host in the storage group is actually using the device at any given time. (Only one host should mount the disk.) A Windows host may actually write to a LUN masked device even if the device is not mounted. Therefore, a Windows host should always be in its own storage group.
To add clients to a CLARiiON storage group
1 Register your clients (hosts) with the array.
2 Create storage groups.
3 Add the NetBackup primary and any alternate clients to the storage groups.
For more detail, see your array administrator or array documentation.
Configuring for EMC_CLARiiON_SnapView_Clone
The following must be completed before NetBackup can use the clone capabilities of the CLARiiON array. The following steps are described in the topics that follow.
204 Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
Table 10-3
Step
Step 1
Step 2
Step 3
Step 4
Step 5
Configuration process for EMC_CLARiiON_SnapView_Clone
Action Related topic
Array administrator creates clone private LUNs.
See
“Creating a clone private LUN with the EMC Navisphere Web interface”
on page 205.
Array administrator creates a clone group and selects a LUN as source.
See
“Creating a clone group and select a LUN as source”
on page 205.
Array administrator adds clone
LUNs to the clone group.
See
“Adding clone LUNs to the clone group”
on page 206.
Array administrator supplies source and target devices.
See
“Obtaining the device identifier for each source and clone LUN”
on page 208.
See
EMC_CLARiiON_SnapView_Snapshot”
on page 209.
See
“Configuring a reserved LUN pool for the storage processors”
on page 210.
NetBackup administrator configures a NetBackup policy for the array, using the device that are identifiers supplied by the array administrator.
See
“Configuring a NetBackup policy for a CLARiiON array method”
on page 211.
Note: For Windows clients and the VSS method, you must synchronize the clone with its source.
Note: These steps are separate from those taken by NetBackup to create the backup.
When the backup begins, NetBackup synchronizes the clones with the source (if necessary) and splits (fractures) the clones to make them available for the backup.
For more information on the EMC array terminology in this section, see your EMC
CLARiiON documentation.
Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
205
Creating a clone private LUN with the EMC Navisphere Web interface
You must configure a clone private LUN for each CLARiiON storage processor that owns a clone source LUN. Clone private LUNs store the portions of the client’s data that incoming write requests change while the clone is in use. Clone private
LUNs are used while a clone LUN is fractured and when a synchronization occurs.
A clone private LUN can be any bound LUN that is at least 250,000 blocks in size.
To create a clone private LUN with the EMC Navisphere Web interface
1 Right-click the array name.
2 Right-click the Snapview node and select Clone Feature Properties.
3 Choose the LUNs you want to label as Clone Private LUNs.
Choose a clone private LUN for each storage processor that contains clone source LUNs. (You must know which storage processor owns a given LUN.)
Only one clone private LUN is required per storage processor. You can add more clone private LUNs later if more space is needed.
Creating a clone group and select a LUN as source
Use the following procedure to create a clone group and select a LUN as source.
206 Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
To create a clone group and select a LUN as source
1 In the EMC Navisphere Web interface, right-click the Snapview node and select Create Clone Group.
2 Enter a name for the clone group.
3 Choose the source LUN to be cloned (the source LUN to associate with this group). This LUN contains the data that is copied to the clones.
Adding clone LUNs to the clone group
Use the following procedure.
Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
207
To add clone LUNs to the clone group
1 In the EMC Navisphere Web interface, on the SnapView > Clones node, right-click the name of the clone group and select Add Clone.
2 Select a LUN from the list to be added to the clone group.
Accept the defaults for Advanced Parameters, Recovery Policy, and
Synchronization Rate.
■ Do not choose a LUN that contains valuable data. Any data on the LUN is overwritten by this procedure.
■ The number of clones to add depends on how many point-in-time copies of the source LUN you want to retain at one time. The limit is 8 clones per source LUN.
This value should match the Maximum Snapshots setting in the
EMC_CLARiiON_Snapview_Clone configuration parameters in the
Snapshot Options dialog in a NetBackup policy.
See
on page 106.
3 When you click Apply, Navisphere begins to copy data from the source LUN to the LUN you have selected, creating a clone LUN.
Any previous data on the clone LUN is lost.
208 Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
Obtaining the device identifier for each source and clone LUN
The NetBackup policy requires entry of the array’s Unique ID. If your array administrator provided LUN numbers for the devices, you must convert those
LUN numbers into Unique IDs for entry in the NetBackup policy Snapshot
Resources pane. You can obtain the LUN Unique IDs in either of two ways, as follows.
To obtain the device identifier for each source and clone LUN
1 Enter the following command on the NetBackup client:
/opt/Navisphere/bin/naviseccli -address CLARiiON_hostname -user
array_admin_username -password password -scope 0 getlun
lun_number -uid
2 Note the exact UID string that this command returns. This UID is the unique
ID of the LUN.
For example, to obtain the unique ID of LUN 67, enter:
/opt/Navisphere/bin/naviseccli -address CLARiiON_hostname -user
array_admin_username -password password -scope 0 getlun 67
-uid
Example output:
UID: 60:06:01:60:C8:26:12:00:4F:AE:30:13:C4:11:DB:11
3 To obtain the number of the LUN to use on the naviseccli command, find the clone group and examine the LUN list.
4 Copy the unique ID into the NetBackup policy, as follows:
■ If the LUN specified on the naviseccli command is the source LUN for the clone group, copy the unique ID into the Source Device field of the Add
Snapshot Resource dialog box of the NetBackup policy. Help is available for that dialog box.
See
“Configuring a policy using EMC_CLARiiON_Snapview_Clone method”
on page 211.
■ If the LUN specified on the naviseccli command is a clone LUN, copy the unique ID into the Snapshot Device(s) field.
Unique ID field
Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
209
To use the Navisphere Web interface
1 To find the unique ID of a LUN, right-click the LUN in the Navisphere Web interface and select Properties.
2 See the Unique ID field.
As of this writing, you cannot copy and paste the Unique ID from the
Navisphere web interface. Use the naviseccli command to copy and paste the
ID.
Storage processor
About configuration for EMC_CLARiiON_SnapView_Snapshot
You must configure a reserved LUN pool for each storage processor that owns a source LUN for which you want to create a SnapView snapshot. (Starting at FLARE version x.24, one combined reserved LUN pool exists for both storage processors.)
The reserved LUN pool stores the portions of the client’s data that incoming write requests change while the snapshot is active.
Note the following before you configure a reserved LUN pool.
■ The reserved LUN pool must contain at least one LUN for each source LUN that is the subject of (participates in) the snapshot. Any available LUN can be
210 Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays added to the reserved LUN pool if the LUN is owned by the storage processor that owns the source LUN.
■ LUNs in the reserved LUN pool are private LUNs, which cannot belong to a storage group. The storage processor manages its reserved LUN pool and automatically assigns one or more private LUNs to a source LUN. This assignment is based on how much snapshot activity takes place in the source
LUN. This activity can result from one busy snapshot or multiple snapshots.
■ While the snapshot is active, client write activity on the source consumes more space in the reserved LUN pool. Adding more LUNs to the reserved LUN pool increases the size of the reserved LUN pool. The storage processor automatically uses a LUN if one is needed.
■ All snapshots share the reserved LUN pool. If two snapshots are active on two different source LUNs, the reserved LUN pool must contain at least two private
LUNs. If both snapshots are of the same source LUN, the snapshots share the same private LUN (or LUNs) in the reserved LUN pool.
Configuring a reserved LUN pool for the storage processors
In the EMC Navisphere Web interface, do the following.
To configure a reserved LUN pool for the storage processors
1 Under the node for your array, right-click Reserved LUN Pool and choose
Configure.
2 In the Configure Reserved LUN Pool dialog box, under Available LUNS, select the LUNs to be added to the reserved LUN pool.
The reserved LUN pool must contain at least one LUN for each source LUN.
3 For FLARE versions before 2.24, click the Add to SPA LUN Pool for storage processor A or Add to SPB LUN Pool for storage processor B.
Check the properties of the source LUN to determine the storage processor that owns it.
4 Click Ok or Apply.
Each reserved LUN pool node shows how much space is free in the pool.
The amount of space that the reserve LUN pool requires depends on how many unique blocks change in the source LUN during the life of the snapshot.
If little space remains in an existing LUN pool, add new LUNs to the LUN pool.
Generally, the more snapshots that are created, the more space that is required in the reserved LUN pool. If the LUN pool space is used up, snapshots attached to backups may become inactive and future snapshot backups fail.
Configuration of snapshot methods for disk arrays
About EMC CLARiiON arrays
211
Configuring a NetBackup policy for a CLARiiON array method
General help for setting up a NetBackup policy is available.
See
“Configuring a Snapshot Client policy”
on page 56.
To configure a NetBackup policy for a CLARiiON array method
1 In the NetBackup Administration Console, click the Perform snapshot
backups box on the policy Attributes tab.
2 Click the Snapshot Client Options option to display the Snapshot Options dialog box.
3 In the Snapshot method pull-down list, select a CLARiiON method. To configure the method, see one of the following topics.
Configuring a policy using EMC_CLARiiON_Snapview_Clone method
In the Snapshot Options dialog box of the policy, you must specify the following information in the Snapshot Resources pane. NetBackup uses this information to correctly rotate through the clone LUNs when performing a SnapView clone backup. After all clone LUNs have been used in a backup, NetBackup automatically determines which clone is the oldest. NetBackup expires the oldest clone so that it can be reused for the current backup.
To configure a policy using EMC CLARiiON Snapview Clone method
1 Obtain the following source and clone LUN information:
■ Array serial number (in the EMC Navisphere Web interface, right-click the array name and select Properties).
■ Unique ID for the source LUN containing the primary data.
■ Unique ID for the target LUN(s) used for snapshots.
See
“Obtaining the device identifier for each source and clone LUN”
on page 208.
Or see your array administrator.
2 Copy and paste (or type) these values into the appropriate field of the
NetBackup policy’s Add Snapshot Resource dialog box, as explained below.
The policy Backup Selections specify a set of one or more source LUNs for which snapshots are taken for backup. For each source LUN that is specified in the policy Backup Selections list, the procedure is as follows.
See
“Configuring the EMC_CLARiiON_Snapview_Clone method”
on page 212.
212 Configuration of snapshot methods for disk arrays
About EMC Symmetrix arrays
Configuring the EMC_CLARiiON_Snapview_Clone method
Use the following procedure to configure the EMC_CLARiiON_Snapview_Clone method.
To configure the EMC_CLARiiON_Snapview_Clone method
1 After you select EMC_CLARiiON_Snapview_Clone on the Snapshot Options dialog box, click Add.
2 In the Add Snapshot Resource dialog box, enter the array’s serial number in the Array Serial # field.
3 Enter the unique ID for the source LUN in the Source Device field.
4 Enter the unique IDs for the clone LUNs in the Snapshot Device(s) field. To enter multiple IDs, place a semicolon between them.
For Instant Recovery backups, the Snapshot Device(s) entries determine where and in what order the snapshots are retained.
See
on page 105.
EMC_CLARiiON_Snapview_Snapshot method
In the Snapshot Options dialog box of the policy, you can set the Maximum
snapshots (Instant Recovery only) parameter for the
EMC_CLARiiON_Snapview_Snapshot method. The maximum value is 8.
See
on page 106.
Common CLARiiON array configuration problems
Note the following regarding the CLARiiON array:
Do not use the EMC_CLARiiON_Snapview_Clone method and the
EMC_CLARiiON_Snapview_Snapshot method to back up the same source LUN. If you attempt a rollback restore from a EMC_CLARiiON_Snapview_Snapshot snapshot, the restore fails if a clone associated with the source LUN is currently synchronized.
About EMC Symmetrix arrays
The following topics include background information and configuration tasks for snapshot backups using EMC Symmetrix arrays. These tasks must be completed before you run a backup.
Configuration of snapshot methods for disk arrays
About EMC Symmetrix arrays
213
EMC Symmetrix DMX software requirements
shows the required EMC software.
Table 10-4 Software that is required for EMC Symmetrix
Software Where to install
EMC Solutions Enabler NetBackup clients
Symmetrix Solutions
Enabler license
NetBackup clients
Versions
For versions used in test configurations, see Symantec NetBackup
Snapshot Client Configuration, at: http://www.symantec.com/docs/TECH51377
For versions used in test configurations, see Symantec NetBackup
Snapshot Client Configuration, at: http://www.symantec.com/docs/TECH51377
Support for EMC Symmetrix with Volume Shadow Copy Service
To use an EMC Symmetrix disk array with Volume Shadow Copy Service, contact
EMC Corporation for the required software and versions. EMC supplies this software as a bundle, to ensure that the software components are at the right level and function correctly.
Prerequisites for using EMC Symmetrix
Note the following prerequisites:
■ Your array administrator must allocate source and target devices before you create any NetBackup policies. See your array administrator for the device identifiers.
■ Your array administrator must allocate a Gatekeeper device and a VCMDB
(Volume Configuration Management database) for all of the NetBackup clients.
A VCMDB is a virtual LUN database that keeps track of which LUNs the client can see. A Gatekeeper is a small disk that the DMX uses to pass commands between the client and the array.
Configuring NetBackup clients to use EMC Symmetrix
Use the following procedure.
214 Configuration of snapshot methods for disk arrays
About EMC Symmetrix arrays
To configure NetBackup clients
1 Install the EMC Solutions Enabler.
You must install EMC Solutions Enabler on each NetBackup media server and client where the array is to be used. After installing the software, continue with the following steps.
2 Register your EMC license keys using the symlmf command.
3 Discover the HBAs in the NetBackup client, to allow the NetBackup client to perform LUN masking operations in the array.
To discover host HBAs, run the following Solutions Enabler SYMCLI command: symmask discover hba -rename
Example output:
Symmetrix ID : 000187930758
Device Masking Status : Success
Identifier Type User-generated Name
----------------------------------------------------
10000000c942e78a Fibre rell/10000000c942e78a where rell is the NetBackup host name.
If no Symmetrix ID appears in the output, there is a connectivity problem.
If the command fails, you must address the problem before doing any further array configuration. This problem can be due to (but is not necessarily limited to) the following:
■ The Solutions Enabler interface is not installed.
■ Your NetBackup client may not be properly zoned to see the array.
For further troubleshooting information, consult your array documentation.
About configuring NetBackup to access the Symmetrix array
You do not need to configure array credentials for the Symmetrix. All communication between NetBackup and the array is done by means of SYMCLI.
If multiple Symmetrix arrays are connected to a NetBackup client, NetBackup automatically sends the SYMCLI command to the correct Symmetrix.
Configuration of snapshot methods for disk arrays
About EMC Symmetrix arrays
215
About configuration for EMC_TimeFinder_Mirror
The EMC_TimeFinder_Mirror method uses the Symmetrix Business Continuance
Volume (BCV) to allow NetBackup to perform mirror backups. For this method, the Snapshot Client source devices are assumed to be STD devices and the target snapshot resources are assumed to be BCV devices. BCV devices are normally created by your EMC technical representative. The EMC_TimeFinder_Mirror method requires that the source device or standard device (STD) be fully synchronized (established) with the snapshot device (BCV). BCV devices must already exist before they can be synchronized and used in a NetBackup backup.
Fully synchronizing STD/BCV mirror pairs
Make sure that each target (BCV) disk is fully synchronized with its source (STD).
One way to accomplish this synchronization is as follows.
To fully synchronize STD/BCV mirror pairs
1 Create a temporary file that contains only the source and target device IDs separated by a space. (Only one source-target pair can exist in a temporary file.)
For example, if the source (STD) device ID is 0050 and the target (BCV) device
ID is 0060, the temporary file should contain the following:
0050 0060
2 Use the symmir command to fully establish the mirror pair.
symmir -sid 000187910258 establish -f temp_file -full
When the pair is synchronized, it can be used in a NetBackup policy.
Synchronization can take a long time. For example, it may take between 5 and 10 minutes for an 8GB STD/BCV pair to enter the synchronized state.
3 Check the status of the mirror pair: symmir -sid 000187910258 query -file temp_file
Make sure the temp_file name matches the temp_file name you used above.
4 In the output, look for Synchronized under the State column. When the pair enters the synchronized state, it is ready to be used for backup.
About configuration for EMC_TimeFinder_Clone
The EMC_TimeFinder_Clone method uses Symmetrix standard devices (STD) as the NetBackup Snapshot Client source devices and TimeFinder Clone copies as
216 Configuration of snapshot methods for disk arrays
About EMC Symmetrix arrays the snapshot devices. Any Symmetrix STD or BCV device can be used as an
EMC_TimeFinder_Clone method snapshot resource.
This method does not require the establishment of a clone relationship between the primary and secondary before the backup. NetBackup automatically manages the primary-secondary clone relationship in the context of a Symmetrix copy session.
Verifying that the clone is complete before doing a point in time rollback
NetBackup initiates clone creation on the array. For large source devices, clone creation may take a long time to complete. The Symmetrix array, however, makes the new clone immediately available for normal restore. This availability allows individual files or directories to be restored as soon as the NetBackup Activity
Monitor marks the job as finished, even if the clone has not been fully created.
Although you can restore individual files or directories before the clone is completely copied, you cannot perform a point in time rollback. Clone creation must be complete before a point in time rollback can succeed.
If a point in time rollback begins before the clone is finished, the restore fails without a failure notification in the Activity Monitor. In this case, the bpfis log contains the phrase
Invalid clone state, cannot restore from device-ID to device-ID
, where the first device ID is the source and the second is the clone.
To verify that the clone is complete before doing a point in time rollback
1 Create a temporary file that contains only the source and target device IDs separated by a space.
For example, if the source device ID is 0050 and the target (clone) device ID is 0060, the temporary file should contain the following:
0050 0060
2 Check the status of the clone with the symclone command. For example: symclone -sid 58 query -file /tmp/0050_0060.txt
where 58 is a short version of a Symmetrix ID ending in 58, such as
000187910258
, and
/tmp/0050_0060.txt
is the temporary file.
3 In the output, look for
Copied under the
State column. When the clone pair is in the copied state, it is ready for point-in-time rollback.
Configuration of snapshot methods for disk arrays
About EMC Symmetrix arrays
217
About configuration for EMC_TimeFinder_Snap
The EMC_TimeFinder_Snap method uses Symmetrix virtual devices (VDEV) to allow NetBackup to perform copy-on-write snapshot backups. This method does not require the establishment of a source-snapshot relationship between the primary and the VDEV devices before the backup. NetBackup automatically manages the source-snapshot relationship.
VDEV devices must already exist before they can be used in a NetBackup backup.
Normally virtual devices are created by your EMC technical representative.
Configuring a policy for EMC_TimeFinder methods
Use the following instructions for the EMC TimeFinder array methods
(EMC_TimeFinder_Snap, EMC_TimeFinder_Clone, EMC_TimeFinder_Mirror).
Help for setting up a NetBackup policy is available.
See
“Configuring a Snapshot Client policy”
on page 56.
To configure a policy for EMC_TimeFinder methods
1 In the NetBackup Administration Console, click the Perform snapshot
backups box on the policy Attributes tab.
2 Click the Snapshot Client Options option to display the Snapshot Options dialog box.
3 In the Snapshot method pull-down list, select a TimeFinder method.
4 In the Snapshot Options dialog box of the policy, you must specify the following information:
■ Symmetrix ID.
■ Unique ID for the snapshot resource from which the TimeFinder_Mirror,
Clone, or Snapshot is created.
■ Unique ID for the target device(s) where the mirror, clone, or snapshot is created.
NetBackup uses this information to correctly rotate through the snapshot, clone, or mirrors when performing a backup. After all the snapshots, clones, or mirrors have been used in a backup, NetBackup automatically determines which is the oldest. NetBackup expires the oldest snapshot, clone, or mirror so that it can be reused for the current backup.
5 See your array administrator for these values.
218 Configuration of snapshot methods for disk arrays
About HP EVA arrays
6 Copy and paste (or type) these values into the appropriate field of the
NetBackup policy’s Add Snapshot Resource dialog box. The procedure is as follows.
7 After selecting an EMC_TimeFinder method on the Snapshot Options dialog box, click Add.
8 In the Add Snapshot Resource dialog box, enter the Symmetrix ID in the
Array Serial # field.
9 Enter the unique ID for the source device in the Source Device field.
10 Enter the unique IDs for the target devices in the Snapshot Device(s) field.
To enter multiple IDs, place a semicolon between them. The ID should be a four-digit value.
■ For EMC_TimeFinder_Mirror, the target devices are BCV devices.
■ For EMC_TimeFinder_Snap, the target devices are VDEV devices.
■ For EMC_TimeFinder_Clone, the target devices are the STD devices that were allocated to be used as clones.
11 Enter source and target device IDs exactly as they appear on the Symmetrix.
For example, if device 4c appears as 004C, then enter it as 004C (case does not matter). The symdev show command can be used to determine how a device ID appears on Symmetrix. Refer to your SymCLI documentation for more information on this command.
For Instant Recovery backups, the Snapshot Device(s) entries determine where and in what order the snapshots are retained.
See
on page 105.
About HP EVA arrays
The following sections describe configuration steps for supported HP arrays.
These steps must be completed before you run a backup.
Prerequisites for working with HP EVA arrays
Note the following prerequisites for the tasks in this section. See your array administrator for further assistance.
■ Add your host (HBA) to the EVA array. All NetBackup primary clients and any alternate clients must be "added" to the EVA array. You can use the SSSU for
HP StorageWorks Command View EVA utility or the StorageWorks Command
View EVA Web interface. Refer to your HP EVA documentation for details.
Configuration of snapshot methods for disk arrays
About HP EVA arrays
219
The EVA array requires that the NetBackup client’s world-wide port name (not the world-wide node name) be used when you add the host entry to the array.
HP EVA software requirements for UNIX
shows the required HP software.
Table 10-5 Software that is required for HP EVA
Software Where to install
SSSU for HP
StorageWorks Command
View EVA (CLI)
NetBackup clients
HP StorageWorks
Command View EVA
Web interface
HP Command View
EVA server
Versions
For versions used in test configurations, see Symantec NetBackup
Snapshot Client Configuration, at: http://www.symantec.com/docs/TECH51377
For versions used in test configurations, see Symantec NetBackup
Snapshot Client Configuration, at: http://www.symantec.com/docs/TECH51377
Diagram of installed software for HP EVA
shows the software components on the NetBackup clients and the HP
EVA Command View server for UNIX and indicates the control function of each.
220 Configuration of snapshot methods for disk arrays
About HP EVA arrays
UNIX client
NetBackup Snapshot
Client
Create snapshot
Restore data
SSSU CLI
Figure 10-3 Software components on NetBackup clients and HP EVA
HP EVA array
HP StorageWorks
Command View
EVA
Register host with array
Create snapshot or restore
HP StorageWorks
Command View
EVA server
StorageWorks
Command View
Web interface
Symantec support for VSS Snapshot and HP EVA
Symantec has an open support policy for VSS Snapshot for NetBackup Snapshot
Client. If a vendor supports a VSS provider for a Windows platform, Symantec provides support for local snapshot, alternate client, FlashBackup local snapshot, and FlashBackup alternate client methods. To use an HP EVA disk array with VSS, contact HP Corporation for the required software and versions. HP supplies this software as a bundle, to ensure that the software components are at the right level and function correctly.
Note that the open support policy for VSS providers is not applicable to Instant
Recovery. To use VSS along with the NetBackup Instant Recovery feature, refer to the NetBackup 7.x Snapshot Client Compatibility List for the components that
NetBackup supports for Instant Recovery with the array. The compatibility list is available at the following URL: http://www.symantec.com/docs/TECH126901
Configuration of snapshot methods for disk arrays
About HP EVA arrays
221
Verifying connectivity from clients to array using SSSU 5.0
NetBackup communicates with the array by means of the SSSU for HP
StorageWorks Command View EVA utility or the StorageWorks Command View
EVA Web interface. To verify that the CLI is installed and that NetBackup can communicate with the array, use the following procedure on each NetBackup client.
To verify connectivity from clients to array using SSSU 5.0
1 Connect to the disk array host:
/opt/hp/sssu/sssu_sunos
Example output:
SSSU for HP StorageWorks Command View EVA 5.0 [v5.0.12]
2 Log on to the disk array host:
NoSystemSelected> select manager manager_host user=manager_username password=manager_password
3 Verify that you can see the EVA arrays that are managed by the host:
NoSystemSelected> ls cell
Example output:
Systems available on this Manager:
HPEVA4000
VRTS.EVA.ROS
See
“Troubleshooting the SSSU procedure”
on page 222.
222 Configuration of snapshot methods for disk arrays
About HP EVA arrays
To verify connectivity from clients to array using SSSU 6.0
1 Connect to the disk array host:
/opt/hp/sssu/sssu_sunos
Example output:
SSSU for HP StorageWorks Command View EVA
Version: 6.0
Build: 34
2 At the prompts, log on to the disk array host:
Manager:disk array host name
Username:username
Password:password
3 Verify that you can see the EVA arrays that are managed by the host:
NoSystemSelected> ls cell
Example output:
Systems available on this Manager: hpeva_2200nc07
See
“Troubleshooting the SSSU procedure”
on page 222.
Troubleshooting the SSSU procedure
If the SSSU command fails, you must address the problem before you do any further array configuration. This problem could be due to the following:
■ The SSSU for HP StorageWorks Command View EVA utility is not installed.
■ The SSSU for HP StorageWorks Command View EVA utility is not a supported version.
■ The array manager credentials are invalid.
For further troubleshooting information, consult your EMC Storage Scripting
System Reference manual.
Policy validation failure for the SSSU command
Policy validation fails when the SSSU CLI is not present at the expected path. The logs display the message
Configuration of snapshot methods for disk arrays
About HP EVA arrays
223
Unable to locate the CLI tool /opt/hp/sssu/ at path sssu_hpux
,
The cause of the error message is the CLI path, which is different from the default
CLI path.
To fix the policy validation, add the following entry into the hpevafi.conf
file:
[CLI_TOOL_INFO]
"FILEPATH"="<SSSU CLI path>"
"FILENAME"="<SSSU CLI tool file name>"
For example, for the HP platform the path would be:
/usr/openv/lib/vxfi/configfiles/hpevafi.conf
The entry would be:
[CLI_TOOL_INFO]
"FILEPATH"="/opt/hp/sssu"
"FILENAME"="sssu_hpux_parisc"
After you manually add these inputs to the hpevafi.conf
file, the validation is successful.
Configuring NetBackup to access the EVA array
You must configure logon credentials on the NetBackup master server that allow the NetBackup client to access the array, as follows.
To configure NetBackup to access to the array
1 In the NetBackup Administration Console, click the Media and Device
Management > Credentials > Disk Array Hosts node in the NetBackup
Administration Console.
2 Right-click in the Disk Array Hosts pane and select New Disk Array Host.
3 Enter the host name through which the array management service is to be accessed. For some arrays, the array management service runs on a separate host; for other arrays it runs in the array itself.
4 Select HP EVA in the Disk Array Host Type pull-down menu.
5 Enter the user name and password for the array management service.
6 Clear (uncheck) the Connect using port number box.
224 Configuration of snapshot methods for disk arrays
About HP EVA arrays
Configuring a NetBackup policy for an HP EVA array method
Help is available for setting up a NetBackup policy in the NetBackup Administration
Console.
See
“Configuring a Snapshot Client policy”
on page 56.
To configure a NetBackup policy for an HP EVA array method
1 In the NetBackup Administration Console, click the Perform snapshot
backups box on the policy Attributes tab.
2 Click the Snapshot Client Options option to display the Snapshot Options dialog box.
3 In the Snapshot method pull-down list, select an HP EVA method.
4 You can set the Maximum snapshots (Instant Recovery only) parameter.
The maximum value is 16 snapshots or vsnaps per source device.
See
on page 106.
HP EVA restrictions
Note the following array configuration restrictions. In essence, you cannot use two or more EVA snapshot methods for a given source disk.
Table 10-6
Array
VSnaps
Snapshots
SnapClones
Restrictions
Note the following restrictions:
■
■
■ If any VSnaps exist, you cannot create Snapshots or
Clones of the source until existing VSnaps are deleted.
A maximum of 16 VSnaps can exist for any VDisk.
You cannot perform a rollback restore from a VSnap or a Snapshot. Rollback only works with clones.
Note the following restrictions:
■
■
■ If any Snapshots exist, you cannot create VSnaps or
Clones of the source until existing Snapshots are deleted.
A maximum of 16 snapshots can exist for any VDisk.
You cannot perform a rollback restore from a VSnap or a Snapshot. Rollback only works with clones.
Any number of clones can be created for a VDisk, as long as disk space exists in the disk group.
Configuration of snapshot methods for disk arrays
About IBM DS6000 and DS8000 arrays
225
About IBM DS6000 and DS8000 arrays
The following sections include background information and configuration tasks for NetBackup Snapshot Client backups using IBM DS6000 and DS8000 arrays.
These tasks must be completed before you run a backup.
IBM DS6000 and DS8000 software requirements
The following IBM software is required.
Software that is required for IBM DS6000 and DS8000 Table 10-7
Software
DSCLI
Where to install
Default location
Version
5.2.2.224 or higher
For instructions on installing the software, refer to your IBM documentation.
Preconfiguration for IBM arrays
No preconfiguration steps are required for IBM DS6000 and DS8000 arrays.
Configuring NetBackup to access the IBM DS6000 or DS8000 array
You must supply logon credentials that allow the NetBackup client to access the
IBM array.
To configure NetBackup to access the IBM DS6000 or DS8000 array
1 In the NetBackup Administration Console, click the Media and Device
Management > Credentials > Disk Array Hosts node in the NetBackup
Administration Console.
2 Right-click in the Disk Array Hosts pane and select New Disk Array Host.
3 For the IBM DS6000 or DS8000 array, enter the name of the host management console (the system where the Storage Manager resides).
4 Select IBM System Storage in the Disk Array Host Type pull-down menu.
5 Enter the user name and password for the array.
6 Clear (uncheck) the Connect using port number box.
226 Configuration of snapshot methods for disk arrays
About IBM DS6000 and DS8000 arrays
Configuring array access for NetBackup hosts not named in a policy
Certain NetBackup hosts that are not named as clients in a policy must be explicitly enabled to access array credentials. An example is a media server that is used for off-host backup processing but is not included in any policy’s Clients list.
To configure array access for NetBackup hosts not named in a policy
1 In the NetBackup Administration Console, click Host Properties > Master
servers > double click name of master server > Properties > Credential
Access.
2 Click Add to enter the name of the client. Then click OK.
Configuring the IBM array for NetBackup
You must add each NetBackup client and alternate client to the IBM array and make array devices available to the clients. In brief, the steps are the following:
To configure the IBM array for NetBackup
1 On the IBM array, provide host name and port information for the NetBackup client.
Note the following:
■ The nickname (on the IBM DS6000 or DS8000) can be the same as the
NetBackup client name.
■ In the IBM DS6000 or DS8000 Storage Manager interface, the host type for AIX may not be obvious. Select
IBM pSeries
.
■ As part of the host definition, select the WWPN of the NetBackup client.
Your NetBackup client must be properly zoned on the SAN to allow communication between it and the array.
2 Repeat step
for each NetBackup client or alternate client that uses the array.
3 Create a volume group and associate the volume group with the NetBackup host you have defined on the array. For details, refer to your IBM documentation.
4 Create logical volumes (or logical drives) for the volume group. This step makes the volumes or drives visible to the NetBackup client. For details, refer to your IBM documentation.
Configuration of snapshot methods for disk arrays
About IBM DS6000 and DS8000 arrays
227
Using DSCLI commands to obtain unique IBM identifiers
The NetBackup policy requires entry of the array’s Unique ID. If your array administrator provided LUN numbers for the devices, you must convert those
LUN numbers into unique IDs for entry in the NetBackup policy Snapshot
Resources pane. You can obtain the LUN unique IDs in either of two ways, as described in this topic.
The LUN ID of the primary and snapshot (clone) logical volume can be found from the array by means of DSCLI commands or the IBM Storage Manager interface.
228 Configuration of snapshot methods for disk arrays
About IBM DS6000 and DS8000 arrays
To use DSCLI commands to obtain unique IBM identifiers
1 Find the host connection and its corresponding volume group by entering the following: lshostconnect -dev enclosure_ID
Example: dscli> lshostconnect -dev IBM.1750-6866123
Date/Time: December 17, 2007 4:18:02 PM IST IBM DSCLI Version: 5.2.2.224 DS:
IBM.1750-6866123
Name ID WWPN HostType Profile portgrp volgrpID
ESSIOport
====================================================================================== oigtsol05 all
0000 10000000C956A9B4 Sun SUN - Solaris 0 V11
0022 10000000C969F60E pSeries IBM pSeries - AIX 0 V46 oigtaix03 all oigtaix02 all
0023 10000000C94AA677 pSeries IBM pSeries - AIX 0 V47
2 Find the volumes presented to this volume group and to the host: showvolgrp -dev enclosure_ID volume_group
Example: dscli> showvolgrp -dev IBM.1750-6866123 V47
Date/Time: December 17, 2007 4:21:01 PM IST IBM DSCLI Version: 5.2.2.224 DS:
IBM.1750-6866123
Name oigtaix02
ID V47
Type SCSI Mask
Vols 0002 0003 0004 0005 0006 0007 0008 0009 0031
The values listed for
Vols are the LUN ids.
3 Find out which device on the host corresponds to a given logical volume.
Enter the following:
/usr/openv/netbackup/bin/nbfirescan
Configuration of snapshot methods for disk arrays
About IBM DS6000 and DS8000 arrays
229
To use the IBM Storage Manager web interface to obtain the device identifiers
1 In the Storage Manager, click Real-time manager > Manage hardware > Host
systems.
2 Click the host for which you need to find the volumes presented.
The volume groups that are associated with the host are displayed.
3 Click the volume group to get the list of the logical volumes that are configured in this volume group.
The Number column indicates the LUN ID.
230 Configuration of snapshot methods for disk arrays
About IBM DS6000 and DS8000 arrays
Configuring a NetBackup policy for IBM_DiskStorage_FlashCopy
For general help setting up a NetBackup policy in the NetBackup Administration
Console, refer to the NetBackup Snapshot Client Administrator’s Guide.
The following procedure focuses on the IBM_DiskStorage_FlashCopy method and its parameters.
To configure a NetBackup policy for IBM_DiskStorage_FlashCopy
1 In the NetBackup Administration Console, click the Perform snapshot
backups box on the policy Attributes tab.
2 Click the Snapshot Client Options option to display the Snapshot Options dialog box.
3 In the Snapshot method pull-down list, select IBM_DiskStorage_FlashCopy.
4 If needed, set Wait for flashcopy operation to complete to 1.
By default (0), the backup does not wait for the FlashCopy operation to complete. If the backup begins before the FlashCopy operation completes, database performance on the client (such as Oracle) may be affected until the
FlashCopy is complete. A setting of 1 means that NetBackup waits for the
FlashCopy to complete before the backup begins, to avoid any performance issues on the client.
Note that a setting of 1 may cause the backup elapsed time to increase significantly. The primary (production) volume may not be accessible until the FlashCopy command completes.
5 On the Snapshot Options dialog box in the Snapshot Resources pane, click
Add.
NetBackup uses the information in the Snapshot Resources pane to correctly rotate through the clone LUNs when performing a FlashCopy clone backup.
After all clone LUNs have been used in a backup, NetBackup automatically determines which clone is the oldest. NetBackup expires the oldest clone so that it can be reused for the current backup. If that clone represents the only backup image copy, NetBackup also expires the backup image associated with the clone.
Note that the policy Backup Selections determine one or more source LUNs for which snapshots are taken for backup. For each source LUN that is specified in the policy Backup Selections list, you must provide the information detailed in the following steps.
See
“Using DSCLI commands to obtain unique IBM identifiers”
on page 227.
6 In the Add Snapshot Resource dialog box, enter the array's serial number in the Array Serial Number field.
Configuration of snapshot methods for disk arrays
About IBM DS4000 array
231
7 Enter the unique ID for the source LUN in the Source Device field.
8 Enter the unique IDs for the clone LUNs in the Snapshot Device(s) field. To enter multiple IDs, place a semicolon between them.
Note the following:
■ The clone LUNs must be unmasked to the client (or alternate client) before you start a backup.
■ For Instant Recovery backups, the Snapshot Device(s) entries determine where and in what order the snapshots are retained.
For further reference on IBM arrays
The following IBM documents may be helpful:
■ The IBM System Storage DS6000 Series: Copy Services http://www.redbooks.ibm.com/redpieces/abstracts/sg246782.html
http://www.redbooks.ibm.com/abstracts/sg246783.html
■ The IBM System Storage DS8000 Series: Copy Services http://www.redbooks.ibm.com/abstracts/sg246787.html
http://www.redbooks.ibm.com/abstracts/sg246788.html
About IBM DS4000 array
The following sections include background information and configuration tasks for NetBackup Snapshot Client backups using IBM DS4000 arrays. These tasks must be completed before you run a backup.
describes the snapshot method for the IBM DS4000.
Table 10-8 New snapshot method for the IBM DS4000 disk array
Method name
IBM_StorageManager_FlashCopy
Description
For full-volume copy (clone) snapshots on the IBM DS4000 series of arrays (excluding
4100), with SMcli version 9.60.
Array preconfiguration tasks
Before you configure a NetBackup policy, make sure that the following tasks have been completed.
describes the tasks.
232 Configuration of snapshot methods for disk arrays
About IBM DS4000 array
Table 10-9 Array preconfiguration tasks
Array administration tasks
Install the disk array and its software, including appropriate licenses.
Where described
See your array documentation.
See
“IBM 4000 software requirements”
on page 232.
See your HBA documentation.
Install supported HBAs on the NetBackup primary client and alternate clients.
Zone the client HBAs through the Fibre
Channel switch, so the array is visible to the primary client and to any alternate clients.
See your Fibre Channel documentation.
Install NetBackup, and array vendor snapshot management software, on the
NetBackup primary client and any alternate clients.
See the appropriate installation documentation.
Create and configure the Access Logical
Drive for the host connection at the array.
Configure logical drives on the array and make them visible to the host.
See your array documentation.
IBM 4000 software requirements
The following IBM software is required.
Software that is required for IBM 4000 Table 10-10
Software
SMclient
SMruntime
Where to install Version
Default location on NetBackup client: 9.60 or higher
/opt/IBM_DS4000/
Default location on NetBackup client: 9.16 or higher
/opt/IBM_DS4000/
For instructions on installing the software, refer to your IBM documentation.
Verifying NetBackup client access, zoning, and LUN masking
You can use the nbfirescan command to verify the following: that NetBackup clients have access to the array devices, and that the arrays are properly zoned
Configuration of snapshot methods for disk arrays
About IBM DS4000 array
233 and LUNs are unmasked. Note that nbfirescan only displays LUNs that have been unmasked and mapped to the host.
To verify NetBackup client access, zoning, and LUN masking
◆ Enter the following on the client:
/usr/openv/netbackup/bin/nbfirescan
This command queries the host’s SCSI bus for all the SCSI (or Fibre) attached devices that are visible.
Example output from an AIX host, for Hitachi and IBM arrays, followed by a description:
DevicePath Vendor Product ID EnclosureId DeviceId [Ctl,Bus,Tgt,Lun]
-------------------------------------------------------------------------
/dev/hdisk8
/dev/hdisk9
HITACHI
HITACHI
OPEN-V-CM
OPEN-V
10266
10266
241
840
[00,00,144640,00]
[00,00,144640,01]
/dev/hdisk45 IBM 1814 FAStT IBM.1814-600A0B800042212
2000000004804132760:0A:0B:80:00:42:33:6E:00:00:16:EF:48:DC:3C:1F [00,00
,327936,01]
/dev/hdisk46 IBM 1814 FAStT IBM.1814-600A0B800042212
2000000004804132760:0A:0B:80:00:42:33:6E:00:00:16:F7:48:DC:57:F3 [00,00
,327936,02]
/dev/hdisk43 IBM 1814 FAStT IBM.1814-600A0B800042212
2000000004804132760:0A:0B:80:00:42:33:6E:00:00:14:A4:48:AA:52:87 [00,00
,327936,03]
/dev/rdsk/c2t6d11s6 HITACHI DF600F
/dev/rdsk/c2t6d10s6 HITACHI DF600F
6484
6484
48
46
/dev/rdsk/c2t10d3s6 HITACHI OPEN-V -SUN 45027 18
/dev/rdsk/c2t10d0s6 HITACHI OPEN-V-CM 45027 0
[00,00,00,00]
[00,00,00,00]
[00,00,00,00]
[00,00,00,00]
Note the following descriptions:
DevicePath
EnclosureId
DeviceId
Ctl,Bus,Tgt,LUN
Represents the actual access point for the device as it exists on the client host.
Unique for each physical disk array.
Unique for a physical disk or virtual disk in an enclosure.
The EnclosureId/DeviceId pair constitutes a host-independent designation of a particular physical or virtual disk within a disk array.
Controller, bus, target, and LUN numbers are the elements that designate a particular physical or virtual disk from the perspective of the client host computer.
234 Configuration of snapshot methods for disk arrays
About IBM DS4000 array
Configuring NetBackup to access the IBM DS4000 array
You must supply logon credentials that allow the NetBackup client to access the
IBM array.
To configure NetBackup to access the IBM DS4000 array
1 In the NetBackup Administration Console, click the Media and Device
Management > Credentials > Disk Array Hosts node.
2 Right-click in the Disk Array Hosts pane and select New Disk Array Host.
3 Enter a dummy (substitute) host name for the IBM 4000 array. Do not enter the actual host name of the array.
4 Select IBM System Storage in the Disk Array Host Type pull-down menu.
5 Enter a user name and the correct password for the array.
The actual user name is not required for disk array operations. You can enter a dummy user name. The password, however, must be valid.
6 Clear (uncheck) the Connect using port number box.
Configuring the IBM 4000 array for NetBackup
You must add each NetBackup client and alternate client to the IBM array and make array devices available to the clients. In brief, the steps are the following.
To configure the IBM 4000 array for NetBackup
1 On the IBM array, provide host name and port information for the NetBackup client. Note the following:
■ Define the host and host group.
A given host group must have a single host, and host name(s) must exist for every HBA port on the host.
■ The host name and host group name on the IBM 4000 must be the same as the NetBackup client name. If more than one host-HBA port entry exists, the host name can differ from the client name.
■ In the IBM Storage Manager interface, select AIX as the host type.
■ As part of the host definition, select the WWPN of the NetBackup client.
Your NetBackup client must be properly zoned on the SAN to allow communication between it and the array.
2 Repeat step 1 for each NetBackup client or alternate client that uses the array.
Configuration of snapshot methods for disk arrays
About IBM DS4000 array
235
3 For every client and host group added, map an Access Logical Drive on LUN number 7 or 31.
4 Create logical drives and map them to the host group. This step makes the logical drives visible to the NetBackup client. For details, refer to your IBM documentation.
Configuring a NetBackup policy for IBM_StorageManager_FlashCopy
For general help setting up a NetBackup policy, refer to the NetBackup Snapshot
Client Administrator’s Guide.
The following procedure focuses on the IBM_StorageManager_FlashCopy method and its parameters.
To configure a NetBackup policy for IBM_StorageManager_FlashCopy
1 In the NetBackup Administration Console, click the Perform snapshot
backups box on the policy Attributes tab.
2 Click Snapshot Client Options to display the Snapshot Options dialog box.
3 In the Snapshot method pull-down list, select
IBM_StorageManager_FlashCopy.
4 You can set the following parameters:
Maximum snapshots
(Instant Recovery only) parameter
The maximum value is 4 snapshots per source device.
For more information on the Maximum Snapshots parameter, see the NetBackup Snapshot Client Administrator’s Guide.
Repository % of Base
(100 for Instant
Recovery)
Determines the size of the IBM repository logical drive as a percentage of the primary device (base logical drive). The size can range from 1% to 100%. The more write activity that occurs on the primary drive, the more space the repository logical drive requires.
If the size of the primary is 500 GB and you set this parameter to 30%, the repository drive is set to 150 GB (30% of 500).
For Instant Recovery backups, the percentage is set to 100% regardless of any value that is entered here. The default (0) does not mean 0%: it means that the array determines the size of the repository drive (usually 20%).
For more details about the repository logical drive, refer to the IBM System Storage DS4000 Series and Storage Manager document.
236 Configuration of snapshot methods for disk arrays
About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
The following sections include background information and configuration tasks for NetBackup Snapshot Client backups using Hitachi SMS/WMS/AMS, USP/NSC, and USP-V/VM series of arrays.
These tasks must be completed before you run a backup.
Hitachi array software requirements
The following Hitachi software is required.
Table 10-11 Software that is required for Hitachi arrays
Software
RAID Manager/LIB
64-bit
Where to install
NetBackup client
Version
01-12-03/04 or later.
Note: To determine the RAID
Manager version, run the following:
/usr/lib/RMLIB/bin/whatrmver
See
on page 236.
For instructions on installing the software, refer to your Hitachi documentation.
Determining the current RAID Manager version
Use the following procedure.
To determine the current RAID Manager version
◆ Enter the following:
/usr/lib/RMLIB/bin/whatrmver
Example output:
Model :RAID-Manager/LIB/Solaris
Ver&Rev:01-12-03/04
Preconfiguration for Hitachi
Before running backups, you must configure the arrays and appropriate volumes.
Refer to your Hitachi array documentation.
Configuration of snapshot methods for disk arrays
About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
237
Pair status must be PSUS After creating volume pairs, you must split each pair and leave the status of the pair at PSUS.
You can use the following CCI command: pairsplit -g dg_name -d device_name -l where dg_name and device_name are the names specified in the CCI configuration file for the primary device.
Configure command devices on
NetBackup client and alternate client
The Hitachi command devices must be visible to the NetBackup client as well as to any alternate client. To configure command devices, refer to your Hitachi documentation.
About communication between NetBackup and the Hitachi array
You do not need to configure array credentials for the Hitachi array. All communication between NetBackup and the array is done by means of command devices. If multiple Hitachi arrays are connected to a NetBackup client, NetBackup sends the NetBackup command to the correct Hitachi array.
To determine if the command devices are visible, see the following topic:
See
“Determining if the Hitachi command devices are visible”
on page 237.
Determining if the Hitachi command devices are visible
Use the following procedure to determine if the Hitachi command devices are visible.
238 Configuration of snapshot methods for disk arrays
About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
To determine if the Hitachi command devices are visible
◆ Enter the following:
/usr/openv/netbackup/bin/nbfirescan
Example output: nbfirescan v4.4.2 - Copyright ©) 2005-2007 Symantec Corp.
Rescanning devices..............................................Complete.
Device count: 37
DevicePath Vendor Product ID EnclosureId DeviceId [Ctl,Bus,Tgt,Lun]
--------------------------------------------------------------------------------------
/dev/rdsk/c3t50060E801029F700d22s6 HITACHI DF600F
[00,00,00,00]
10816 0201
/dev/rdsk/c3t50060E801029F700d1s6 HITACHI DF600F-CM 10816
[00,00,00,00]
0003
The last line of the example shows a command device (DF600F-CM).
See
“About communication between NetBackup and the Hitachi array”
on page 237.
About configuring the Hitachi array for NetBackup
You must add each NetBackup client and alternate client to a host group on the
Hitachi array.
Note the following:
■ The name of the host group must match the host name or fully qualified domain name of the client as specified in the NetBackup policy. The name should not be more that 16 characters in length.
■ For host entries in the host groups, specify the WWNN/WWPN of each host.
Obtaining the Hitachi array serial number and the unique device identifiers
The NetBackup policy requires the Hitachi array's serial number and the unique
IDs (device identifiers) for the source and clone LUNs. Use the following procedure to obtain that information.
Configuration of snapshot methods for disk arrays
About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
239
To obtain the Hitachi array serial number and the unique device identifiers
◆ Enter the following command:
/usr/openv/netbackup/bin/nbfirescan
Example output:
DevicePath Vendor Product ID EnclosureId DeviceId [Ctl,Bus,Tgt,Lun]
----------------------------------------------------------------------------------------
-------------------------------------------------------------------------------
/dev/rdsk/c2t6d15s HITACHI F600F 6484 53 [00,00,00,00]
/dev/rdsk/c2t6d14s6 HITACHI F600F 6484 52 [00,00,00,00]
The Enclosure ID is the serial number and the Device ID is the array’s device
ID.
Configuring a NetBackup policy for Hitachi_ShadowImage or
Hitachi_CopyOnWrite
For general help setting up a NetBackup policy in the NetBackup Administration
Console, refer to the NetBackup Snapshot Client Administrator’s Guide.
The following procedure focuses on the Hitachi_ShadowImage and
Hitachi_CopyOnWrite methods and their parameters.
Note: The term "clone LUNs," as used in this procedure, refers to the
Hitachi_ShadowImage method. For the Hitachi_CopyOnWrite method, the term
"clone LUNs" can be replaced with "snapshot LUNs."
To configure a NetBackup policy for Hitachi_ShadowImage or Hitachi_CopyOnWrite
1 In the NetBackup Administration Console, click the Perform snapshot
backups box on the policy Attributes tab.
2 Click the Snapshot Client Options option to display the Snapshot Options dialog box.
3 In the Snapshot method pull-down list, select Hitachi_ShadowImage or
Hitachi_CopyOnWrite.
240 Configuration of snapshot methods for disk arrays
About HP-XP arrays
4 In the Snapshot Resources pane, click Add.
NetBackup uses the information in the Snapshot Resources pane to correctly rotate through the designated LUNs when performing a ShadowImage (or
CopyOnWrite) backup. After all clone LUNs have been used in a backup,
NetBackup automatically determines which clone is the oldest. NetBackup expires the oldest clone so that it can be reused for the current backup. If that clone represents the only backup image copy, NetBackup also expires the backup image associated with the clone.
Note that the policy’s Backup Selections list must specify one or more source
LUNs for which snapshots are created for the backup. For each source LUN in the policy Backup Selections list, you must supply a serial number and unique IDs.
See
“Obtaining the Hitachi array serial number and the unique device identifiers”
on page 238.
5 In the Add Snapshot Resource dialog box, enter the array's serial number in the Array Serial # field.
6 Enter the unique ID for the source LUN in the Source Device field.
The ID must be entered without leading zeroes. For example, if the LUN ID is 0110, enter 110 in the Source Device field.
7 Enter the unique IDs for the clone LUNs (for Hitachi_ShadowImage method) or the snapshot LUNs (for Hitachi_CopyOnWrite) in the Snapshot Device(s) field. To enter multiple IDs, place a semicolon between them.
The ID must be without leading zeroes. For example, if the LUN ID is 0111, enter 111 in the Snapshot Device(s) field.
Note the following:
■ The LUNs must be unmasked to the client (or alternate client) before you start a backup.
■ For Instant Recovery backups, the Snapshot Device(s) entries determine where and in what order the snapshots are retained.
About HP-XP arrays
The following sections include background information and configuration tasks for NetBackup Snapshot Client backups using HP-XP series of arrays.
These tasks must be completed before you run a backup.
Configuration of snapshot methods for disk arrays
About HP-XP arrays
241
HP-XP array software requirements
The following HP-XP software is required.
Table 10-12 Software that is required for HP-XP arrays
Software
RAID Manager/LIB
64-bit
Where to install
NetBackup client
Version
01-12-03/04 or later
Note: To determine the RAID Manager version, run the following:
/usr/lib/RMLIB/bin/whatrmver
See
on page 236.
For instructions on installing the software, refer to your HP-XP documentation.
Preconfiguration for HP-XP
Before running backups, you must configure the arrays and appropriate volumes.
Refer to your HP-XP array documentation.
Pair status After creating volume pairs, you must split each pair and leave the status of the pair at
PSUS.
You can use the following CCI command: pairsplit -g dg_name -d device_name -l where dg_name and device_name are the names specified in the CCI configuration file for the primary device.
Configure command devices on NetBackup client and alternate client
The HP-XP command devices must be visible to the NetBackup client as well as to any alternate client. To configure command devices, refer to your HP-XP documentation.
About communication between NetBackup and the HP-XP array
You do not need to configure array credentials for the HP-XP array. All communication between NetBackup and the array is done by means of command devices. If multiple HP-XP arrays are connected to a NetBackup client, NetBackup sends the NetBackup command to the correct HP-XP array.
242 Configuration of snapshot methods for disk arrays
About HP-XP arrays
To determine if the command devices are visible, see the following topic:
See
“Determining if the HP-XP command devices are visible”
on page 242.
Determining if the HP-XP command devices are visible
Use the following procedure to determine if the command devices are visible.
To determine if the command devices are visible
◆ Enter the following:
/usr/openv/netbackup/bin/nbfirescan
About configuring the HP-XP array for NetBackup
You must add each NetBackup client and alternate client to a host group on the
HP-XP array.
Note the following:
■ The name of the host group must match the host name or fully qualified domain name of the client as specified in the NetBackup policy. The name should not be more that 16 characters in length.
■ For host entries in the host groups, specify the WWNN/WWPN of each host.
Obtaining the array serial number and unique HP-XP identifiers
The NetBackup policy requires the HP-XP array's serial number and the unique
IDs (device identifiers) for the source and clone LUNs. Use the following procedure to obtain that information.
To obtain the array serial number and unique HP-XP identifiers
◆ Enter the following command:
/usr/openv/netbackup/bin/nbfirescan
Configuring a NetBackup policy for HP_XP_BusinessCopy and
HP_XP_Snapshot
For general help setting up a NetBackup policy in the NetBackup Administration
Console, refer to the Symantec NetBackup Administrator's Guide, Volume I.
The following procedure focuses on the HP_XP_BusinessCopy and HP_XP_Snapshot methods and their parameters.
Configuration of snapshot methods for disk arrays
About HP-XP arrays
243
Note: The term "clone LUNs," as used in this procedure, refers to the
HP_XP_BusinessCopy method. For the HP_XP_Snapshot method, the term "clone
LUNs" can be replaced with "snapshot LUNs."
To configure a NetBackup policy for HP_XP_BusinessCopy and HP_XP_Snapshot
1 In the NetBackup Administration Console, click the Perform snapshot
backups box on the policy Attributes tab.
2 Click the Snapshot Client Options option to display the Snapshot Options dialog box.
3 In the Snapshot method pull-down list, select HP_XP_BusinessCopy or
HP_XP_Snapshot.
4 In the Snapshot Resources pane, click Add.
NetBackup uses the information in the Snapshot Resources pane to correctly rotate through the designated LUNs when performing a BusinessCopy (or
Snapshot) backup. After all clone LUNs have been used in a backup, NetBackup automatically determines which clone is the oldest. NetBackup expires the oldest clone so that it can be reused for the current backup. If that clone represents the only backup image copy, NetBackup also expires the backup image associated with the clone.
See
“Obtaining the array serial number and unique HP-XP identifiers”
on page 242.
5 In the Add Snapshot Resource dialog box, enter the array's serial number in the Array Serial # field.
6 Enter the unique ID for the source LUN in the Source Device field.
The ID must be entered without leading zeroes. For example, if the LUN ID is 0110, enter 110 in the Source Device field.
7 Enter the unique IDs for the clone LUNs (for HP_XP_BusinessCopy method) or the snapshot LUNs (for HP_XP_Snapshot) in the Snapshot Device(s) field.
To enter multiple IDs, place a semicolon between them.
The ID must be without leading zeroes. For example, if the LUN ID is 0111, enter 111 in the Snapshot Device(s) field.
Note the following:
■ The LUNs must be unmasked to the client (or alternate client) before you start a backup.
■ For Instant Recovery backups, the Snapshot Device(s) entries determine where and in what order the snapshots are retained.
244 Configuration of snapshot methods for disk arrays
About array troubleshooting
About array troubleshooting
These topics provide troubleshooting assistance for array-related issues.
Troubleshooting issues pertaining to all arrays
Note the following issues:
■ See
“Important disk array method notes and restrictions”
on page 183.
■ Backups fail with the following message in the bpfis log: snapshot services: snapshot method analysis failed: no combos generated: stack elements not capable of any split or quiesce.
This message can appear in the following cases:
■ The source device or target devices were incorrectly specified in the policy.
■ The wrong type of disk array method was selected. For example, if you selected an EMC CLARiiON method for an EMC Symmetrix device.
Troubleshooting Solaris issues
Backups fail on non-Leadville Solaris systems and the following message appears in the bpfis log: devicefi: Failed to the initialize the import node
"UDID##HP##HSV##5000-1FE1-5007-0020##6005-08B4-0010-5F49-0000-5
000-901E-0000", device could not be found.
In this example, an HP-EVA snapshot was not found on the backup host. The
/kernel/drv/sd.conf
file probably has insufficient lun= entries. Add lun= entries for the HP-EVA target in sd.conf
and restart the system. More information is available about LUN entries in sd.conf.
See
on page 191.
Troubleshooting host OS type specification
Some arrays (such as HP EVA) require that you specify the OS type of the host. If the OS type is not set, or is not set properly, unpredictable behavior may result.
Troubleshooting NetBackup and EMC CLARiiON arrays
Note the following issues:
Configuration of snapshot methods for disk arrays
About array troubleshooting
245
Table 10-13 Issues with NetBackup and EMC CLARiiON arrays
Issue Explanation/Recommended Action
Backups fail and the following message appears in the bpfis log: emcclariionfi: Unable to find SP that owns
LUN 1. Verify that credentials have been supplied for the SP that owns LUN 1.
In this example, the message appears because LUN 1 is owned by a CLARiiON storage processor for which credentials have not been supplied. In a single path configuration, all LUNs must be owned by one storage processor and credentials must be supplied for at least that storage processor. It is okay to supply credentials for both storage processors because NetBackup automatically determines which set of credentials should be used. In a multipath configuration, credentials for both storage processors should be supplied because multipathing software may automatically change which storage processor owns the LUN.
Backups fail and the following message appears in the bpfis log: emcclariionfi: WARNING: Unable to import any login credentials for any appliances.
Credentials must be added for the CLARiiON array by means of the NetBackup Administration Console.
See
“Configuring NetBackup to access the CLARiiON array”
on page 202.
Backups fail and one or both of the following messages appear in the bpfis log: emcclariionfi: The host hostname was not found in any storage groups. To import a snapshot to host hostname, hostname must be in a Clariion storage group.
emcclariionfi: LUN masking failed. Could not find a storage group containing the hostname [hostname].
NetBackup searches the CLARiiON's storage groups for the import host. (For a local backup, the import host is the host where the source device is mounted. For an off-host backup, the import host is the alternate client.)
When the host is found, the snapshot device is assigned to that storage group, thus making it visible to the import host where the backup can proceed. If the import host is not in any storage groups, the backup fails.
Backups fail and the following message appears in the bpfis log: emcclariionfi: No more available HLU numbers in storage group. LUN LUN number cannot be LUN masked at this time
EMC_CLARiiON_Snapview_Clone backups fail and the following message appears in the bpfis log: emcclariionfi: Could not find LUN LUN
number in clonegroup clonegroup name
The device cannot be imported to the host, because the maximum number of devices from the array is already imported to this host. Expire any unneeded backup images.
The clone target device does not exist in the clonegroup belonging to the source device. Either correct the target list in the policy or use Navisphere to add the target device to the source device's clone group.
246 Configuration of snapshot methods for disk arrays
About array troubleshooting
Table 10-13 Issues with NetBackup and EMC CLARiiON arrays (continued)
Issue Explanation/Recommended Action
Both types of CLARiiON backups fail with the following in the bpfis log: emcclariionfi: CLIDATA: Error: snapview command failed emcclariionfi: CLIDATA: This version of Core Software does not support
Snapview
These messages appear when the Snapview software is not installed on the CLARiiON array. Snapview must be installed on the array before CLARiiON clone or snapshot backups can succeed. Please see the array documentation or contact EMC for more information.
Backups fail and the following message appears in the bpfis log: execNAVISECCLI: CLI Command [CLI command] failed with error [error number]
NetBackup uses naviseccli to send commands to the
CLARiiON array. If naviseccli encounters an error, it is captured and placed in the bpfis log. The lines immediately following the above line should contain the output from naviseccli that indicates why the command failed.
After a point-in-time rollback from a Windows VSS backup that was made with the EMC CLARiiON Snapview
Clone snapshot provider, all clones are fractured (split from the primary)
As a best practice, avoid performing a point-in-time rollback from a Windows VSS backup that was made with the EMC CLARiiON Snapview Clone snapshot provider, if one of the clones is configured for the policy has not been used for an Instant Recovery backup. After a rollback, all the clones are placed in a “fractured” state.
(Fractured clones are no longer synchronized with the primary.) As a result, any clone that had not already been used for a backup is no longer available for a future
Instant Recovery backup.
If you must perform a point-in-time rollback before all clones have been used for backups, note which clones are still synchronized before you do the rollback. After the rollback, you can manually resynchronize the clones.
Troubleshooting NetBackup and EMC Symmetrix arrays
Note the following issues:
Table 10-14 Issues with NetBackup and EMC Symmetrix arrays
Issue Explanation/Recommended Action
Point in time rollback fails and the following message appears in the bpfis log:
Invalid clone state, cannot restore from
device-ID to device-ID , where the first device ID is the source and the second is the clone.
See
“Verifying that the clone is complete before doing a point in time rollback”
on page 216.
Configuration of snapshot methods for disk arrays
About array troubleshooting
247
Table 10-14 Issues with NetBackup and EMC Symmetrix arrays (continued)
Issue Explanation/Recommended Action
If all Save Device space is consumed on the Symmetrix, a backup with EMC_TimeFinder_Snap or EMC_
TimeFinder_Clone fails with the following error in the bpfis log:
Check the symapi log (often found at /var/symapi/log on UNIX) to determine the exact error. If the log indicates there is no Save Device space, add Save Devices to the
Save Device pool on your Symmetrix array.
An internal Snap or Clone error has occurred. Please see the symapi log file
EMC_TimeFinder_Mirror backups fail and the following message appears in the bpfis log:
This message indicates that the STD-BCV pair is not in a state that allows the mirror to be created. Verify that the pair were fully synchronized before the backup attempt.
emcsymfi: Invalid STD-BCV pair state
See
“Fully synchronizing STD/BCV mirror pairs”
on page 215.
TimeFinder backups fail and a message similar to the following appears in the bpfis log: device 00A4 to director/port that is not accessible to the HBA port 210000e08b86b34f emcsymfi: 2 of 2 HBA WWNs assigned to director/port combinations for accessing device 00A4 are not accessible due to misconfiguration of the array.
Device 00A4 has not been mapped to any Symmetrix director ports that are zoned to the host. All Symmetrix devices (source devices and target devices) must be mapped to an array director port that is zoned to the import host. For a local backup policy, the import host is the host where the source device is mounted. For an off-host backup policy, the import host is the alternate client.
emcsymfi: Since there were no valid mappings the device import will fail. To resolve this issue you must reconfigure your array 000187910258 to bind device 00A4 to director ports accessible to host.
Troubleshooting NetBackup and HP EVA arrays
Backups fail with the following warning message in the bpfis log:
WARNING: No credentials found for HP HSV
Credentials must be added for the EVA array by means of the NetBackup
Administration Console.
See
“Configuring NetBackup to access the EVA array”
on page 223.
248 Configuration of snapshot methods for disk arrays
About array troubleshooting
Troubleshooting IBM DS6000 and DS8000 arrays
This section provides explanations and recommended actions, as well as log entries that may help identify the problem.
Note the following important items:
■ Before you start a backup, the snapshot device (clone) must be visible
(unmasked) to the NetBackup client or alternate client.
■ For backup and Instant Recovery rollback restore: you must supply logon credentials that allow the NetBackup client to access the IBM array. For
NetBackup hosts not named in a policy (such as alternate clients), you must also configure NetBackup so that the host can access the credentials.
Backups may appear to succeed, but the bprd log on the server contains messages similar to the following:
09:02:17.999 [4292.3092] <2> is_disk_client_configured: db_cred_allowed(host1.enterprise.com, 1) failed: 227
09:02:17.999 [4292.3092] <2> read_text_file: is_disk_client_configured(host1.enterprise.com) failed: 227
09:02:17.999 [4292.3092] <2> process_request: read_text_file failed - status = client is not validated to use the server
(131)
Until credential access is enabled, a backup or a point-in-time rollback fails with NetBackup status 5.
See
“Configuring NetBackup to access the IBM DS6000 or DS8000 array”
on page 225.
See
“Configuring array access for NetBackup hosts not named in a policy”
on page 226.
Snapshot errors with IBM DS6000 and DS8000 arrays
(NetBackup status code 156)
Note these possible explanations:
Table 10-15 Issues encountered with Snapshot (NetBackup status code 156)
Issue Explanation/Recommended Action
The snapshot device (clone) is not visible (unmasked) to the NetBackup client or alternate client.
Make the clone device visible to the NetBackup client or alternate client before you retry the backup. Contact IBM technical support or refer to your IBM array documentation.
Configuration of snapshot methods for disk arrays
About array troubleshooting
249
Table 10-15 Issues encountered with Snapshot (NetBackup status code 156)
(continued)
Issue Explanation/Recommended Action
The snapshot device (clone) is also a source device in another device pair.
The following message may appear in the
/usr/openv/netbackup/logs/bpfis/ibmtsfi.log.date log:
Reconfigure source and clone devices so that the clone required for this backup is not a source device for another clone. Contact IBM technical support or refer to your IBM array documentation.
CMUN03041E mkflash: Copy Services operation failure: already a FlashCopy source
The snapshot device (clone) and source device are not of equal size.
The following message may appear in the
/usr/openv/netbackup/logs/bpfis/ibmtsfi.log.date log:
Reconfigure source and clone devices to be identical in size. Contact IBM technical support or refer to your IBM array documentation.
CMUN03049E mkflash: Copy Services operation failure: incompatible volumes
The source device is already recording enabled for
FlashCopy.
The following message may appear in the
/usr/openv/netbackup/logs/bpfis/ibmtsfi.log.date log:
Verify whether the source device has a FlashCopy relationship with some device other than the snapshot device (clone) specified in the policy. If a FlashCopy relationship exists with some other device, delete the relationship and start the backup again.
CMUN03027E mkflash: FlashCopy operation failure: action prohibited by current
FlashCopy state. Contact IBM technical support for assistance.
The IBM FlashCopy license is not installed.
The following message may appear in the
/usr/openv/netbackup/logs/bpfis/ibmtsfi.log.date log:
Install the FlashCopy license on the storage subsystem.
Contact IBM technical support or refer to your IBM array documentation.
CMUN03035E mkflash: Copy Services operation failure: feature not installed.
250 Configuration of snapshot methods for disk arrays
About array troubleshooting
Table 10-15 Issues encountered with Snapshot (NetBackup status code 156)
(continued)
Issue Explanation/Recommended Action
The FlashCopy relationship is not recording enabled.
The following message may appear in the
/usr/openv/netbackup/logs/bpfis/ibmtsfi.log.date log:
■
■ Make sure a FlashCopy relationship exists for the device pair.
If the FlashCopy relationship is not recording enabled, remove the FlashCopy relationship and then re-run the backup.
CMUN03027E resyncflash: FlashCopy operation failure: action prohibited by current
FlashCopy state. Contact IBM technical support for assistance
A FlashCopy relationship does not exist.
The following message may appear in the
/usr/openv/netbackup/logs/bpfis/ibmtsfi.log.date log:
Verify that a FlashCopy pair does not exist, and then re-execute the backup.
CMUN03027E resyncflash: FlashCopy operation failure: action prohibited by current
FlashCopy state. Contact IBM technical support for assistance.
A resynchronize operation was attempted on a FlashCopy pair that does not exist.
Incremental Copy is in progress.
The following message may appear in the
/usr/openv/netbackup/logs/bpfis/ibmtsfi.log.date log:
Allow the background copy or maintenance activity to complete. Then re-run the backup.
CMUN02498E resyncflash: The storage unit is busy.
This message can appear for the following reasons:
■
■
A background copy is in progress for the given pair of devices on the array.
Some maintenance activity is currently in progress on the array.
Troubleshooting IBM4000 arrays
These sections provide explanations and recommended actions, as well as log entries that may help identify the problem.
Configuration of snapshot methods for disk arrays
About array troubleshooting
251
Snapshot errors encountered with IBM4000 arrays (NetBackup status code 156)
The following table lists explanations and recommended actions for status code
156.
Table 10-16 Explanations and recommended actions for status code 156
Problem Description and recommended action for status code 156
The array does not have enough free space.
FlashCopy logical drives are created under the same logical array as is the base or primary logical drive. The storage subsystem might have free space, but if the logical array has insufficient space, the FlashCopy operation fails.
The following messages may appear in the /usr/openv/netbackup/logs/bpfis log:
23:44:48.007 [655588] <2> onlfi_vfms_logf: INF - snapshot services: ibmdsfi:Wed Mar 12
2008 23:44:48.007721 <Thread id - 1> FlashCopy could not be created. command [create
FlashCopyLogicalDrive baseLogicalDrive="angela_javelin_4" userLabel="angela_javelin_4_flcp_4";].23:44:48.012 [655588] <2> onlfi_vfms_logf: INF snapshot services: ibmdsfi: FlashCopy creation failed for source volume angela_javelin_4 on storage unit ibmds4700.
In addition, the following messages may appear in
/usr/openv/netbackup/logs/bpfis/ibmdsfi.log.date:
Mon Mar 31 2008 14:25:23.036588 <Pid - 1065104 / Thread id - 1> FlashCopy could not be created. command [create FlashCopyLogicalDrive baseLogicalDrive="drive-claix11-1" userLabel="drive-claix11-1_flcp";]. Mon Mar 31 2008 14:25:23.037164 <Pid - 1065104 /
Thread id - 1> OUTPUT=[Unable to create logical drive "drive-claix11-1_flcp" using the
Create FlashCopy Logical Drive command at line 1. Error - The operation cannot complete because there is not enough space on the array. The command at line 1 that caused the error is: create FlashCopyLogicalDrive baseLogicalDrive="drive-claix11-1" userLabel="drive-claix11-1_flcp";
Recommended action: Make sure that the array has enough space available for the snapshot.
The maximum number of FlashCopies (4) already exist on the array.
The following messages may appear in /usr/openv/netbackup/logs/bpfis/ibmdsfi.log.date:
Mon Mar 31 2008 14:25:23.036588 <Pid - 1065104 / Thread id - 1> FlashCopy could not be created. command [create FlashCopyLogicalDrive baseLogicalDrive="drive-claix11-1" userLabel="drive-claix11-1_flcp";]. Mon Mar 31 2008 14:25:23.037164 <Pid - 1065104 /
Thread id - 1> OUTPUT=[Could not create a flashcopy logical drive using the Create
FlashCopyLogicalDrive command at line 1. Error 129 - The operation cannot complete because the maximum number of flashcopy logical drives have been created for this base logical drive.
Recommended action: Delete any FlashCopies that NetBackup did not create.
252 Configuration of snapshot methods for disk arrays
About array troubleshooting
Table 10-16 Explanations and recommended actions for status code 156
(continued)
Problem Description and recommended action for status code 156
The Access Logical
Drive is not mapped for the NetBackup client or alternate client at LUN 31 or 7.
On the IBM DS4000, the Access Logical Drive communicates with the storage subsystem.
Any client that is connected to and needs to communicate with the storage subsystem should have an Access Logical Drive mapped to it. If an Access Logical Drive is not mapped to the client, the client is unable to communicate with the array. As a result, any NetBackup client operation involving the array fails.
Recommended action: Create and map an Access Logical Drive. Contact IBM technical support or refer to your IBM array documentation.
The DAR driver is not functional.
Recommended action: Make sure that the RDAC package is installed on the AIX host.
For further reference on IBM System Storage DS4000
The following IBM documents may be helpful:
■ IBM System Storage DS4000 Series and Storage Manager http://www.redbooks.ibm.com/abstracts/sg247010.html
■ IBM System Storage DS Storage Manager Version 10.30: Copy Services User’s
Guide http://www.filibeto.org/unix/aix/lib/hardware/ds4800/copy-services-ug-gc53113600.pdf
■ IBM System Storage DS4000 Storage Manager Version 9 Installation and Support
Guide
Troubleshooting Hitachi arrays
This section provides explanations and recommended actions, as well as log entries that may help identify the problem.
Note the following important items:
■ RAID Manager version 01-12-03/04 or later is required.
See
“Determining the current RAID Manager version”
on page 236.
■ Before you start a backup, the snapshot device (clone LUN or snapshot LUN) must be visible (unmasked) to the NetBackup client or alternate client.
■ For the NetBackup policy Snapshot Resource configuration, specify device IDs in decimal and without leading zeros.
For example, if your source device ID is 0100 and the snapshot device ID is
0101, enter 100 and 101 in the Snapshot Resources dialog box.
Configuration of snapshot methods for disk arrays
About array troubleshooting
253
See
“Configuring a NetBackup policy for Hitachi_ShadowImage or
on page 239.
NetBackup policy validation fails with Hitachi arrays
Note these possible explanations:
Table 10-17 NetBackup policy validation fails
Issue Explanation/Recommended Action
Look for the following error in the
/usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log:
Make sure that the RMLIB 64-bit library is installed. This requirement applies when you upgrade from a 6.5.x
system (requires 32-bit RMLIB) to a 7.1 system, and when you install a fresh 7.1 system.
Library RMLIB init failed
The Hitachi command device is not unmasked.
See the sample log messages in the next row.
Refer to Hitachi documentation for creating and unmasking command devices.
The Hitachi command device is unmasked but is not visible to client, or the enclosure ID specified in the policy’s Snapshot Resources is invalid.
Make sure that the command device is recognized by the operating system and that the enclosure ID is entered correctly in the policy's Snapshot Resources.
The
/usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log may contain messages similar to the following:
To determine if the command device is recognized by the operating system, try device discovery commands such as the following:
Fri Mar 21 2008 16:26:46.431046 <Pid - 9477
/ Thread id - 1> Entering Function delayedInit [110, providers/hitachi/hitachi_plugin.cpp] Fri
Mar 21 2008 16:26:49.173893 <Pid - 9477 /
Thread id - 1> <Device name="/dev/rdsk/c4t50060E801029F700d2s6" devfsadm cfgadm -al
A log message for the enclosure ID would include an entry such as the following: udid="UDID##HITACHI##HDS##75040816##3" bus="0" target="0" lun="0" vendor="HITACHI" product="DF600F-CM" /> Fri Mar 21 2008
16:26:49.174493 <Pid - 9477 / Thread id -
1> Exiting Function delayedInit [110, providers/hitachi/hitachi_plugin.cpp] c3t50060E801029F700d28
<HITACHI-DF600F-CM-0000 cyl 52 alt 2 hd 50 sec 768> which shows that the device is visible as c3t50060E801029F700d28.
If the delayedInit message does not include at least one entry for the enclosure ID that was entered in the policy’s Snapshot Resources, the command device is not unmasked or is not visible to NetBackup client (host).
254 Configuration of snapshot methods for disk arrays
About array troubleshooting
Table 10-17 NetBackup policy validation fails (continued)
Issue Explanation/Recommended Action
A mismatch exists between the policy’s snapshot method and the type of LUNs specified for the Snapshot Devices.
For example, if you select the Hitachi_ShadowImage method but specify snapshot LUNs instead of clone LUNs for the Snapshot Devices, an error occurs.
Specify the correct snapshot method or snapshot devices.
See the sample log messages in the next bullet.
A disk pair was not created for the source device and snapshot device specified in the NetBackup policy’s
Snapshot Resources.
The
/usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log may contain messages similar to the following.
Set up a disk pair (primary and secondary) for the source device and snapshot device that are specified in the policy’s Snapshot Resources. Refer to the Hitachi documentation.
If the snapshot method is Hitachi_CopyOnWrite:
Fri Mar 21 2008 16:26:49.173893 <Pid - 9477
/ Thread id - 1> HITACHI_FIM_SNAPSHOT not supported for 10
If the snapshot method is Hitachi_ShadowImage:
Fri Mar 21 2008 16:26:49.173893 <Pid - 9477
/ Thread id - 1> HITACHI_FIM_SHADOW_IMAGE not supported for 10
Configuration of snapshot methods for disk arrays
About array troubleshooting
255
Table 10-17 NetBackup policy validation fails (continued)
Issue Explanation/Recommended Action
In the policy’s Snapshot Resources, the device identifier for the source device or snapshot device is invalid.
The
/usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log may contain messages similar to the following:
Recommended action: Make sure that the identifiers are correctly entered in the policy’s Snapshot Resources.
Specify source and snapshot IDs without leading zeros.
See
“Configuring a NetBackup policy for
Hitachi_ShadowImage or Hitachi_CopyOnWrite”
on page 239.
Fri Mar 21 2008 16:26:49.173893 <Pid - 9477
/ Thread id - 1> getrminfo failed. Fri Mar
21 2008 16:26:49.173893 <Pid - 9477 /
Thread id - 1> operation failed with error number <> with message <msg>'.
The above message may indicate that a device ID in the policy’s Snapshot Resources is incorrect or does not exist.
For example, if the specified snapshot device ID does not exist:
Mon May 12 2008 21:32:32.088876 <Pid - 8040
/ Thread id - 1> getrminfo is called for
'9999'. Mon May 12 2008 21:32:32.089736
<Pid - 8040 / Thread id - 1> getrminfo failed. Mon May 12 2008 21:32:32.090003
<Pid - 8040 / Thread id - 1> operation failed with error number '-1' with message
'[EL_CMDRJE] An order of the control command rejected.'.
The RAID Manager library libsvrrm.so software is not installed in the /usr/lib/ directory.
Recommended action: Install the RAID Manager package in /usr/lib/. See the Hitachi documentation.
The installed version of RAID Manager library libsvrrm.so
is not supported.
Recommended action: Look for the Library RMLIB version message in the
/usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log.
See
“Determining the current RAID Manager version”
on page 236.
Backup or restore or image expiration fails with Hitachi arrays
The following table lists possible explanations:
256 Configuration of snapshot methods for disk arrays
About array troubleshooting
Issue
Table 10-18 Backup or restore or image expiration fails
Explanation/Recommended Action
These messages indicate that the instance number is not available. A problem may exist with the instance number management logic.
■
■
Remove the following file.
/usr/openv/lib/vxfi/cachefiles/hitachi/
UDID##HITACHI##HDS##enclosure id##*
The enclosure id is the array's serial number that is specified in the policy’s Snapshot Resources.
Gather the appropriate Hitachi logs and contact
Symantec customer support for NetBackup.
Configuration of snapshot methods for disk arrays
About array troubleshooting
257
Table 10-18 Backup or restore or image expiration fails (continued)
Issue
A problem occurred that involved the Hitachi instance number. For example, the Hitachi snapshot provider did not receive the instance number for the command device.
The instance number is needed to connect to the array.
The
/usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log contains the following message:
Couldn't get instance no failed with message ....
The log may contain the following additional messages:
Fri Mar 21 2008 16:26:49.818233 <Pid - 9477
/ Thread id - 1> Entering Function attachCmd [156, providers/hitachi/hitachi_rmlibintf.cpp]
Fri Mar 21 2008 16:26:49.173893 <Pid - 9477
/ Thread id - 1> attachcmddev is called with cmd dev /dev/dsk/c1t0d0s2 and instance number 0. Fri Mar 21 2008 16:26:49.818308
<Pid - 9477 / Thread id - 1> Exiting
Function attachCmd [156, providers/hitachi/hitachi_rmlibintf.cpp]
The attachcmddev message should list the Hitachi command device (for the enclosure ID that was specified in the policy) and the instance number. If the Hitachi command device is not included in the message, then the instance number was not received. A limited number of instance numbers are allowed per command device. If the maximum number of processes is using the same command device, no more instance numbers are available.
This situation may indicate a problem with the instance number management logic of the Hitachi provider.
Note also the following potential messages:
Fri Mar 21 2008 16:26:49.818233 <Pid - 9477
/ Thread id - 1> Entering Function attachCmd [156, providers/hitachi/hitachi_rmlibintf.cpp]
Fri Mar 21 2008 16:26:49.173893 <Pid - 9477
/ Thread id - 1> Couldn't get instance no failed with message '%s'. Fri Mar 21 2008
Explanation/Recommended Action
258 Configuration of snapshot methods for disk arrays
About array troubleshooting
Table 10-18 Backup or restore or image expiration fails (continued)
Explanation/Recommended Action Issue
16:26:49.818308 <Pid - 9477 / Thread id -
1> Exiting Function attachCmd [156, providers/hitachi/hitachi_rmlibintf.cpp]
Another example message is the following:
Fri Mar 21 2008 16:26:49.173893 <Pid - 9477
/ Thread id - 1> Couldn't get instance no failed with message 'Instance No Exhausted, couln't reclaim giving up'
The default array controller of the source device is not the same as the controller of the snapshot device. Use the Storage Navigator interface to verify.
Recommended action: Make sure that the clone (or snapshot) device has the same default controller as the source device. See the Hitachi documentation.
Advertisement
Key features
- Instant Recovery
- Off-host backup
- FlashBackup
- RealTime
- Block level incremental backup (BLIB)
- Support for Cluster Volume Manager Environments (CVM)
- Support for multiple disk arrays
- NAS snapshot