How much space is required in a VxFS file system for the recover file as used by the fscdsconv utility
Hi all, I'm going to migrate a VXVM/VXFS (vers 5.1SP1RP4) volume/file system Solaris Sparc platform to VXVM/VXFS 6.03 Linux 6.5 platform, the file system size is 2TB space, real 1TB.... how much space is required for utility fscdsconv during conversion, there is a formula for this job? Thanks a lot Cecilia1KViews4likes1Comment
reallocate the /etc/vx/cbr/bk , vg config backup file without any service restart ...
1. Create the directory to copy the vg config backup file . # mkdir -p /tech/vgconfigbackup/bk ( please must create the "bk" directory ) 2. Take the backup of scripts " /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh " # cp /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh_bkp<date> 3. Made the required change care fully in below script . # vi /usr/lib/vxvm/voladm.d/lib/vxcbrlib comment the existing line "CF_BKUP_BASE_PATH" and change CF_BKUP_BASE_PATH to point to a new location. 4. Delete the all old vg configuration file backup from default location . 5. Take the new vg configuration backup and test 6. Check the new vg configuration file backup in new location .1.4KViews4likes3Comments
failed to create a Veritas dg
Hi, I'm creating a DG with 6 LUNs. The LUNs have 1 TB each. The disks are as below: When you configure a disk error message appears: emc_clariion0_264 auto - - nolabel emc_clariion0_265 auto - - nolabel emc_clariion0_266 auto - - nolabel emc_clariion0_267 auto - - nolabel emc_clariion0_268 auto - - nolabel emc_clariion0_269 auto - - nolabel root@ # vxdisksetup -i emc_clariion0_264 format=cdsdisk c5t500601663EE00243d228s2 VxVM vxdisksetup ERROR V-5-2-5241 Cannot label as disk geometry cannot be obtained. root@ # root@ # vxdisksetup -i emc_clariion0_265 format=cdsdisk c5t5006016F3EE00243d241s2 VxVM vxdisksetup ERROR V-5-2-5241 Cannot label as disk geometry cannot be obtained. root@ # ... ... root@ # vxdisk list emc_clariion0_264 Device: emc_clariion0_264 devicetag: emc_clariion0_264 type: auto flags: nolabel private autoconfig pubpaths: block=/dev/vx/dmp/emc_clariion0_264 char=/dev/vx/rdmp/emc_clariion0_264 guid: - udid: DGC%5FVRAID%5FCKM00123600618%5F6006016025303100932DF87904C4E411 site: - errno: Device path not valid Multipathing information: numpaths: 8 c7t5006016E3EE00243d228s2 state=enabled type=secondary c7t500601673EE00243d228s2 state=enabled type=primary c5t5006016F3EE00243d228s2 state=enabled type=secondary c5t500601663EE00243d228s2 state=enabled type=primary c6t500601663EE00243d228s2 state=enabled type=primary c6t5006016F3EE00243d228s2 state=enabled type=secondary c8t5006016E3EE00243d228s2 state=enabled type=secondary c8t500601673EE00243d228s2 state=enabled type=primary root@BMG01 # Can someone help me solve the problem? Thanks. MarconiSolved4.6KViews2likes12Comments
Migrating to a new SAN
We're in the process of moving to new datacenters. All servers will be moved over but the SAN won't. The SAN will be replicated to a new SAN in the new datacenters by our SAN admins. That means, the LUNs in the new SAN will be identical to the old, also the LUN numbers. Example output from'vxdisk list' on the current host shows: c1t50050768014052E2d129s2 auto:cdsdisk somedisk01 somedg online This disk will get same LUN nr, but the target name will probably differ as it's new hardware in the new DC. Will this work with Veritas SFHA? If not, is there any way to do this the way the datacenter project wants to? If I could choose to do this my way, I would presentthe LUNs on the new SANto my servers so that I could do a normal host based migration. Add the new LUN to the diskgroup and mirror the data, then remove the old LUN. However, I'm told that the hosts in the current datacenter won't be able to see the new SAN.Solved2.2KViews2likes3Comments
What is the VDID
VOM uses the VDID obtained from VxVM to identify the array as so has identifed an Hitachi USP-V (actually the USPis rebadged as StorageTek 9990V) as: HITACHI_R600_SerialNo This is not useful as I don't know what R600 means, so I am trying to understand what the VDID is. I have looked in: SF admin VOM users VOM Install VOM Add-ons User But I can't find any definitions in these. I could only find an old VOM windows guide reference to it -http://sfdoccentral.symantec.com/vom/4.0/win_unix/html/vom_winadm_addon_users/SFW_VOM40/ch04s03s13.htm which says: The Veritas Disk ID (VDID) is a string that contains information that can identify the array that a disk is contained in. The VDID string is shown in the GUI as a part of the display of information for disks. The VDID string is also shown as a result of thevxdisk diskinfoand thevxdisk listCLI commands. The format of the VDID string varies by array manufacturer and array model. The details of how to interpret the VDID string for a particular array are in an appendix. and the next page gives a table for format of VDID Strings for Various Arrays including Hitachi 9960, 9970, 9980, 9200, 9500,7700,USP HITACHI_{Model}_{EnclosureID}_{CU}_{ LogicalDeviceID } Hitachi other models WWWN+LUNID vxdisk list does not give VDID (and vxdisk diskinfo is Windows syntax), but I can get VDID from vxlist whichshows: Enclosure: hitachi_usp-v0 Status: connected Model: HITACHI Revision: 6008 Array Type: A/A Serial Number: SerialNo ASL: name=libvxhdsusp.so version=vm-6.1-rev-1 I/O Policy: default=MinimumQ current=MinimumQ Partition Size: default=512 current=512 Recovery Option: Throttle cur=Nothrottle[0] def=Nothrottle[0] Error-Retry cur=Timebound[300] def=Timebound[300] Failover Policy: default=Global current=Global Redundancy: default=0 current=0 Disk Count: 241 Path Count: 482 VDID: HITACHI_R600_SerialNo Target Ports: 5,5,6,6 As I understand, in vxdmpadm, the enclosure name is the enclosure type appended with a number (0, 1, 2 etc) so the enclosue is unqiue within the host, but not between hosts, so I understand the need to a unique identifier, but it would seem sensible to justappend the serial number to the enclosure name. So where can I find a recent definition for VDID on UNIX so I can find out whatR600 means - perhaps this is the Enclosure_id - are there any vxvm commands I can run to obtainEnclosure_id Thanks MikeSolved1.2KViews2likes3Comments
how to check the configuration vxconfigbackup copies ?
How tocheck the number of configuration copies saved ? how to change it ? How tochange the default directory of the log files created by vxonfigbackup ? How to logrotate thi sfiles to keep the size low of etc/vx/cbr/bk directory ? Regards, sivaSolved1.1KViews2likes2CommentsQDepth tuneup for DMP
Hi Am I right thinking setting the following in /etc/system which sets the QDepth and IO Timeout globally for the HBA's set sd:sd_io_time=0x3c set sd:sd_max_throttle=8 can be controlled at array level using vxdmpadm as per these tunable parameters https://sort.symantec.com/public/documents/sf/5.0/solaris/html/vxvm_admin/ag_ch_dmp_vm31.html#458394 and will this overide the system settings only for the specific Array and use the defaults or forced from /etc/system values for the rest? Any other insights on this would be great. ThanksSolved1.4KViews2likes4Commentsis it possible to use multipathd with vxvm, and not vxdmp?
Hello, I'm using rhel 5.5 64bit. I would like to know about the possibility of using vxvm with native Linux multipathd instead of the bundled vxdmp pathing software. Is this possible, or recommended? why or why not? Cheers, MarcSolved1.2KViews2likes6Commentsveritas storage foundation + netapp filer + lun iscsi
Hi to everybody, I have a problem on my IBMAIX system : root@ronobe: / =>oslevel -s 5300-08-04-0844 root@ronobe: / =>lslpp -l |grep -i VRTSvxvm VRTSvxvm 5.0.1.0 APPLIED Veritas Volume Manager by VRTSvxvm 5.0.1.0 APPLIED Veritas Volume Manager by I've mapped one lun of my netapp filer to do some tests...the systems see it : root@ronobe: / =>lscfg -vps -l hdisk56 hdisk56 Other iSCSI Disk Drive Manufacturer................NETAPP Machine Type and Model......LUN ROS Level and ID............302E3220 Serial Number...............W-COk4OR Device Specific.(Z0)........0000043270001002 Device Specific.(Z1)........ToME Device Specific.(Z2)........S316 Device Specific.(Z3)........0 Device Specific.(Z4)........ Device Specific.(Z5)........ON But veritas do not see it if I do simple a vxdisk list.Infact I see only the other storages: DS6410_27 auto:cdsdisk thorax2909 thoray29 online udid_mismatch DS6410_28 auto:cdsdisk thoray2907 thoray29 online udid_mismatch DS6410_29 auto:cdsdisk thorax2906 thoray29 online udid_mismatch DS6410_30 auto:cdsdisk thorax2908 thoray29 online udid_mismatch DS6410_31 auto:cdsdisk thoray2906 thoray29 online udid_mismatch DS6410_32 auto:cdsdisk thoray2905 thoray29 online udid_mismatch DS6410_33 auto:cdsdisk thoray2903 thoray29 online udid_mismatch DS6410_34 auto:cdsdisk thoray2902 thoray29 online udid_mismatch DS6410_35 auto:cdsdisk thoray2908 thoray29 online udid_mismatch DS6410_36 auto:cdsdisk thoray2904 thoray29 online udid_mismatch DS6410_37 auto:cdsdisk thoray2901 thoray29 online udid_mismatch DS6410_38 auto:cdsdisk thorax2911 thoray29 online udid_mismatch DS6410_39 auto:cdsdisk thoray2912 thoray29 online udid_mismatch DS6410_40 auto:cdsdisk thorax2903 thoray29 online udid_mismatch DS6410_41 auto:cdsdisk thorax2901 thoray29 online udid_mismatch DS6410_42 auto:cdsdisk thorax2902 thoray29 online udid_mismatch DS6410_43 auto:cdsdisk thoray2915 thoray29 online udid_mismatch DS6410_44 auto:cdsdisk thorax2905 thoray29 online udid_mismatch DS6410_45 auto:cdsdisk thoray2914 thoray29 online udid_mismatch DS6410_46 auto:cdsdisk thoray2911 thoray29 online udid_mismatch DS6410_47 auto:cdsdisk thoray2917 thoray29 online udid_mismatch DS6410_48 auto:cdsdisk thoray2910 thoray29 online udid_mismatch DS6410_49 auto:cdsdisk thoray2913 thoray29 online udid_mismatch DS6410_50 auto:cdsdisk thoray2909 thoray29 online udid_mismatch DS6410_51 auto:cdsdisk thorax2904 thoray29 online udid_mismatch DS6410_52 auto:cdsdisk thoray2916 thoray29 online udid_mismatch DS6410_53 auto:cdsdisk thorax2907 thoray29 online udid_mismatch DS6410_82 auto:cdsdisk thoray2918 thoray29 online udid_mismatch DS6410_83 auto:cdsdisk thoray2919 thoray29 online udid_mismatch DS6410_84 auto:cdsdisk thoray2920 thoray29 online udid_mismatch DS6410_85 auto:cdsdisk thoray2921 thoray29 online udid_mismatch DS6410_86 auto:cdsdisk thoray2922 thoray29 online udid_mismatch DS6410_87 auto:cdsdisk thoray2926 thoray29 online udid_mismatch DS6410_88 auto:cdsdisk thoray2927 thoray29 online udid_mismatch DS6410_89 auto:cdsdisk thoray2923 thoray29 online udid_mismatch DS6410_90 auto:cdsdisk thoray2925 thoray29 online udid_mismatch DS6410_91 auto:cdsdisk thoray2924 thoray29 online udid_mismatch DS6410_96 auto:cdsdisk thoray2928 thoray29 online udid_mismatch DS6410_108 auto:cdsdisk thoray0115 thoray01 online udid_mismatch DS6410_109 auto:cdsdisk thoray0122 thoray01 online udid_mismatch DS6410_110 auto:cdsdisk thoray0121 thoray01 online udid_mismatch DS6410_111 auto:cdsdisk thoray2929 thoray29 online udid_mismatch DS8100_25 auto:LVM - - LVM DS8100_26 auto:LVM - - LVM DS8100_27 auto:LVM - - LVM DS8100_33 auto:cdsdisk poste8 PTP online DS8100_34 auto:cdsdisk poste5 PTP online DS8100_35 auto:cdsdisk poste3 PTP online DS8100_36 auto:cdsdisk poste4 PTP online What do I do wrong?maybe some packages are not installed? thanks to everyone who can suggest me a solution!Solved781Views2likes5Comments
How much space is required in a VxFS file system for the recover file as used by the fscdsconv utility
Hi all, I'm going to migrate a VXVM/VXFS (vers 5.1SP1RP4) volume/file system Solaris Sparc platform to VXVM/VXFS 6.03 Linux 6.5 platform, the file system size is 2TB space, real 1TB.... how much space is required for utility fscdsconv during conversion, there is a formula for this job? Thanks a lot Ceciliareallocate the /etc/vx/cbr/bk , vg config backup file without any service restart ...
1. Create the directory to copy the vg config backup file . # mkdir -p /tech/vgconfigbackup/bk ( please must create the "bk" directory ) 2. Take the backup of scripts " /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh " # cp /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh_bkp<date> 3. Made the required change care fully in below script . # vi /usr/lib/vxvm/voladm.d/lib/vxcbrlib comment the existing line "CF_BKUP_BASE_PATH" and change CF_BKUP_BASE_PATH to point to a new location. 4. Delete the all old vg configuration file backup from default location . 5. Take the new vg configuration backup and test 6. Check the new vg configuration file backup in new location .