Create veritas file system Solaris

We have an impressive footprint of Sun server mainly M8000, M5000 and E2900 where frequently we have to create Veritas file system on storage provisioned from Clariions. Since, we handle both the Unix and Storage team it becomes rather easy to fulfill business requirement and avoid possible delays. Once the storage is provisioned we start like this:

1. As leadville drivers are in place on Solaris 10 servers, use cfgadm -al to determine the attachment points for external FC.
2. Use cfgadm -c configure , repeat this for all Ap_Id ,Changing the state of the attachment point for making the occupant hardware resource to be usable by OS
3. devfsadm -C ,Asking the drivers to do whatever to probe for the new devices and build subsequently the device files, it also create links for the files like /dev/rdsk/c1t0dos0 etc
4. powercf -q ,Create emcpower pseudo devices for the newly detected luns
5. powermt config ,Creates powerpath configuration
6. powermt save ,Commit the changes to disk
7. format (Label the disk). Repeat this for all the luns.
8. vxdctl enable ,vxconfigd runs in enable mode to rescan for the new devices
9. vxdisk list ,To verify veritas is able to see the new luns, check the state should be online invalid)
10. /etc/vx/bin/vxdisksetup -i emcpowerX ,Setup the disk in cds format, which is default in VxVm 5.0 and above and initializes the disk. Repeat this for all the new luns.
11. vxdg init Disk1=emcpowerX Disk2=emcpowerY , for all the disks that should be a part of the disk group. You can use -T option if you plan to deport and import the diskgroup on another Solaris machine with lower disk group version.
12. vxassist -g make size. Creates the volume to be used later for creating the file system later
13. mkfs -F vxfs -o logsize=32768,bsize=8192,largefiles /dev/rdsk/dg_name/volume
, This is veritas recommended intent log size for volume greater than 512 GB. The calculation is multiple of bsize*logsize<=256MB for file system size > 512 GB. If the file system size is less than 512 GB, then the recommended intent log size is 64 MB. If we are using a block size of 4096 then for 64MB intent log we will have to use 16384 as logsize parameter.
14. Mount the file system.

Comments

Post a Comment

Popular posts from this blog

zpool and power path partial compatibility

Is power path fully supported with zpools, no. It's partial. You can have the pseudo devices assigned to a pool but it uses the native ctd disk only. Recently I lost 2 paths from the vnx array to m9000 server running Solaris 11.1. When I ran the zpool status -x command some of the pools were online while some of them were un available. Power path was reporting 2 paths only but it was active. So ideally the zpools should be online. But it's not. I enabled the remaining 2 paths and all became online. Internally the pools were pointing to one of the ctd devices that belonged to dead path and it was not coming online. Also few of the emcpower devices were renamed, so I had to do zpool import -d with the alternate disk. It seems power path is not completely supported now but may become in future.
Read more

Recoverpoint replication reporting with vmax splitter

Guys, Have you ever thought of automating the RP replication status and send status via email or post it to any reporting platform. Since the splitter impacts the VMAX FA's and there is an overhead of 13% on the utilization its good idea to see if the replication is driving the utilization of vmax FA. There are ways of pulling iops/read/write using symstat but its utilization (Director CPU utilization etc) which plays a significant role. As it crosses 80% we start seeing the increase in device response time. However, to measure FA utilization we will have to go through SMAS UI then pull out the reports. Its manual effort. But there is a way to automate it through REST API. You can get the details what type of objects are supported by pointing to : https://smc server :8443/univmax/restapi Coming to the point, getting recoverpoint consistency group status fully automated doesn't seems to be tough. Lets get through the steps. 1. Hash your SSH keys of the unix host to ...
Read more

Weird problem post power maintenance, no Powerpath pseudo name for Luns

We had the scheduled power maintenance activity in our data center. Every team was notified and we powered doen the servers through cron job. The servers were powered down first then storage (CX-380). And the reverse was followed during startup. After the power shutdown, the SAN was booted up. we forgot to disable the the snapshots. They were still active. Once it came up, the sessions were not there, but snapshot was active. Tried to deactivate the snapshot, failed with the error the "Failing Command: K10SnapCopyAdmin DBid 0 Op 1051. 71 00 80 43" Tried to create a session and attach the snapshot to the session, still unable to deactivate it, neither was able to attach to any other session. Looked at powerlink: It says the command issued to the snapshot is not owned by the SP. I trespassed all the snapshot source lun to SPA, and then tried to deactivate, nothing happened. Rebooted the SP's one by one through the management console. (http:/SP-IP/setup) Then I was able to...
Read more