09-01-2008
i am not sure, if that's still the same way in 5.0, but in the old versions, you could backup your configuration this way:
save:
------------
This command saves the definition of the volumes, plexes, subdisks, and the disk group itself:
vxprint -g diskgroup -hmQqr > blabla.save
This command saves the definition of the volumes, plexes, and subdisks only:
vxprint -g GROUP -hrmvpsQq > blabla.save
view the saved configuration:
------------
vxprint -D - -rht < blabla.save
recover:
------------
To recover a lost volume using the saved configuration:
# vxprint -D - -rhtmqQ lostvolume < blabla.save > restoredvolume
This command creates object definitions for a restored volume out of the object definitions in the lost volume.
To implement the object definitions of restoredvolume into a real volume:
# vxmake -g diskgroup -d restoredvolume
To start the restored volume, and recover its plexes, if appropriate:
# vxrecover -Es restoredvolume
regards
- PRESSY
10 More Discussions You Might Find Interesting
1. Solaris
hi ,
we have a monthly policy for database backups .
the database is a huge one about 200 GB in size and every month , we shut down the database and take a full system backup .
my question is : Is there a way to know that i have taken a valid backup, I need to do something like a test restore... (5 Replies)
Discussion started by: ppass
5 Replies
2. SuSE
I am running SuSE 9.1 and want to backup my LVM vg00 on Veritas Backup Exec 10 Win2K server. My problem, I am unable to browse any of the folder/files of LVM vg00 in Veritas. He could find files on rooot but not in LVM.
Any idea/help will be much appreciated.
Thanks,
Aa (1 Reply)
Discussion started by: aamirs
1 Replies
3. SCO
Hello All,
We have Veritas Backup Exec on a Windows 2003 OS and trying to setup the Ralus agent on SCO to perform regular backups of our Unixware system; but for some reason after "I believe" installing the agent on SCO; and launching it using the 'agent.be" command I receive a syntax error... (1 Reply)
Discussion started by: Yorgy
1 Replies
4. UNIX for Advanced & Expert Users
how can i determine that
what percentage of stack region is currently is used?
(i am using tru64 unix) (2 Replies)
Discussion started by: yakari
2 Replies
5. SCO
I have 3 SCO 5.0.5 machines. Two are running the /etc/bkupexec/agent.be just fine but the 3rd fails with a NRL initialization error. It can't seem to find the backup server in the /etc/hosts file.
The entry is in the /etc/hosts file.
The perms are set correctly on /etc /etc/bkupexec... (0 Replies)
Discussion started by: cnpaul
0 Replies
6. AIX
hello,
I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup:
Veritas Software is not able to communicate properly with our tape library
When we tried to run these commands here's the output
# cfgmgr -l fscsi0
# cfgmgr -l fscsi2
# cfgmgr -l fscsi1
cfgmgr:... (3 Replies)
Discussion started by: filosophizer
3 Replies
7. AIX
Hi all. I hope someone could give me a hand on installing Backup Exec agent on AIX machine :(
Agent:
OS: AIX 5.3
Hostname: DB-HN-SRV02
IP: 10.1.4.64
Backup server:
OS: Windows Server 2003
Hostname: backup-srv
IP: 10.1.5.51
I download "Legacy Unix agent.tar", untar, then run file... (0 Replies)
Discussion started by: bsddaemon
0 Replies
8. Shell Programming and Scripting
Hi Everyone,
we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment?
Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies
9. Solaris
Hi all
I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it?
right now i don't have veritas file system setup. i have only ufs file sysytem
please help some production data is to be restore.
backup was taken... (0 Replies)
Discussion started by: nikhil kasar
0 Replies
10. UNIX for Beginners Questions & Answers
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
LEARN ABOUT HPUX
vxunreloc
vxunreloc(1M) vxunreloc(1M)
NAME
vxunreloc - move a hot-relocated subdisk back to its original disk
SYNOPSIS
/etc/vx/bin/vxunreloc [-f] [-g diskgroup] [-n dm_name] [-t tasktag] dm_name
DESCRIPTION
The Veritas Volume Manager (VxVM) hot-relocation feature can detect an I/O failure in a subdisk, relocate the subdisk, and recover the plex
associated with the subdisk. vxunreloc lets you reverse the process and move the hot-relocated subdisks back onto a disk that was replaced
after a disk failure.
dm_name specifies the disk where the hot-relocated subdisks originally resided. The -n option moves the subdisks to a different disk from
where VxVM originally relocated them. For example, when disk03 fails, all the subdisks residing on it are hot-relocated to other disks.
After the disk is repaired, it is added back to the disk group using a different name, for example, disk05. If you wanted to move all the
hot-relocated subdisks back to the repaired disk, you would enter:
/etc/vx/bin/vxunreloc -n disk05 disk03
When vxunreloc moves the hot-relocated subdisks, it moves them to their original offsets. However, if there was a subdisk that occupied
part or all of the area on the destination disk, vxunreloc prints an error message and exits. In this situation, you can use the -f option
to unrelocate the subdisks to a specified disk, but not to their original offsets.
OPTIONS
-f Unrelocates a subdisk to a different offset if unrelocating to the original offset is not possible.
-g diskgroup
Unrelocates a subdisk from the specified disk group. If this option is not specified, the default disk group is determined using
the rules given in the vxdg(1M) manual page.
-n dm_name
Specifies a new disk name to relocate to a disk with a different name.
-t tasktag
Specifies a tag to pass to the underlying utility.
SUBDISK RECORD FIELDS
orig_dmname
When a subdisk is hot-relocated, its original disk media name is stored in the orig_dmname field. When you run the vxunreloc
command to move the subdisk back to the original disk (or to a new disk), this field is cleared. Before you run the vxunreloc
command, you can do a search on this field to determine the subdisks that originated from a failed disk. For example, the fol-
lowing command lists all the subdisks that were hot-relocated from mydg01 in the disk group mydg. Note that you must prefix the
field name with "sd_" for the command to work.
vxprint -g mydg -se 'sd_orig_dmname="mydg01"'
orig_dmoffset
When a subdisk is hot-relocated, its offset into the original disk is stored in the orig_dmoffset field. When you run vxunreloc
to move the subdisk to the original disk, or to a new disk, this field is zeroed. The following command lists a hot-relocated
subdisk which originally resided at disk10 at offset 1000. Again note that you must prefix the field names with "sd_" for the
command to work.
vxprint -g dg01 -se 'sd_orig_dmname="disk10"
&& sd_orig_dmoffset=1000'
EXIT CODES
If the operation fails, vxunreloc exits with a non-zero status. A non-zero exit code is not a complete indicator of the problems encoun-
tered, but rather denotes the first condition that prevented further execution of the utility.
See vxintro(1M) for a list of standard exit codes.
SEE ALSO
vxassist(1M), vxintro(1M), vxmake(1M), vxprint(1M), vxrelocd(1M), vxsd(1M), vxsparecheck(1M)
VxVM 5.0.31.1 24 Mar 2008 vxunreloc(1M)