![]()
Preserves the data already on the LUN when the LUN is grown. User must validate with the array’s vendor whether or not the array VxVM makes noĪttempt to verify the validity of pre-existing data on the LUN, so the FAILED ROOT DISK USING VERITAS VOLUME MANAGER LICENSE KEYLicense has been installed the normal VxVM license key is not enough toĭLE should only be performed on arrays that preserve data. This command option is available only if a Storage Foundation ( resize ) that is provided to support dynamic LUN expansion FAILED ROOT DISK USING VERITAS VOLUME MANAGER HOW TOHow to get VxVM to recognize that a hardware RAID LUN has been grownīeginning with VxVM 4.0, the vxdisk(1M) command has a new option Will turn off that flag, leaving us with:Ĭ1t41d4s2 auto:sliced ckdg01 newckdg onlineĬ1t41d5s2 auto:sliced ckdg02 newckdg online Since at this point, the ‘newckdg’ diskgroup is a full-fledgedĭiskgroup, there’s really no need to leave those flags on, so the commands Whether or not you chose to leave that ‘clone_disk’ flag turned on is up ![]() What we’re left with now is BOTH diskgroups imported simultaneously:Ĭ1t41d4s2 auto:sliced ckdg01 newckdg online clone_diskĬ1t41d5s2 auto:sliced ckdg02 newckdg online clone_disk FAILED ROOT DISK USING VERITAS VOLUME MANAGER UPDATEThis will update the UDID stored in theĭisk’s vxvm private region to the actual disk’s UDID. Validate these disks, and make sure that they are no longer mismatched You must use the ‘updateid’ flag as well, because we need to ![]() The ‘useclonedev’ flag instructs vxvm to use ONLY cloned disks, not the # vxdg -n newckdg -o useclonedev=on -o updateid import ckdg The command to import the diskgroup using the cloned disks while renaming the Original and the cloned) to be imported simultaneously, you will have toįor this example, we will leave the original diskgroup named ‘ckdg’,Īnd change the cloned diskgroup to ‘newckdg’. So, if you want both of these diskgroups (the VxVM will never allow you to have two diskgroups with the same name So here, you have a choice as to how to proceed. The ‘udid_mismatch’ flag is further documented in the The ‘udid_mismatch’ indicates that vxvm knows this disk is a copy of some We can now see them using:Ĭ1t41d4s2 auto:sliced - online udid_mismatchĬ1t41d5s2 auto:sliced - online udid_mismatch Will bring them into the vxvm configuration. Two disks after deporting the diskgroup (to ensure consistency), and then We use some sort of cloning operation to create two new copies of these We start with a simple 2-disk diskgroup called ‘ckdg’.Ĭ0t0d0s2 auto:sliced rootdisk rootdg online Of cloned disks on the same host as the original diskgroup. This tutorial shows a simplified example of importing a diskgroup made up To allow VxVM to easily identify which disk(s) are originals and whichĪre clones, as well as commands to easily import a diskgroup made of upĬloned disks, therefore allowing these operations to take place even on However, beginning with VxVM 5.0, additional features have been added Was because the disk’s VxVM private region contained identical informationĪs the original disk, causing VxVM confusion as to which was the original Replicated (cloned) disks were mapped to a secondary host and theĭiskgroup using those disks had to be imported there. Prior to the 5.0 version of Veritas Volume Manager (VxVM), those So-called “in-the-box data replication” features of some SUN arrays. The Hitachi ‘Shadow Image’ feature, or EMC’s TimeFinder, or any of the VxVM 5.0+ - How to import a disk group of cloned disks on the same host as the originalsīy sebastin on Feb.24, 2009, under Veritas Volume ManagerĬloned disks are created typically by hardware specific copying, such as Public length is the size of the disk minus private area of the disk. Maximum possible size is 524288 blocks (version 5.0 ![]() Vxdisk -f init disk_name type=auto format=sliced |simple|cdsdisk Vxdisksetup -i disk_name format=sliced|simple|cdsdisk If you want to force -T 90 on VxVM 5.0MP1, One of the following disk init might be required to force simple, This can possibly be fixed by inserting -T version number option to the vxdg init command. When you move data from older versions to newer one and if you have ivc-snap or metromirror technology to replicate data on a regular basis, upgrading veritas from 3.5 to 5.0 may impose a problem while try to keep the compatibility with disk layouts. and this format type is not suitable for root disk. ![]() slice 7 holds private and public regions. Simple uses slice 3 to hold public and private regons and rest all slices (apart from slice 2) are zeroed out.Ĭdsdisk for cross platform data migration. Sliced type is used for the rootdg slices 3 and 4 are crated to hold separate private and public region partitions with all slices (apart from slice 2) zeroed out. It is an optional in newer versions since 4.1 Rootdg is a mandatory requirement for the older versions of VxVM. By sebastin on Apr.27, 2009, under Veritas Volume Manager ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |