Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Volume Manager; importing a disk Post 302163285 by BOFH on Thursday 31st of January 2008 01:55:25 PM
Old 01-31-2008
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
 

10 More Discussions You Might Find Interesting

1. Solaris

Disk Mirror in Solaris 9 via Solaris Volume Manager

Hello, I am trying to do mirror in solaris 9. I have total 0-7 disks 4 5 6 7 0 1 2 3 Drive 0 and Drive 4 = Boot Drives Need to Mirror following drives. Drive 1 and Drive 5 = Need to mirror Drive 1 was mounted on: /prod1, /prod2, /prod3, /prod4, /prod5. Then i... (3 Replies)
Discussion started by: deal732
3 Replies

2. UNIX for Advanced & Expert Users

Veritas Volume Manager question (Disk layout with 4 plexes)

I am trying to build a veritas volume similar to an existing volume on another server. The output on source server is: usbtor12# vxprint -hrtg appdg v anvil_sqlVOL - ENABLED ACTIVE 629145600 SELECT - fsgen pl anvil_sqlVOL-01 anvil_sqlVOL ENABLED ACTIVE 629145600... (3 Replies)
Discussion started by: momin313
3 Replies

3. Solaris

Veritas Volume Manager: disk "failed was"

Hello there, I'm going to describe a situation I've got here... feel free to ask away questions and I'll provide what I can if it'll help me get this answered! When I do a vxdisk list, I see a disk that VxVM calls "disk4" that is listed as "failed was: c1t9d0s2". When I do a format, I can go... (3 Replies)
Discussion started by: kitykity
3 Replies

4. UNIX for Dummies Questions & Answers

VERITAS Volume Manager - mirror a disk/volume

I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies

5. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

6. UNIX for Dummies Questions & Answers

importing a Physical Volume

hi guys I'm added a new disk to my server (virtual environment) It used to be a Volume Group=Vol_Group01 and Logical Volume= Log_Vol_01_Data and I see /dev/sdb Disk /dev/sdb doesn't contain a valid partition table Disk /dev/sdc: 133.1 GB, 133143986176 bytes 255 heads, 63... (3 Replies)
Discussion started by: karlochacon
3 Replies

7. AIX

Regarding AIX volume manager & replacing a disk

First a little background: I'm working with an AIX 6.1 TL05 running two mirrored SAS disks (rootvg) and four SSDs (appvg) All four SSDs belong to appvg and are setup to mirror as follows: hdisk4 --> hdisk6 (containing application fs) hdisk5 --> hdisk7 (containing database fs) A few days... (1 Reply)
Discussion started by: Michael Mullig
1 Replies

8. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% / ... (0 Replies)
Discussion started by: fretagi
0 Replies

9. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Discussion started by: fretagi
4 Replies

10. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
vxbootsetup(1M) 														   vxbootsetup(1M)

NAME
vxbootsetup - set up system boot information on a Veritas Volume Manager disk SYNOPSIS
/etc/vx/bin/vxbootsetup [-g diskgroup] [medianame ... ] DESCRIPTION
The vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a disk, the required volumes, standvol, rootvol and swapvol (and optionally, dumpvol) must be created on the disk. All of these volumes must be contiguous with only one subdisk. The -g option may be used to specify the boot disk group. If no medianame arguments are specified, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to be bootable. If medianame arguments are given, only the disks that are associated with the specified disk names are configured to be bootable. vxbootsetup requires that: o The root volume must be named rootvol and must have a usage type of root. o The swap volume must be named swapvol and must have a usage type of swap. o The volumes containing /usr and /var (if any) must be named usr and var, respectively. See the chapter "Recovery from Boot Disk Failure" in the Veritas Volume Manager Troubleshooting Guide for detailed information on how the system boots and how VxVM impacts the system boot process. The vxmirror, vxrootmir, and vxresize utilities call vxbootsetup automatically. If you use vxassist, or vxmake and vxplex to create mirrors of the root volume on a disk, you must run vxbootsetup explicitly to make the disk bootable. ARGUMENTS
medianame Specifies the disk name (disk media name) of a VM disk that is to be configured as bootable. SEE ALSO
disksetup(1M), edvtoc(1M), vxassist(1M), vxevac(1M), vxinstall(1M), vxintro(1M), vxmake(1M), vxmirror(1M), vxplex(1M), vxresize(1M), vxrootmir(1M) Veritas Volume Manager Troubleshooting Guide VxVM 5.0.31.1 24 Mar 2008 vxbootsetup(1M)

Featured Tech Videos

All times are GMT -4. The time now is 10:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy