Required some inputs for VCS functions...
As we are in phase to built a DR project for Enterprise Vault.We have some quries for the same... 1) Once the data is replicated to DR, is there any way in VCS to check for integrity of the replicated data? 2) Copying vault store partitions to new storage would be a time consuming task since the size of the partitions and the number of files is huge. What would be the best practice method recommended by Symantec for copying this data in order to improve efficiency and also minimize risk of data loss. 3) Once the solution is deployed, is it possible to revert back to windows format storage from Symantec format with minimal data loss? Regards VVVSolved1.1KViews8likes4Comments
Recover deleted file
Hello. I've a vxfs filesystem (vxfs 5.0). Yesterday I've accidentally deleted a directory containing about 1000 files. Today I've remounted the filesystem readonly; I want to try to recover that deleted files (if they are not already overridden). Exists some tool to do that? Thankyou Matteo2KViews2likes7Comments
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.2KViews2likes3CommentsNew set of articles about troubleshooting the "failed" disk status, as reported by vxdisk
Hi, all. We have released a set of articles that contain information about troubleshooting the "failed" disk status, as reported by vxdisk. Here is the link: "Failed" or "failed was" is reported by vxdisk http://www.symantec.com/docs/TECH200618 Since this is a broad topic, the "technote" is actually a set of about a dozen article that have been organized into a logical tree structure, with TECH200618 at its "root." Let us know what you think! Regards, Mike498Views2likes0CommentsHow to break root disk Mirror in VxVM
Hi All bash-3.00# vxprint -g rootdg -vh rootvol TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 v rootvol root ENABLED 60821952 - ACTIVE - - pl rootvol-01 rootvol ENABLED 60821952 - ACTIVE - - sd rootdg01-B0 rootvol-01 ENABLED 1 0 - - Block0 sd rootdg01-02 rootvol-01 ENABLED 60821951 1 - - - pl rootvol-02 rootvol ENABLED 60821952 - ACTIVE - - sd rootdg02-01 rootvol-02 ENABLED 60821952 0 - - - bash-3.00# df -h / Filesystem size used avail capacity Mounted on /dev/vx/dsk/bootdg/rootvol 29G 19G 9.4G 67% / 1) From above configuration we see root file system is configured on volume rootvol which is a mirror. Now i'd like to break the mirror and keep the mirror copy for backout purpose as i will be upgrading on the actual root disk. I do not want to delete the plexes or the mirror copy. Suppose in SVM, d0 is a mirror and d10 and d20 are its submirrors, we issue metadetach d0 d20 command to detach the submirror. How do we accomplish the same in the above VxVM configuration ? 2) Plexrootvol-02 has only 1 subdisk rootdg02-01, whereas Plex rootvol-01 has 2 subdisks rootdg01-B0 and rootdg01-02. What is the significance of having 2 subdisks for the plex rootvol-01 ? If the Plexrootvol-01is a mirrored copy of another plexrootvol-02 then the size and number of subdisks in each plex should be the same or not ? ===================================================================================================== use-nvramrc?=true nvramrc=devalias vx-rootdg01 /pci@1f,700000/scsi@2/disk@0,0:a devalias vx-rootdg02 /pci@1f,700000/scsi@2/disk@1,0:a 3) Once the root volume plex has been disassociated can we still use both the above listed device aliases to boot OS from ok prompt ? ok> boot vx-rootdg01 ok> boot vx-rootdg02 Thank you everybody for your response as always. Response is highly appreciated. Regards, Danish.Solved3KViews1like7Comments
unable to mount the filesystem under veritas volume manager
# fsck -m /dev/vx/rdsk/ax4nonprod/MediaLibrary ** /dev/vx/rdsk/ax4nonprod/MediaLibrary BAD SUPER BLOCK: MAGIC NUMBER WRONG USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; eg. fsck [-F ufs] -o b=# [special ...] where # is the alternate super block. SEE fsck_ufs(1M). # fsck -F vxfs /dev/vx/rdsk/ax4nonprod/MediaLibrary UX:vxfs fsck: WARNING: V-3-20836: file system had I/O error(s) on meta-data. UX:vxfs fsck: WARNING: V-3-20837: file system had I/O error(s) on user data. log replay in progress log replay failed to clean file system file system is not clean, full fsck required full file system check required, exiting ... # fsck -F vxfs -o full /dev/vx/rdsk/ax4nonprod/MediaLibrary UX:vxfs fsck: WARNING: V-3-20836: file system had I/O error(s) on meta-data. UX:vxfs fsck: WARNING: V-3-20837: file system had I/O error(s) on user data. log replay in progress pass0 - checking structural files pass1 - checking inode sanity and blocks UX:vxfs fsck: ERROR: V-3-26117: bc_read failure devid = 0, bno = 1804093680, off = 0, len = 131072 # # vxdg list NAME STATE ID ax4flexstor enabled,cds 1212569692.93.PON140 ax4nonprod enabled,cds 1211357290.341.PON140 ax4nonprod2 enabled,cds 1343120352.120.PON140 prod enabled,cds 1163173573.213.PON140 # # # # vxdg list ax4nonprod Group: ax4nonprod dgid: 1211357290.341.PON140 import-id: 1024.91 flags: cds version: 120 alignment: 8192 (bytes) ssb: on detach-policy: global dg-fail-policy: dgdisable copies: nconfig=default nlog=default config: seqno=0.1660 permlen=1280 free=1202 templen=34 loglen=192 config disk emcpower29s2 copy 1 len=1280 disabled config disk emcpower30s2 copy 1 len=1280 disabled config disk emcpower31s2 copy 1 len=1280 disabled config disk emcpower32s2 copy 1 len=1280 disabled config disk emcpower33s2 copy 1 len=1280 disabled config disk emcpower34s2 copy 1 len=1280 disabled config disk emcpower35s2 copy 1 len=1280 disabled config disk emcpower36s2 copy 1 len=1280 disabled config disk emcpower37s2 copy 1 len=1280 disabled config disk emcpower38s2 copy 1 len=1280 disabled config disk emcpower39s2 copy 1 len=1280 disabled config disk emcpower40s2 copy 1 len=1280 disabled config disk emcpower41s2 copy 1 len=1280 state=clean online config disk emcpower42s2 copy 1 len=1280 disabled config disk emcpower43s2 copy 1 len=1280 state=clean online config disk emcpower44s2 copy 1 len=1280 disabled config disk emcpower45s2 copy 1 len=1280 disabled config disk emcpower46s2 copy 1 len=1280 disabled config disk emcpower47s2 copy 1 len=1280 disabled config disk emcpower48s2 copy 1 len=1280 disabled config disk emcpower49s2 copy 1 len=1280 state=clean online config disk emcpower58s2 copy 1 len=48144 disabled config disk emcpower59s2 copy 1 len=48144 disabled config disk emcpower60s2 copy 1 len=48144 disabled config disk emcpower61s2 copy 1 len=48144 disabled config disk emcpower62s2 copy 1 len=48144 disabled config disk emcpower63s2 copy 1 len=48144 disabled config disk emcpower64s2 copy 1 len=48144 disabled config disk emcpower66s2 copy 1 len=48144 disabled config disk emcpower68s2 copy 1 len=48144 disabled config disk emcpower69s2 copy 1 len=48144 state=clean online config disk emcpower73s2 copy 1 len=48144 disabled config disk emcpower74s2 copy 1 len=48144 disabled config disk emcpower75s2 copy 1 len=48144 state=clean online config disk emcpower76s2 copy 1 len=48144 disabled config disk emcpower77s2 copy 1 len=48144 disabled config disk emcpower78s2 copy 1 len=48144 disabled config disk emcpower79s2 copy 1 len=48144 disabled config disk emcpower80s2 copy 1 len=48144 disabled config disk emcpower81s2 copy 1 len=48144 disabled config disk emcpower82s2 copy 1 len=48144 disabled config disk emcpower83s2 copy 1 len=48144 disabled config disk emcpower84s2 copy 1 len=48144 disabled config disk emcpower85s2 copy 1 len=48144 state=clean online config disk emcpower102s2 copy 1 len=48144 disabled config disk emcpower103s2 copy 1 len=48144 disabled config disk emcpower104s2 copy 1 len=48144 disabled config disk emcpower105s2 copy 1 len=48144 disabled config disk emcpower106s2 copy 1 len=48144 state=clean online config disk emcpower107s2 copy 1 len=48144 disabled log disk emcpower29s2 copy 1 len=192 disabled log disk emcpower30s2 copy 1 len=192 log disk emcpower31s2 copy 1 len=192 disabled log disk emcpower32s2 copy 1 len=192 disabled log disk emcpower33s2 copy 1 len=192 disabled log disk emcpower34s2 copy 1 len=192 log disk emcpower35s2 copy 1 len=192 log disk emcpower36s2 copy 1 len=192 disabled log disk emcpower37s2 copy 1 len=192 disabled log disk emcpower38s2 copy 1 len=192 disabled log disk emcpower39s2 copy 1 len=192 disabled log disk emcpower40s2 copy 1 len=192 disabled log disk emcpower41s2 copy 1 len=192 disabled log disk emcpower42s2 copy 1 len=192 disabled log disk emcpower43s2 copy 1 len=192 disabled log disk emcpower44s2 copy 1 len=192 disabled log disk emcpower45s2 copy 1 len=192 disabled log disk emcpower46s2 copy 1 len=192 disabled log disk emcpower47s2 copy 1 len=192 log disk emcpower48s2 copy 1 len=192 disabled log disk emcpower49s2 copy 1 len=192 disabled log disk emcpower58s2 copy 1 len=7296 disabled log disk emcpower59s2 copy 1 len=7296 disabled log disk emcpower60s2 copy 1 len=7296 disabled log disk emcpower61s2 copy 1 len=7296 disabled log disk emcpower62s2 copy 1 len=7296 log disk emcpower63s2 copy 1 len=7296 disabled log disk emcpower64s2 copy 1 len=7296 disabled log disk emcpower66s2 copy 1 len=7296 log disk emcpower68s2 copy 1 len=7296 disabled log disk emcpower69s2 copy 1 len=7296 disabled log disk emcpower73s2 copy 1 len=7296 disabled log disk emcpower74s2 copy 1 len=7296 disabled log disk emcpower75s2 copy 1 len=7296 disabled log disk emcpower76s2 copy 1 len=7296 disabled log disk emcpower77s2 copy 1 len=7296 disabled log disk emcpower78s2 copy 1 len=7296 log disk emcpower79s2 copy 1 len=7296 disabled log disk emcpower80s2 copy 1 len=7296 disabled log disk emcpower81s2 copy 1 len=7296 disabled log disk emcpower82s2 copy 1 len=7296 disabled log disk emcpower83s2 copy 1 len=7296 disabled log disk emcpower84s2 copy 1 len=7296 disabled log disk emcpower85s2 copy 1 len=7296 disabled log disk emcpower102s2 copy 1 len=7296 disabled log disk emcpower103s2 copy 1 len=7296 disabled log disk emcpower104s2 copy 1 len=7296 disabled log disk emcpower105s2 copy 1 len=7296 disabled log disk emcpower106s2 copy 1 len=7296 disabled log disk emcpower107s2 copy 1 len=7296 disabled # # vxdisk -g ax4nonprod -e list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME emcpower29s2 auto ax4nonprod01 ax4nonprod online emcpower29c emcpower30s2 auto ax4nonprod02 ax4nonprod online emcpower30c emcpower31s2 auto ax4nonprod03 ax4nonprod online emcpower31c emcpower32s2 auto ax4nonprod04 ax4nonprod online emcpower32c emcpower33s2 auto ax4nonprod05 ax4nonprod online emcpower33c emcpower34s2 auto ax4nonprod06 ax4nonprod online emcpower34c emcpower35s2 auto ax4nonprod07 ax4nonprod online emcpower35c emcpower36s2 auto ax4nonprod08 ax4nonprod online emcpower36c emcpower37s2 auto ax4nonprod09 ax4nonprod online emcpower37c emcpower38s2 auto ax4nonprod10 ax4nonprod online emcpower38c emcpower39s2 auto ax4nonprod11 ax4nonprod online emcpower39c emcpower40s2 auto ax4nonprod12 ax4nonprod online emcpower40c emcpower41s2 auto ax4nonprod13 ax4nonprod online emcpower41c emcpower42s2 auto ax4nonprod14 ax4nonprod online emcpower42c emcpower43s2 auto ax4nonprod15 ax4nonprod online emcpower43c emcpower44s2 auto ax4nonprod16 ax4nonprod online emcpower44c emcpower45s2 auto ax4nonprod17 ax4nonprod online emcpower45c emcpower46s2 auto ax4nonprod18 ax4nonprod online emcpower46c emcpower47s2 auto ax4nonprod19 ax4nonprod online emcpower47c emcpower48s2 auto ax4nonprod20 ax4nonprod online emcpower48c emcpower49s2 auto ax4nonprod21 ax4nonprod online emcpower49c emcpower58s2 auto ax4nonprod22 ax4nonprod online emcpower58c emcpower59s2 auto ax4nonprod23 ax4nonprod online emcpower59c emcpower60s2 auto ax4nonprod24 ax4nonprod online emcpower60c emcpower61s2 auto ax4nonprod25 ax4nonprod online emcpower61c emcpower62s2 auto ax4nonprod26 ax4nonprod online emcpower62c emcpower63s2 auto ax4nonprod27 ax4nonprod online emcpower63c emcpower64s2 auto ax4nonprod28 ax4nonprod online emcpower64c emcpower66s2 auto ax4nonprod29 ax4nonprod online emcpower66c emcpower68s2 auto ax4nonprod30 ax4nonprod online emcpower68c emcpower69s2 auto ax4nonprod31 ax4nonprod online emcpower69c emcpower73s2 auto ax4nonprod39 ax4nonprod online emcpower73c emcpower74s2 auto ax4nonprod40 ax4nonprod online emcpower74c emcpower75s2 auto ax4nonprod41 ax4nonprod online emcpower75c emcpower76s2 auto ax4nonprod42 ax4nonprod online emcpower76c emcpower77s2 auto ax4nonprod43 ax4nonprod online emcpower77c emcpower78s2 auto ax4nonprod44 ax4nonprod online emcpower78c emcpower79s2 auto ax4nonprod32 ax4nonprod online emcpower79c emcpower80s2 auto ax4nonprod33 ax4nonprod online emcpower80c emcpower81s2 auto ax4nonprod34 ax4nonprod online emcpower81c emcpower82s2 auto ax4nonprod35 ax4nonprod online emcpower82c emcpower83s2 auto ax4nonprod36 ax4nonprod online emcpower83c emcpower84s2 auto ax4nonprod37 ax4nonprod online emcpower84c emcpower85s2 auto ax4nonprod38 ax4nonprod online emcpower85c emcpower102s2 auto ax4nonprod45 ax4nonprod online emcpower102c emcpower103s2 auto ax4nonprod46 ax4nonprod online emcpower103c emcpower104s2 auto ax4nonprod47 ax4nonprod online emcpower104c emcpower105s2 auto ax4nonprod48 ax4nonprod online emcpower105c emcpower106s2 auto ax4nonprod49 ax4nonprod online emcpower106c emcpower107s2 auto ax4nonprod50 ax4nonprod online emcpower107c # vxdisk list | grep -i ax4nonprod emcpower29s2 auto:cdsdisk ax4nonprod01 ax4nonprod online emcpower30s2 auto:cdsdisk ax4nonprod02 ax4nonprod online emcpower31s2 auto:cdsdisk ax4nonprod03 ax4nonprod online emcpower32s2 auto:cdsdisk ax4nonprod04 ax4nonprod online emcpower33s2 auto:cdsdisk ax4nonprod05 ax4nonprod online emcpower34s2 auto:cdsdisk ax4nonprod06 ax4nonprod online emcpower35s2 auto:cdsdisk ax4nonprod07 ax4nonprod online emcpower36s2 auto:cdsdisk ax4nonprod08 ax4nonprod online emcpower37s2 auto:cdsdisk ax4nonprod09 ax4nonprod online emcpower38s2 auto:cdsdisk ax4nonprod10 ax4nonprod online emcpower39s2 auto:cdsdisk ax4nonprod11 ax4nonprod online emcpower40s2 auto:cdsdisk ax4nonprod12 ax4nonprod online emcpower41s2 auto:cdsdisk ax4nonprod13 ax4nonprod online emcpower42s2 auto:cdsdisk ax4nonprod14 ax4nonprod online emcpower43s2 auto:cdsdisk ax4nonprod15 ax4nonprod online failing emcpower44s2 auto:cdsdisk ax4nonprod16 ax4nonprod online emcpower45s2 auto:cdsdisk ax4nonprod17 ax4nonprod online emcpower46s2 auto:cdsdisk ax4nonprod18 ax4nonprod online emcpower47s2 auto:cdsdisk ax4nonprod19 ax4nonprod online emcpower48s2 auto:cdsdisk ax4nonprod20 ax4nonprod online emcpower49s2 auto:cdsdisk ax4nonprod21 ax4nonprod online emcpower58s2 auto:cdsdisk ax4nonprod22 ax4nonprod online emcpower59s2 auto:cdsdisk ax4nonprod23 ax4nonprod online emcpower60s2 auto:cdsdisk ax4nonprod24 ax4nonprod online emcpower61s2 auto:cdsdisk ax4nonprod25 ax4nonprod online emcpower62s2 auto:cdsdisk ax4nonprod26 ax4nonprod online emcpower63s2 auto:cdsdisk ax4nonprod27 ax4nonprod online emcpower64s2 auto:cdsdisk ax4nonprod28 ax4nonprod online emcpower66s2 auto:cdsdisk ax4nonprod29 ax4nonprod online emcpower68s2 auto:cdsdisk ax4nonprod30 ax4nonprod online emcpower69s2 auto:cdsdisk ax4nonprod31 ax4nonprod online emcpower73s2 auto:cdsdisk ax4nonprod39 ax4nonprod online emcpower74s2 auto:cdsdisk ax4nonprod40 ax4nonprod online emcpower75s2 auto:cdsdisk ax4nonprod41 ax4nonprod online emcpower76s2 auto:cdsdisk ax4nonprod42 ax4nonprod online emcpower77s2 auto:cdsdisk ax4nonprod43 ax4nonprod online emcpower78s2 auto:cdsdisk ax4nonprod44 ax4nonprod online emcpower79s2 auto:cdsdisk ax4nonprod32 ax4nonprod online emcpower80s2 auto:cdsdisk ax4nonprod33 ax4nonprod online emcpower81s2 auto:cdsdisk ax4nonprod34 ax4nonprod online emcpower82s2 auto:cdsdisk ax4nonprod35 ax4nonprod online emcpower83s2 auto:cdsdisk ax4nonprod36 ax4nonprod online emcpower84s2 auto:cdsdisk ax4nonprod37 ax4nonprod online emcpower85s2 auto:cdsdisk ax4nonprod38 ax4nonprod online emcpower94s2 auto:cdsdisk ax4nonprod205 ax4nonprod2 online emcpower95s2 auto:cdsdisk ax4nonprod206 ax4nonprod2 online emcpower96s2 auto:cdsdisk ax4nonprod207 ax4nonprod2 online emcpower97s2 auto:cdsdisk ax4nonprod208 ax4nonprod2 online emcpower98s2 auto:cdsdisk ax4nonprod203 ax4nonprod2 online emcpower99s2 auto:cdsdisk ax4nonprod204 ax4nonprod2 online emcpower100s2 auto:cdsdisk ax4nonprod201 ax4nonprod2 online emcpower101s2 auto:cdsdisk ax4nonprod202 ax4nonprod2 online emcpower102s2 auto:cdsdisk ax4nonprod45 ax4nonprod online emcpower103s2 auto:cdsdisk ax4nonprod46 ax4nonprod online emcpower104s2 auto:cdsdisk ax4nonprod47 ax4nonprod online emcpower105s2 auto:cdsdisk ax4nonprod48 ax4nonprod online emcpower106s2 auto:cdsdisk ax4nonprod49 ax4nonprod online emcpower107s2 auto:cdsdisk ax4nonprod50 ax4nonprod onlineSolved3.1KViews1like2Comments
Recover data after vxdisksetup
Hello, I have the following situation: Mistakenly, an administrator has issued a vxdisksetup -i -f to an existing disk. The vxdisk -e list shows the disk online, but no dg, volumes (as expected after the vxdisksetup command) Is it possible to recover the previous existing data on this disk?. Thanks to all. all ideas are welcomed Osvaldo612Views1like2CommentsHow to recover root password (root disk is encapsulated and mirrored)
Hi Team, I have forgotten root password. I need to know the procedure to recover root password. My server has Veritas volume manager and root disk is encapsulated and mirrored. Note: I can't use the below procedure because server goes in panic mode as root disk is encapsulated and mirrored. Sun Sparc System ---- 1. Break signal from ILOM to bring system in OK system. 2. insert solaris DVD 3. boot cdrom -s (Single user mode) 4. Identify boot disk eeprom boot-device format <find c#t#d# format of boot disk> example disk@0,0:a --a--slice 0 now run fsck on root disk. fsck /dev/rdsk/c1t0d0s0 5.mount /dev/rdsk/c1t0d0s0 /a 6. TERM=vt100; export TERM 7. echo $TERM 8. vi /a/etc/shadow 9. remove root password by removing the data between 1st and 2nd collon for root username. 10. cd / umount /a 11. reboot 12. root password is blank so just press ENTER to login. 13. more /etc/shadow 14. passwd (to change root passward). 15. logout and login with new passward. Please provide the well tested and standard procedure for my environment. Thanks in advance. Regards, SK MangalSolved2.9KViews1like10Comments
Mount HP-UX VXFS 6 filesystem on Redhat Linux Server?
Here goes: I have a need to migrate a numebr of large files from several servers to a linux based system from HP-UX 11.23. The data resides on VXFS version 6 filesystems on san storage. I have found LVM tools that allow me to make the MVM structures visible as disks that show up in device mapper on the linux side and I can run strings and dd on the luns and they SEEM to contain the appropriate data. The data itself is in Intersystems Cache database chunks. If I can get the actual files copied over, I can do an endian conversion on them and start using them immediately in the new environment. My problem is transport. I have several 32 GB file that need to be moved and while I haven't done time tests, I am assuming the actual migration time may be prohibitive. I have downloaded a trial of Storage Essentials and installed it on the linux server, but after I make the logical volume visible, I getthe following error when trying to perform the mount: UX:vxfs mount.vxfs: ERROR: V-3-25584: /dev/mapper/vg1220625654-lvol1 is not a supported device UX:vxfs mount.vxfs: ERROR: V-3-24996: Unable to get disk layout version Any help is appreciated. I have been searching high and low on the web, but can't seem to find any current threads about this. There are some older ones about freevxfs that used toexist for linux, but they all said it doesn't work with newer versions of vxfs filesystems. Thanks!Solved2.7KViews1like2Comments
How to Un-Encapsulate the Mirrored (second disk) of vxvm root mirror?
3-Node V880 Sun CLuster 3.1u4 system with VXVM 4.1 patched up to 117080-07. All three nodes are identical as far as root disk layout. Solaris 10 with Kernel 137137-09. Configuration: Disk 0 = 72gb and Disk 1 = 72gb. They are all UFS filesystems. The FS layout is s0=/ (rootvol) s1=swap (swapvol) s3=/global (s3globalvol...maybe, not sure) s4=/usr2 (usr2) s5=/oracle (oracle) Problem: Lost the Primary boot disk Part of the manual un-ecapsulation method (TECH DOC 18432) is to convert the Mirrored Disk back to c#t#d# format. HOWEVER, on the secondary disk (mirored), the "vxdiskadm" menu to mirror all volumes, does not put the original vtoc onto the mirrored Disk (disk 1). To unencapsulate , how do I get the vtoc back to original layout without wiping out the data contained in the PRIV and Public areas of the disk. I believe the priv data is like on slice 3 and the public is on slice 7 (thats justwhere vxvm put them).480Views1like1Comment
Recover deleted file
Hello. I've a vxfs filesystem (vxfs 5.0). Yesterday I've accidentally deleted a directory containing about 1000 files. Today I've remounted the filesystem readonly; I want to try to recover that deleted files (if they are not already overridden). Exists some tool to do that? Thankyou MatteoNew set of articles about troubleshooting the "failed" disk status, as reported by vxdisk
Hi, all. We have released a set of articles that contain information about troubleshooting the "failed" disk status, as reported by vxdisk. Here is the link: "Failed" or "failed was" is reported by vxdisk http://www.symantec.com/docs/TECH200618 Since this is a broad topic, the "technote" is actually a set of about a dozen article that have been organized into a logical tree structure, with TECH200618 at its "root." Let us know what you think! Regards, MikeRecover data after vxdisksetup
Hello, I have the following situation: Mistakenly, an administrator has issued a vxdisksetup -i -f to an existing disk. The vxdisk -e list shows the disk online, but no dg, volumes (as expected after the vxdisksetup command) Is it possible to recover the previous existing data on this disk?. Thanks to all. all ideas are welcomed OsvaldoHow to Un-Encapsulate the Mirrored (second disk) of vxvm root mirror?
3-Node V880 Sun CLuster 3.1u4 system with VXVM 4.1 patched up to 117080-07. All three nodes are identical as far as root disk layout. Solaris 10 with Kernel 137137-09. Configuration: Disk 0 = 72gb and Disk 1 = 72gb. They are all UFS filesystems. The FS layout is s0=/ (rootvol) s1=swap (swapvol) s3=/global (s3globalvol...maybe, not sure) s4=/usr2 (usr2) s5=/oracle (oracle) Problem: Lost the Primary boot disk Part of the manual un-ecapsulation method (TECH DOC 18432) is to convert the Mirrored Disk back to c#t#d# format. HOWEVER, on the secondary disk (mirored), the "vxdiskadm" menu to mirror all volumes, does not put the original vtoc onto the mirrored Disk (disk 1). To unencapsulate , how do I get the vtoc back to original layout without wiping out the data contained in the PRIV and Public areas of the disk. I believe the priv data is like on slice 3 and the public is on slice 7 (thats justwhere vxvm put them).