Sponsored Content
Operating Systems Solaris How to create mirror disk in solaris machine? Post 302426647 by Lespaul20 on Wednesday 2nd of June 2010 12:16:55 PM
Old 06-02-2010
I'd also recommend ZFS.
This User Gave Thanks to Lespaul20 For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

Disk Mirror in Solaris 9 via Solaris Volume Manager

Hello, I am trying to do mirror in solaris 9. I have total 0-7 disks 4 5 6 7 0 1 2 3 Drive 0 and Drive 4 = Boot Drives Need to Mirror following drives. Drive 1 and Drive 5 = Need to mirror Drive 1 was mounted on: /prod1, /prod2, /prod3, /prod4, /prod5. Then i... (3 Replies)
Discussion started by: deal732
3 Replies

2. Solaris

Solaris 10 - breaking of mirror and change new hard disk

Hi, am a newbie at solaris. Need advice and help on this. 1) How do I break the mirror between 2 hard disks. (wish to keep 1 good hard disk as backup) 2) After remove 1 hard disk and put in new hard disk, how do I initialise or fomat the new hard disk? 3) How do I put back the backup... (3 Replies)
Discussion started by: chongkls77
3 Replies

3. Solaris

Create a logical volume from a mirror and single disk?

I have two 72GB disks that are mirrored and mounted (/backup). I have a 18GB drive in an array I just attached to the server, which is running Solaris 9. I need to create a new logical volume partition and make the existing mirror device (/dev/md/dsk/d34) and the array's 18GB drive a member of... (3 Replies)
Discussion started by: dotcom75
3 Replies

4. Shell Programming and Scripting

Disk Space availability on solaris machine

Hi, I have a question regarding finding free space on the disk of a solaris machine. Many mount points are available in my machine. Right now i am using df -b option to get the free disk space available. I have an assignment to check free space on the disk. I pass the directory as a... (3 Replies)
Discussion started by: raghu.amilineni
3 Replies

5. Solaris

x86 Sun Machine and Solaris Soft Mirror

Hi everyone, Normally it always easier in Sparc machine, i can set or manually use the boot-device in NVram to boot the mirrored disk. However I have a big trouble about x86 mirror for a long time. I have been doing anything i can: search document, google, ask the others. Recently i did as... (5 Replies)
Discussion started by: tien86
5 Replies

6. Solaris

Solaris Volume Manager: Break Mirror and use to make a 2nd machine

Hello: I have a machine built on 2 drives and mirrors have been created to a second set of 2 drives (4 total) on the same platform. SVM. Might anyone provide guidance to create a second machine by breaking the mirrored set, moving the two mirrors (2) to another machine (same platform type),... (1 Reply)
Discussion started by: 4dailyrunner
1 Replies

7. Solaris

Create a boot disk mirror on Solaris 10 x86

I’m setting up a boot disk mirror on Solaris 10 x86. I’m used to doing it on SPARC, where you can copy the partition table using fmthard. My x86 boot disk has 2 primary partitions, a Solaris one and a diagnostic one. Is there a way to copy those 2 primary partitions to the second disk without... (6 Replies)
Discussion started by: TKD
6 Replies

8. Solaris

Solaris patching using mirror disk backup? need help!

hi friends, need help.. it is my first time patching using mirror disk backup approach, not so sure about the steps :confused: how do you detach, patch it, boot it and reattach it ? any kind soul here can advise ? thanks in advance..:) below is the information from my machine: Filesystem ... (3 Replies)
Discussion started by: Exposure
3 Replies

9. HP-UX

What is the difference between DRD and Root Mirror Disk using LVM mirror ?

what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies

10. Solaris

Solaris 9 x86 check disk mirror status

We have Proliant DL380 G2 running Solaris 9 x86 There are 6 physical disks installed which I believe are mirrored at hardware level to 3 sets to present 3 disks to the OS. Is there any way to check the mirror status at OS level ? I am guessing not and it may need a trip to site as we have no... (4 Replies)
Discussion started by: frustrated1
4 Replies
SUNW.HAStoragePlus(5)					     Sun Cluster Miscellaneous					     SUNW.HAStoragePlus(5)

NAME
SUNW.HAStoragePlus - resource type that enforces dependencies between Sun Cluster device services, file systems, and data services DESCRIPTION
SUNW.HAStoragePlus describes a resource type that enables you to specify dependencies between data service resources and device groups, cluster file systems, and local file systems. Note - Local file systems include the UNIX File System (UFS), Quick File System (QFS), Veritas File System (VxFS), and Solaris ZFS (Zettabyte File System). This resource type enables you to bring data services online only after their dependent device groups and file systems are guaranteed to be available. The SUNW.HAStoragePlus resource type also provides support for mounting, unmounting, and checking file systems. Resource groups by themselves do not provide for direct synchronization with disk device groups, cluster file systems, or local file sys- tems. As a result, during a cluster reboot or failover, an attempt to start a data service can occur while its dependent global devices and file systems are still unavailable. Consequently, the data service's START method might time out, and your data service might fail. The SUNW.HAStoragePlus resource type represents the device groups, cluster, and local file systems that are to be used by one or more data service resources. You add a resource of type SUNW.HAStoragePlus to a resource group and set up dependencies between other resources and the SUNW.HAStoragePlus resource. These dependencies ensure that the data service resources are brought online after the following situa- tions occur: 1. All specified device services are available (and collocated, if necessary). 2. All specified file systems are checked and mounted. You can also use the SUNW.HAStoragePlus resource type to access a local file system from a non-global zone. EXTENSION PROPERTIES
The following extension properties are associated with the SUNW.HAStoragePlus resource type: AffinityOn Specifies whether a SUNW.HAStoragePlus resource needs to perform an affinity switchover for all global devices that are defined in the GlobalDevicePaths and FilesystemMountPoints extension properties. You can specify TRUE or FALSE. Affinity switchover is set by default, that is, AffinityOn is set to TRUE. The Zpools extension property ignores the AffinityOn extension property. The AffinityOn extension property is intended for use with the GlobalDevicePaths and FilesystemMountPoints extension properties only. When you set the AffinityOn extension property to FALSE, the SUNW.HAStoragePlus resource passively waits for the specified global ser- vices to become available. In this case, the primary node or zone of each online global device service might not be the same node or zone that is the primary node for the resource group. The purpose of an affinity switchover is to enhance performance by ensuring the colocation of the device groups and the resource groups on a specific node or zone. Data reads and writes always occur over the device primary paths. Affinity switchovers require the poten- tial primary node list for the resource group and the node list for the device group to be equivalent. The SUNW.HAStoragePlus resource performs an affinity switchover for each device service only once, that is, when the SUNW.HAStoragePlus resource is brought online. The setting of the AffinityOn flag is ignored for scalable services. Affinity switchovers are not possible with scalable resource groups. FilesystemCheckCommand Overrides the check that SUNW.HAStoragePlus conducts on each unmounted file system before attempting to mount it. You can specify an alternate command string or executable, which is invoked on all unmounted file systems. When a SUNW.HAStoragePlus resource is configured in a scalable resource group, the file-system check on each unmounted cluster file system is omitted. The default value for the FilesystemCheckCommand extension property is NULL. When you set this extension property to NULL, Sun Cluster checks UFS or VxFS by issuing the /usr/sbin/fsck -o p command. Sun Cluster checks other file systems by issuing the /usr/sbin/fsck com- mand. When you set the FilesystemCheckCommand extension property to another command string, SUNW.HAStoragePlus invokes this command string with the file system mount point as an argument. You can specify any arbitrary executable in this manner. A nonzero return value is treated as an error that occurred during the file system check operation. This error causes the START method to fail. When you do not require a file system check operation, set the FilesystemCheckCommand extension property to /bin/true. FilesystemMountPoints Specifies a list of valid file system mount points. You can specify global or local file systems. Global file systems are accessible from all nodes or zones in a cluster. Local file systems are accessible from a single cluster node or zone. Local file systems that are managed by a SUNW.HAStoragePlus resource are mounted on a single cluster node or zone. These local file systems require the underlying devices to be Sun Cluster global devices. These file system mount points are defined in the format paths[,...]. You can specify both the path in a non-global zone and the path in a global zone, in this format: Non-GlobalZonePath:GlobalZonePath The global zone path is optional. If you do not specify a global zone path, Sun Cluster assumes that the path in the non-global zone and in the global zone are the same. If you specify the path as Non-GlobalZonePath:GlobalZonePath, you must specify GlobalZonePath in the global zone's /etc/vfstab. The default setting for this property is an empty list. You can use the SUNW.HAStoragePlus resource type to make a file system available to a non-global zone. To enable the SUNW.HAStoragePlus resource type to do this, you must create a mount point in the global zone and in the non-global zone. The SUNW.HAStoragePlus resource type makes the file system available to the non-global zone by mounting the file system in the global zone. The resource type then per- forms a loopback mount in the non-global zone. Each file system mount point should have an equivalent entry in /etc/vfstab on all cluster nodes and in all global zones. The SUNW.HAS- toragePlus resource type does not check /etc/vfstab in non-global zones. SUNW.HAStoragePlus resources that specify local file systems can only belong in a failover resource group with affinity switchovers enabled. These local file systems can therefore be termed failover file systems. You can specify both local and global file system mount points at the same time. Any file system whose mount point is present in the FilesystemMountPoints extension property is assumed to be local if its /etc/vfstab entry satisfies both of the following conditions: 1. The non-global mount option is specified. 2. The "mount at boot" field for the entry is set to "no." A Solaris ZFS is always a local file system. Do not list a ZFS in /etc/vfstab. Also, do not include ZFS mount points in the Filesystem- MountPoints property. GlobalDevicePaths Specifies a list of valid global device group names or global device paths. The paths are defined in the format paths[,...]. The default setting for this property is an empty list. Zpools Specifies a list of valid ZFS storage pools, each of which contains at least one ZFS. These ZFS storage pools are defined in the format paths[,...]. The default setting for this property is an empty list. All file systems in a ZFS storage pool are mounted and unmounted together. The Zpools extension property enables you to specify ZFS storage pools. The devices that make up a ZFS storage pool must be accessible from all the nodes or zones that are configured in the node list of the resource group to which a SUNW.HAStoragePlus resource belongs. A SUNW.HAStoragePlus resource that manages a ZFS storage pool can only belong to a failover resource group. When a SUNW.HAStoragePlus resource that manages a ZFS storage pool is brought online, the ZFS storage pool is imported, and every file system that the ZFS stor- age pool contains is mounted. When the resource is taken offline on a node, for each managed ZFS storage pool, all file systems are unmounted and the ZFS storage pool is exported. Note - SUNW.HAStoragePlus does not support file systems created on ZFS volumes. ZpoolsSearchDir Specifies the location to search for the devices of Zpools. The default value for the ZpoolsSearchDir extension property is /dev/dsk. The ZpoolsSearchDir extension property is similar to the -d option of the zpool command. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscu | +-----------------------------+-----------------------------+ SEE ALSO
rt_reg(4), attributes(5) WARNINGS
Make data service resources within a given resource group dependent on a SUNW.HAStoragePlus resource. Otherwise, no synchronization is pos- sible between the data services and the global devices or file systems. Strong resource dependencies ensure that the SUNW.HAStoragePlus resource is brought online before other resources. Local file systems that are managed by a SUNW.HAStoragePlus resource are mounted only when the resource is brought online. Enable logging on UFS systems. Avoid configuring multiple SUNW.HAStoragePlus resources in different resource groups that refer to the same device group and with Affini- tyOn flags set to TRUE. Redundant device switchovers can occur. As a result, resource and device groups might be dislocated. Avoid configuring a ZFS storage pool under multiple SUNW.HAStoragePlus resources in different resource groups. NOTES
The SUNW.HAStoragePlus resource is capable of mounting any cluster file system that is found in an unmounted state. All file systems are mounted in the overlay mode. Local file systems are forcibly unmounted. The waiting time for all device services and file systems to become available is specified by the Prenet_Start_Timeout property in SUNW.HAStoragePlus. This is a tunable property. SunOS 5.9 25 Sep 2007 SUNW.HAStoragePlus(5)
All times are GMT -4. The time now is 03:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy