Release Notes: Emc Snapview and Admsnap
Release Notes: Emc Snapview and Admsnap
Release Notes: Emc Snapview and Admsnap
Release Notes
P/N 300-002-132
REV A01
December 15, 2004
Please read these release notes completely before installing or using the
software.
Topics include
Product Descriptions
Product Descriptions
SnapView
EMC SnapView is a storage-system-based software application that
allows you to create a copy of a LUN by using either clones or snapshots.
You can use the clone or snapshot for decision support, system backups,
data modeling, software application testing, or as a base for temporary
operations on the production data without damaging the original data
on the source LUN.
A clone is an actual copy of a LUN and it takes time to create. A
snapshot is a virtual point-in-time copy of a LUN and takes only seconds
to create. Depending on your application needs, you can create clones,
snapshots and snapshots of clones.
Admsnap
The admsnap program runs on host systems in conjunction with
SnapView in the SPs, and lets you start, activate, deactivate, and stop
SnapView sessions. All admsnap commands are sent to the SP through
the Fibre Channel bus.
The admsnap utility is an executable program that you can run
interactively or via script.
For all Microsoft Windows and UNIX platforms, flush cached data
from the host before you start a session. Failure to do this will result in
an inconsistent or unusable point-in-time copy.
The admsnap clone commands can activate and deactivate a clone, and,
for a Windows platform, flush data from a source LUN to its clone,
bringing the source and clone into the synchronized state.
SnapView Rollback
SnapView rollback is a feature that allows the system administrator to
unsnap a SnapView source LUN, instantly restoring its contents from
a different point-in-time version. Any persistent SnapView session can
be rolled back, in a way that appears instantaneous to host computers,
without destroying any of the source LUNs sessions or snapshots. The
production host's view of source LUN contents changes immediately,
though actual data copying back to source LUNs runs invisibly in the
background at a user-controllable speed.
The source LUNs that are the target of a rollback operation remain
accessible and accept host I/O during and after the rollback; any new
data written from the host supersedes data being rolled back from the
session.
A rollback operation is non-destructive: the source LUNs other sessions
are unaffected by the rollback and can still be accessed via their snapshot
LUNs. The session being rolled back is also unaffected, except that any
snapshot associated with it becomes temporarily inaccessible to host I/O
for the duration of the rollback operation.
Hardware
SnapView software is supported on CX300, CX400, CX500, CX600,
CX700 and FC4700-Series storage systems only. Admsnap is supported
on a host running any of the following operating systems: IBM AIX,
Hewlett Packard HP-UX, SGI IRIX, Linux, Novell NetWare, Sun
Solaris, Windows 2000, Windows NT, or Windows Server 2003.
Storage-System Software
The following table lists the revisions of Access Logix software that are
compatible with this release.
Storage-System Type
CX700
02.06.700.5.xxx or higher
CX600
02.06.600.5.xxx or higher
CX500
02.06.500.5.xxx or higher
CX400
02.06.400.5.xxx or higher
CX300
02.06.300.5.xxx or higher
FC4700-Series
8.51.5x or higher
Operating Systems
Please refer to the EMC Support Matrix for a complete listing of
operating systems supported by SnapView, VSS, and admsnap.
Installation Notes
Installation Notes
SnapView
The SP names of the CLARiiON array must be unique for the NDU of
the SnapView software to be successful.
The administrator must set up a global user account for SYSTEM (all
capitals) on all arrays that are attached to the host.
Detail
[87316]
Problem Description
Detail
Detail
Frequency of occurrence: Frequent
Prevention/Resolution:
The SP on which the session is stuck must be rebooted to
clear this condition.
Problem Description
Detail
10
Problem Description
Detail
Platform-Specific Problems
Problem Description
Detail
[75026]
11
12
Problem Description
Detail
Configuration Limitations
The configuration guidelines for SnapView 02.03.5.022 are listed in the
following table.
Parameter
CX500 or CX400
CX300
50 maximum
(includes source LUN and
Primary or Secondary
MirrorView images)
50 maximum
(includes source LUN
and Primary or
Secondary MirrorView
images)
Clones
Per Storage System
8 maximum
8 maximum
8 maximum
Clone Groups
50 maximum
25 maximum
25 maximum
2 required
2 required
2 required
300 maximum
150 maximum
100 maximum
8 maximum
8 maximum
8 maximum
8 maximum
8 maximum
8 maximum
100 maximum
50 maximum
25 maximum
SnapView Sessionsa
Per Source LUN
Reserved Pool LUNs
Per Storage System
a. The limits for snapshots and sessions include SnapView snapshots or SnapView sessions and any reserved snapshots or reserved sessions
used in another application such as SAN Copy.
13
Technical Notes
Technical Notes
This section contains information that will help with the installation, use,
and management of the storage system. It provides generic information
that applies to all platforms and platform-specific information, except for
Hewlett Packard Tru64 systems.
14
Technical Notes
15
Technical Notes
16
Technical Notes
Admsnap with DMP software. If you install and use the DMP
software for Solaris, you must use persistent SnapView sessions.
DMP-installed systems will sometimes generate I/O requests to both
SPs for a LUN. For SnapView, this will cause a session to trespass
when the non-owning SP receives the I/O request. A persistent
session will survive the trespass operation and I/O will continue
normally. Non-persistent sessions will terminate. Also, for admsnap
operations that use the -o <pathname> parameter, you can also use
the /dev/vx/rdmp/cXtXdXsX pathnames as arguments.
HP-UX
17
Technical Notes
2.
Unmount the file system from the volume group, using the
following command:
umount filesystem-name
Deactivate and export the volume group, by issuing the
following commands:
vgchange -a n volume-name
vgexport volume-name
Use the admsnap start command to start a session on the
snapshot LUN.
admsnap start -s session-name -o /dev/rdsk/cNtNdN
where cN specifies the HBA number; tN specifies the SP
number, and dN specifies the LUN number; for example
c0t1d12.
3.
4.
5.
6.
7.
vgchange -a y volume-name
Once the snapshot is activated, mount the volume group to a
file system, using the following format:
mount /dev/volume-name/lvol1 /filesystem
18
Technical Notes
SnapView. The reboot of the Linux host may be slow if there are
deactivated snapshots in the hosts storage group. Activating the
snapshots or removing them from the storage group will allow the
reboot to complete normally.
Irix
Linux
NetWare
19
Technical Notes
Solaris
20
Technical Notes
The operations that are not supported in the admsnap 1.50 release for
Solaris, but may be added in a future release, are as follows:
21
Technical Notes
When ready to resume I/O to the disk, use the Microsoft Cluster
Administrator to bring the Disk Group(s) back online by rightclicking the Disk Group and selecting Bring Online.
Create a Clone Group with the source and clone LUNs of equal
size. For this example, the drive letter assigned to the source
LUN on the production host is H:.
2.
3.
4.
5.
6.
7.
8.
9.
Synchronize the clone LUN. This operation will update the clone
LUN with the changes made to the source LUN on the
production host.
22
Technical Notes
Admsnap and drive letter restriction. Admsnap does not allow the
use of drive letters A:, B:, C:, and D: with o and d options on
admsnap activate or admsnap deactivate commands. If A, B, C or D
drive letter is used, then only the physical drive will be activated and
no drive letter will be assigned.
23
Technical Notes
Name: LunRescan
Type: REG_MULTI_SZ
Value: <you can leave this null>
Added to key:
\\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk
24
Technical Notes
Output and Return Codes. The following changes have been made
to the Windows 2000 and Windows Server 2003 admsnap. These
changes affect the text output and return codes (exit codes) of the
command.
25
Technical Notes
26
Technical Notes
27
Technical Notes
28
Documentation
Documentation
The following documents apply to this product release and are located
on the SnapView documentation CD (P/N 068090623).
Part Number
Publication
069001180
069001181
069001193
Documentation Updates
This section describes changes to the SnapView online help, the EMC
SnapView Version 2.X for Navisphere 6.X Administrators Guide
(P/N 069001180), the EMC SnapView Version 2.X Installation Guide, and
the EMC SnapView Version 2.X Command Line Interfaces Reference (P/N
069001181).
Installing the SnapView UI
Add the following information to the SnapView Installation Guide:
The SnapView UI is installed on all CX300, CX500, and CX700 storage
systems at the factory.
29
Documentation Updates
SnapView Limits
In the SnapView Administrators and Reference Guides, replace the
SnapView Configuration Guidelines table on page 1-11 with the table
below:
Parameter
CX500 or CX400
CX300
50 maximum
(includes source LUN
and Primary or
Secondary MirrorView
images)
50 maximum
(includes source LUN
and Primary or
Secondary MirrorView
images)
8 maximum
8 maximum
8 maximum
50 maximum
25 maximum
25 maximum
2 required
2 required
2 required
300 maximum
150 maximum
100 maximum
8 maximum
8 maximum
8 maximum
8 maximum
8 maximum
8 maximum
100 maximum
50 maximum
25 maximum
Clones
Per Storage System
SnapView Sessionsa
Per Source LUN
Reserved Pool LUNs
Per Storage System
a. The limits for snapshots and sessions include SnapView snapshots or SnapView sessions and any reserved snapshots or
reserved sessions used in another application such as SAN Copy.
30
Software Media
Software Media
The following table lists the applicable software media for this product
release:
Product
CD Part Number
Description
SnapView
068090519
Admsnap
068090628
HP-UX
IRIX
Linux 2.4
NetWare
Solaris
Windows 2000
Windows NT
31
Worldwide:
(508) 497-7901
Follow the voice menu prompts to open a service call, then select
CLARiiON Product Support.
Sales and Customer Service Contacts
For the list of EMC sales locations, please access the EMC home page at:
http://www.emc.com/contact/
For additional information on the EMC products and services available
to customers and partners, refer to the EMC Powerlink website at:
http://powerlink.emc.com
For CLARiiON documentation, after you log in to Powerlink, select
Support > Document Library.
32