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
vxconfigrestore
vxconfigrestore(1M) vxconfigrestore(1M)
NAME
vxconfigrestore - restore disk group configuration
SYNOPSIS
/etc/vx/bin/vxconfigrestore [-c | -d | -n | -p] [-l directory] {dgname | dgid}
DESCRIPTION
The vxconfigrestore utility is used to restore a disk group's configuration information if this has been lost or become corrupted. The
disk group whose configuration is to be restore is specified either by name or by ID.
Any disks whose private region headers have become corrupted are reinstalled when the disk group configuration is restored. If you choose
not to reinstall the VxVM headers for these disks, it may not be possible to restore the disk group.
The disk group configuration backup files may have been automatically created by the vxconfigbackupd daemon, or manually by running the
vxconfigbackup command.
Restoration of a disk group configuration has two stages: precommit and commit. The precommit stage allows you to temporarily load the con-
figuration that is to be restored, and examine it using the vxprint utility. At this stage, the disk group configuration is read-only. No
permanent changes are written to disk until you choose to commit them. If desired, you can abandon the restore operation at the precommit
stage.
OPTIONS
-c (Commit) Permanently commits changes to the disks. The restoration must be at the precommit stage for this command to succeed.
Volumes are synchronized in the background. For large volume configurations, it may take some time to perform the synchroniza-
tion. You can use the vxtask -l list command to monitor the progress of this operation.
-d (Decommit) Abandons the restore operation at the precommit stage.
-n (Precommit: no installation of VxVM disk header) Loads the disk group configuration at the precommit stage. This option speci-
fies that disks whose private region headers have become corrupted are not to be reinstalled.
-l directory
Specifies a directory other than the default (/etc/vx/cbr/bk) where the backup configuration files are located.
-p (Precommit: load) Loads the disk group configuration at the precommit stage. This option specifies that disks whose private
region headers have become corrupted are to be reinstalled. The vxprint command can be used to examine the disk group configura-
tion.
Note: The volumes have not yet been synchronized at this stage.
This is the default operation if no option is specified.
EXAMPLES
Load the configuration of the mydg disk group from the default directory, and reinstall disks that have corrupted VxVM disk headers:
vxconfigrestore -p mydg
Load the configuration of the mydg1 disk group from the backup files in the directory /dgbackup/mydg1 without reinstalling any disks that
have corrupted private region disk headers:
vxconfigrestore -n -l /dgbackup/mydg1 mydg1
Abandon the restoration of the mydg2 disk group at the precommit stage:
vxconfigrestore -d -l /dgbackup/mydg2 mydg2
Commit the restoration of the configuration of the mydg disk group from the backup files in the directory /dgbackup/mydg:
vxconfigrestore -c -l /dgbackup/mydg mydg
FILES
/etc/vx/cbr/bk/dgname.dgid/dgid.dginfo
Default location of backup file for disk group information.
/etc/vx/cbr/bk/dgname.dgid/dgid.diskinfo
Default location of backup file for disk attributes.
/etc/vx/cbr/bk/dgname.dgid/dgid.binconfig
Default location of backup file for binary configuration copy.
/etc/vx/cbr/bk/dgname.dgid/dgid.cfgrec
Default location of backup file for configuration records in vxprint -m format.
NOTES
A disk group must be restored on the same physical disks as are defined in the configuration backup files.
The disk group configuration backup and restore utilities do not save any data in the public region. This includes file system or other
application data that is configured within VxVM objects.
A shared disk group in a cluster is restored as a private disk group. After the commit phase has completed, you can deport the private
disk group and re-import it as a shared disk group.
SEE ALSO
vxconfigbackup(1M), vxconfigbackupd(1M)
VxVM 5.0.31.1 24 Mar 2008 vxconfigrestore(1M)