10-26-2013
Just use zpool mirror/attach/detach.
Add a with same size or bigger from EVA storage in tibcoapp pool via attach.
After the resilver is complete, detach the EMC disk.
No need for SAN storage replication techniques.
Hope that helps
Regards
Peasant.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
We currently have a Solaris box connected to a Clariion storage system that is utilising DMP for path failover. I would prefer to use EMC's Powerpath and was wondering if the two can coexist?
Basically, I am struggling to find any documentation on the subject and was wonder if anyone can give me... (2 Replies)
Discussion started by: aaron2k
2 Replies
2. Linux
Hi all,
Currently i am involved in developing a device driver for a custom hardware.
My linux stack already has the sysfs directory structure
/sys/class/hwmon/
My need is that, while loading my device driver i need to create a "xyz" sysfs directory inside hwmon sysfs directory as... (0 Replies)
Discussion started by: cbalu
0 Replies
3. Solaris
Friends,
Could u please clarify how does a Solaris 10 machine recognize a SATA hard disk, SATA CD/DVD drives.
Will it recognize it like a SCSI? eg.c0t0d0 or like ide ? eg.c0d0
thank u. (11 Replies)
Discussion started by: saagar
11 Replies
4. Red Hat
Hi ,
I have a redhat 5.3 server which has 2 vg.. one is rootvg in local harddisk and another one is applicationvg in SAN.. When I reboot the server , EMC powerpath driver is not starting up automatically. Hence applicationvg is not mounting properly. Therefore I need to unmount it manually and... (4 Replies)
Discussion started by: Makri
4 Replies
5. Emergency UNIX and Linux Support
Dear All,
I was having powerpath 5.2 on SUN server with SVM connected to CLARIION box.Please find the following output :
root # powermt display dev=all
Pseudo name=emcpower3a
CLARiiON ID=CK200073400372
Logical device ID=60060160685D1E004DD97FB647BFDC11
state=alive; policy=CLAROpt;... (1 Reply)
Discussion started by: Reboot
1 Replies
6. Solaris
I saved one of my zfs snapshot on the remote machine with following command. And now i want to restore the same snapshot to original server how can i receive it on the original server from backup server.
#zfs send rpool/ROOT/sol10_patched@preConfig | ssh x.x.x.x zfs receive... (1 Reply)
Discussion started by: fugitive
1 Replies
7. AIX
I'm trying to auto-mount EMC Symmetrix BCV device at boot.
but having problem making BCV available.
I put script called mkbcv to the inittab and engineer suggested to add
120 sec sleep between cfgmgr so I did that also.
My mkbcv script seems to be working fine, it says "hdisk4 Available" ... (1 Reply)
Discussion started by: shuhei365
1 Replies
8. Linux
Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3.
I did sucessfully managed to create the LUN on the Storage (the LUN is named DBLNX25EC_TST), after doing the following process:
echo "1" > /sys/class/fc_host/host<n>/issue_lip
and
echo "- - -" >... (10 Replies)
Discussion started by: Zarnick
10 Replies
9. Solaris
It seems like I lost one path on my Solaris-11 box. But I want to make sure before going to Storage team, if issue is from OS side or Storage side. Storage team is able to see that only one wwwn is looged in their switch. I am not at server's physical location. What does below output says ? I... (0 Replies)
Discussion started by: solaris_1977
0 Replies
10. Solaris
Hello All
I’ve made the decision to switch my storage server from FreeNAS to Solaris. I opted to use FreeNAS as it has ZFS and until BTRFS is stable, it’s the best option (IMHO) for backup and network storage.
The switch was facilitated by the USB stick that FreeNAS was on got lost during a... (1 Reply)
Discussion started by: BlueDalek
1 Replies
pm(9P) Kernel Properties for Drivers pm(9P)
NAME
pm - Power Management properties
DESCRIPTION
The pm-hardware-state property can be used to influence the behavior of the Power Management framework. Its syntax and interpretation is
described below.
Note that this property is only interpreted by the system immediately after the device has successfully attached. Changes in the property
made by the driver after the driver has attached will not be recognized.
pm-hardware-state is a string-valued property. The existence of the pm-hardware-state property indicates that a device needs special han-
dling by the Power Management framework with regard to its hardware state.
If the value of this property is needs-suspend-resume, the device has a hardware state that cannot be deduced by the framework. The frame-
work definition of a device with hardware state is one with a reg property. Some drivers, such as SCSI disk and tape drivers, have no reg
property but manage devices with "remote" hardware. Such a device must have a pm-hardware-state property with a value of needs-suspend-
resume for the system to identify it as needing a call to its detach(9E) entry point with command DDI_SUSPEND when system is suspended, and
a call to attach(9E) with command DDI_RESUME when system is resumed. For devices using original Power Management interfaces (which are now
obsolete) detach(9E) is also called with DDI_PM_SUSPEND before power is removed from the device, and attach(9E) is called with
DDI_PM_RESUME after power is restored.
A value of no-suspend-resume indicates that, in spite of the existence of a reg property, a device has no hardware state that needs saving
and restoring. A device exporting this property will not have its detach() entry point called with command DDI_SUSPEND when system is sus-
pended, nor will its attach() entry point be called with command DDI_RESUME when system is resumed. For devices using the original (and now
obsolete) Power Management interfaces, detach(9E) will not be called with DDI_PM_SUSPEND command before power is removed from the device,
nor attach(9E) will be called with DDI_PM_RESUME command after power is restored to the device.
A value of parental-suspend-resume indicates that the device does not implement the detach(9E) DDI_SUSPEND semantics, nor the attach()
DDI_RESUME semantics, but that a call should be made up the device tree by the framework to effect the saving and/or restoring of hardware
state for this device. For devices using original Power Management interfaces (which are now obsolete), it also indicates that the device
does not implement the detach(9E) DDI_PM_SUSPEND semantics, nor the attach(9E) DDI_PM_RESUME semantics, but that a call should be made up
the device tree by the framework to effect the saving and/or restoring the hardware state for this device.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+--------------------------+--------------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------------+--------------------------------+
|Interface stability |Evolving |
+--------------------------+--------------------------------+
SEE ALSO
power.conf(4), pm(7D), attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm-components(9P)
Writing Device Drivers
SunOS 5.10 20 Jan 2004 pm(9P)