Start a Conversation

Unsolved

This post is more than 5 years old

614

January 15th, 2013 04:00

Using logical device names for admsnap

AX4-5 FC, RedHat Linux 6.3, admsnap 2.30.0.0.0-1

Is it possible to use the logical device names (as reported in powerpath) rather than physical device names (such as /dev/empowera) when specitying LUN's with admsnap ?

The docs refer to "bieng able to substitute drive letters or file-system names" in lieu of , but EMC support are unable to tell we exactly what "file-system names" refer to here.

This is what I get when I try:

# /usr/admsnap/admsnap start -s Galdyn_Wednesday -o Galdyn

Error looking up object "Galdyn".

Error:  0x3E02000C (The specified object was not found)

The relavent output from from powermt is:

Pseudo name=emcpowerr

CLARiiON ID=CK200101300170 [atlas.jhi.uclan.ac.uk]

Logical device ID=60060160A8802900BE4CE23C883CE211 [Galdyn]

state=alive; policy=CLAROpt; priority=0; queued-IOs=0;

Owner: default=SP A, current=SP A    Array failover mode: 1

==============================================================================

--------------- Host ---------------   - Stor -   -- I/O Path --  -- Stats ---

###  HW Path               I/O Paths    Interf.   Mode    State   Q-IOs Errors

==============================================================================

   1 qla2xxx                  sdd       SP B0     active  alive       0      0

   1 qla2xxx                  sds       SP A0     active  alive       0      0

Thanks

4.5K Posts

January 15th, 2013 12:00

The admsnap software supports native device names and PowerPath pseudo-device names. If you use a PowerPath pseudo-device name, you can add this device name to the etc/fstab file (for Linux) or to the etc/vfstab file (for Solaris).

Linux Server (UNIX)

admsnap start -s session1 -o /dev/sdc (for a file system)

admsnap start -s session1 -o /database (for a file system)

Does this help?

glen

5 Posts

January 17th, 2013 08:00

Thanks Glen - that does exactly what is required. Because the source LUN's failover between cluster nodes and can only ever be mounted on one node at a time i didn't want to put them in vfstab. But i guess with the "no automatic" mount option that will be safe.

I guess that also will work with the naming of the snapshots for activating and deactiavting too.

No Events found!

Top