- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: LVM, EVA, and DLE, and any other TLA you can t...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 02:06 AM
10-18-2011 02:06 AM
LVM, EVA, and DLE, and any other TLA you can think of!
Hi
We have two systems, A & B. Both are running 11v3.
A is Prod, B is Pre-Prod.
On a week-nightly basis, snap clones are created of some of A's LUNS using SSSU scripts. These snaps are then presented and mounted on B.
The following night, these snaps are unomunted from B, deleted, re-created, and re-mounted.
The scripts we use maintain the same LUN ID, VG names, WWN's etc.
I am required to increase the size of one of the LUNs on both systems from 400GB to 500GB. Last week, I resized the SNAP LUN on B on the EVA, and tried to run some vgmodify commands, but couldn't. Now looking at the SNAP LUN again, it has gone back fdown to 400GB.
My question is, could someone please explain the steps needed to make this happen with ZERO downtime.
If any file contents, scripts contents are required, let me know.
Best Regards
Tariq
- Tags:
- sssu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 03:08 AM
10-18-2011 03:08 AM
Re: LVM, EVA, and DLE, and any other TLA you can think of!
do share us the script. we need to understand on how many LUNs are involve.
Generally, there are 2 option i could see from here:
option A:
(1) create new LUN, present to server A, vgextend,lvextend,fsadm (increase filessytem online)
(2) modify your script to snap the old and new LUN and present it to server B
(3) From server B, the script should vgimport the existing LUN and new snap LUN and mount them.
Option B:
(1) in server A, increase the LUN size, ioscan, vgmodify (to take up the new lun size),lvextend,fsadm.
with this approach, there will be not much thing need to do in the script as the script will create a snap on existing LUN. If the new LUN is 500GB, a new 500GB snap will be created.
//
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 03:36 AM
10-18-2011 03:36 AM
Re: LVM, EVA, and DLE, and any other TLA you can think of!
Here are extracts from the scripts:
On A at 01:00 (SNAP Creation)
$SSSU "FILE /opt/bc/smalogin" \
"ADD COPY \"Snap probkup\" DISK_GROUP=\"\Disk Groups\SNAP Disk Group\" REDUNDANCY=VRAID5 VDISK=\"\Virtual Disks\\$SOURCEAPP\backups\ACTIVE\" WORLD_WI
DE_LUN_NAME=6005-08b4-0010-46a9-0001-3000-1a7b-0000" >> $LOG 2>&1
#
$SSSU "FILE /opt/bc/smalogin" \
"ADD LUN 34 VDISK=\"\Virtual Disks\\$SOURCEAPP\Snap probkup\ACTIVE\" HOST=\"\Hosts\\$SOURCEAPP\\HATHOR\"" >> $LOG 2>&1
echo "coins Backups done" >> $LOG 2>&1
#
On B at 03:30 (SNAP mount)
ioscan -fnC disk
insf -e
vgchgid /dev/rdisk/disk649
vgimport vg_snap_probkup /dev/disk/disk649
vgchange -a y vg_snap_probkup
fsck /dev/vg_snap_probkup/lvol1
mount -r /dev/vg_snap_probkup/lvol1 /SNAP/probkup
on B at 22:00 (SNAP unmount)
umount /SNAP/probkup
vgchange -a n /dev/vg_snap_probkup
vgexport /dev/vg_snap_probkup
On A at 23:00 (SNAP deletion)
echo "\nDeleting "\\Virtual Disks\\$SOURCEAPP\\SnapClone of backups\" >>$DELETELOG
$SSSU "FILE /opt/bc/smalogin" "DELETE VDISK \"\Virtual Disks\\$SOURCEAPP\Snap probkup\ACTIVE\"" >> $DELETELOG
_____________________________________________
This is the sequence, and we want to increase the LUN size from 400GB to 500GB.
Regards
Tariq
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 03:46 AM
10-18-2011 03:46 AM
Re: LVM, EVA, and DLE, and any other TLA you can think of!
if this is the case, you need to increase the size of LUN 6005-08b4-0010-46a9-0001-3000-1a7b-0000 from 400GB to 500GB.
YOu can do this at the command view of the eva storage.
When this complete, at server A, you need to run ioscan and vgmodify. This is important so that LVM could detect and use the new disk capacity.
You can compare before and after the lun expansion with diskinfo command.
refer this example. h20000.www2.hp.com/bc/docs/support/.../c01920387.pdf
When you are done, you can extend your fileystem as usual.
You do not need to do any modification in the script. The script will create a snap of lun 6005-08b4-0010-46a9-0001-3000-1a7b-0000.
The new snap size will follow exactly with whatever new size of 6005-08b4-0010-46a9-0001-3000-1a7b-0000 has.
//
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 03:52 AM
10-18-2011 03:52 AM
Re: LVM, EVA, and DLE, and any other TLA you can think of!
OK.
The 400GB SNAP lun is a snap clone of this volume below:
/dev/vg20/lvol1 419348480 358217512 61130968 85% /probkup
We need to increase this on the EVA as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 03:54 AM
10-18-2011 03:54 AM
Re: LVM, EVA, and DLE, and any other TLA you can think of!
OK. On Server A, our ultimate aim is to increase the volume below to 500GB.
The 400GB SNAP lun is a snap clone of this volume below:
/dev/vg20/lvol1 419348480 358217512 61130968 85% /probkup
We need to increase this on the EVA as well.
This leads me to the question, if we just increase the size of this volume on Server A (Prod), will the SNAP clones automatically take the new size?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2011 03:32 AM
11-02-2011 03:32 AM
Re: LVM, EVA, and DLE, and any other TLA you can think of!
yes. Your script will create similar size as your source LUN.
This script will work as long as your disk group have enough disk space for allocation.
PS: appreciate if you could assign some points to any of the posters.