In VEA GUI, this is NOT enabled even though user can deport/destroy DG through vxdg command. It will also ask if the disks should be disabled (offlined). It is possible that updates have been made to the original version after this document was translated and published. Step #4: Re-scan device tree once LUN(s) have been expanded. # devfsadm -C Step #5: Resize 'logical' VXVM object to match larger LUN dimensions. # vxdisk -g
This will avoid a reboot. Sorry, we couldn't post your feedback right now, please try again later. Extending Concat Volume in Veritas Volume Manager Extending Stripe Volume in Veritas Volume Manager Extending Mirror-Stripe Volume in Veritas Volume M... Thanks for the help in advance. https://support.symantec.com/en_US/article.TECH6397.html
In this case maybe increase the number of copy in the diskgroup Note the number of copies (attribute nconfig): vxdg list yourdg increase this number : vxedit set nconfig=5 yourdg Remove It's important that all of the disks/filesystems necessary for the ABC database to run are included in the disk group, otherwise the database could not be moved to another system. You may also refer to the English Version of this knowledge base article for up-to-date information. Output format: [Device_Name] c1t11d0Enable access for this device? [y,n,q,?] (default: y) yThis disk is listed as added to a disk group.
Disks shown in Veritas Storage Foundation for Windows to be Unreadable or Foreign can be removed, but doing so causes you to lose all existing data on the disk that is No Yes Did this article save you the trouble of contacting technical support? But you can have it your way. Create/Manage Case QUESTIONS?
A disk group must have at least two disks to perform the DLE operation because, during the DLE operation, the disk will be temporarily removed from the disk group, and it ie: # vxprint -qhtrg dumpdg From the currently available output it looks like the system has lost access to the disk at some point (possibly temporarily, or at least long enough Display help about the menuing system q Exit from menusSelect an operation to perform: 3Remove a diskMenu: VolumeManager/Disk/RemoveDiskUse this operation to remove a disk from a disk group. navigate to these guys To change the scheme use vxdiskadm command and select option 20.
If the device is busy the server will have to be rebooted in order for the kernel to be aware of the LUN expansion, prior to and after using the "vxdisk When I try to remove the last disk from the old SAN on the host using "vxdg -g dg rmdisk
Let us see how we can create a basic volume and a file system with Veritas Volume Manager.I have added six, 1 GB disks (other than two, 16 GB disks for https://sort.veritas.com/public/documents/vom/4.0/windowsandunix/productguides/html/vom_winadm_addon_users/RemoveDiskWebDialog.htm We assume here that you've agreed with the Oracle DBA's to use a block size of 8192 for our filesystems. Select Actions-> Remove Disk from Dynamic Disk Group. The disk group is not currently enabled (imported).
Below is the vxdisk list output. check over here vxdiskadm: "Remove a disk" CLI: # vxdg -g diskgroup rmdisk dm_name # vxdiskunsetup [-C] device_tag Example: # vxdisk list DEVICE TYPE DISK GROUP STATUS IBM_VSCSI0_1 auto: LVM - - LVM TagmaStore-USP0_1 Prev Up Next Disk tasks Home Remove a disk from the computer Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES
You can also see the layout as concat in the 6th column.To heck the disk property of a disk in the mydg :# vxdisk -p list c1t2d0 DISK : c1t2d0s2 DISKID I could resolve the issue. If the device is busy. his comment is here dis-associating the plexes and sd's vxplex -o rm dis dw01-01 # zap the dm from the dg vxdg -g dwproddg rmdisk dwprodd01 # nuke the da vxdisk rm c2t2d13s2 NAME STATE
An administrator can specify a specific size using the variable length. This host is running on centos 4.8. vxedit rename ABCdg10 ABCdg_hot_spare Using long disk names can be more descriptive, but will make using vxva trickier, as it will truncate your disk name somewhat if it is too long.
Creating Layered Volume Storage Attributes: Examples Creating a snapshot volume Renaming a Volume Removing Filesystem & Free Up Luns Extending Mirror-Concat Volume in Veritas Volume M... Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? You may wish to review moving a volume off of a particluar disk Procedure 1) comment the volume(s) you're destroying out of vfstab 2) umount the volume 3) stop it: vxvol Create/Manage Case QUESTIONS?
Try these resources. I could gmathew Level 3 05-04-2010 02:27 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thanks Everyone. Also, deport a disk group to use all of the disks remaining in a disk group.A prompt will ask for the name of a disk group. weblink Click OK to complete the operation.
mount -F vxfs -o largefiles /dev/vx/dsk/ABCdg/ABC01 /u03/oradata/ABC Resizing a mounted volume and file system: /etc/vx/bin/vxresize -g rootdg -F vxfs archive 16g Recovering disks under VM control: (if you want to live Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? Rename a Disk Group /root dfwns19 # df -k | grep reports /dev/vx/dsk/reportsdg/ncr01 /u01/app/oracle/admin/REPORTS /dev/vx/dsk/reportsdg/ncr02 /u01/app/oracle/product/8.0.5REPORTS /dev/vx/dsk/reportsdg/ncr03 /u01/oradata/REPORTS /dev/vx/dsk/reportsdg/ncr04 /u02/oradata/REPORTS /dev/vx/dsk/reportsdg/ncr05 /u03/oradata/REPORTS /dev/vx/dsk/reportsdg/ncr06 /u04/oradata/REPORTS /dev/vx/dsk/reportsdg/ncr07 /u11/oraarch/REPORTS dfwns19 # umount /u01/app/oracle/admin/REPORTS dfwns19
To remove a disk from a dynamic disk group, use the Remove Disk from Dynamic Disk Group command. It is not required to run the format command to change the length of partition 2 of the disk in advance. Also it is a preferred way to check the entry in vfstab by mounting it with just "mount /mount-point" or "mountall" command.# cat /etc/vfstab |grep data /dev/vx/dsk/mydg/myvol /dev/vx/rdsk/mydg/myvol /data vxfs 0 Deport a disk group to move the disks in a disk group to another system.
For my convenience I will be using OS native disk scheming. How can I remove this disk from the disk group? The book is wrong ) # sdname dmname,start_offset,sd_length vxmake -g dwproddg sd dwprodd15-01 dwprodd15,0,8389440 # create a plex from your sd vxmake -g dwproddg plex dw01-02 sd=dwprodd15-01 # attach the plex After mirroing I have removed the old plex.
No Yes Did this article save you the trouble of contacting technical support? Renaming a VM Disk: Since names like "ABCdg10" are not as descriptive as they could be, you can rename it to something more useful. To check all the disks scanned under the Operating System:# vxdisk -eoalldgs list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR disk_8 auto:none - - online invalid c1t0d0s2 - disk_9 auto:none - Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
Article:000016550 Publish: Article URL:http://www.veritas.com/docs/000016550 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in eg: config copies on the 6 "new" disks (emcpower[q-v]) state=iofailed, Error: error=Disk read failure That state tends to be seen when the dg has lost access to the disk and has Also paste the output of the following command, if deletion of the DG is not your purpose: vxdisk -o alldgs -e list vxprint -qhtrg dg01 Regards, Dev 0 Kudos Reply As If still not sure / wish to look further before proceeding, the output Dev suggested would be helpful, as well as the following for each disk: # vxdisk list