![]() |
|
|
|||||||
| Home | Forums | Register | Rules & FAQ | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| Filesystems, Disks and Memory Questions involving NAS, SAN, RAID, Robotic Libraries, backups, etc go here. |
Other UNIX.COM Threads You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Repair boot sector after stupidly importing disk into vg? | selzeda | AIX | 3 | 4 Weeks Ago 06:33 PM |
| Volume Manager 1.3 | timpdixon | HP-UX | 0 | 04-21-2008 08:20 AM |
| How to resize mirror volume in veritas volume manager 3.5 on Solaris 9 OE | nageswarb | SUN Solaris | 0 | 03-14-2008 12:46 PM |
| Disk Mirror in Solaris 9 via Solaris Volume Manager | deal732 | SUN Solaris | 3 | 05-02-2007 08:43 AM |
| Logical Volume Manager Help | pheusion | AIX | 5 | 05-19-2006 06:35 AM |
![]() |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
Volume Manager; importing a disk
System: Alpha with Tru64 5.1b
Disk under LSM (Logical Storage Manager; essentially v2 of Veritas VxVM) control was generating disk errors. The disk was timing out a lot and generating a few disk errors. DBAs couldn't keep the oracle instance up on that node of the cluster. I contacted HP and got a replacement disk and replaced it a couple of days ago. Unfortunately, the DBAs didn't have a good back up of the data. I've put the old disk back in the SCSI shelf and would like to have LSM recognize it again but without losing any of the data on the public disk. We're considering running voldisksetup disk06 to bring the disk back under LSM control and then volrecover disk06 to restore the metadata for this disk. The question is, would voldisksetup cause a problem or lose the data that currently exists in the public disk? Can you think of an alternate way that I can research? Thanks for checking this out. Carl |
| Forum Sponsor | ||
|
|