Sponsored Content
Full Discussion: AIX's restorevgfiles
Operating Systems AIX AIX's restorevgfiles Post 303002003 by MichaelFelt on Wednesday 16th of August 2017 03:21:00 AM
Old 08-16-2017
Quote:
Originally Posted by kwliew999
Seek help from all experts,
I understand that if I perform a savevg on a VG, and later perform a restvg to another hdisk, I will get back a exact same VG that I perform savevg earlier. It will be identical even on permission bit, owner and group.
However, if I perform a restorevgfiles for a filesystem from the same savevg file, will I get a identical filesystem? In terms of permission and owner and group will be identical as well?
As bakunin mentions the commands mksysb and savevg are scripts that act as "front-ends" and are able to collect and record information needed to recreate an "identical" copy during restore.

a) it is not advisable to restvga volume group that you have saved, but not removed. While it may be possible to provide an argument to give the volume group a new name, by default restvg wants to re-create the same logical volume names. As the original volume group exists - this is not acceptable and AIX will rename to logical volumes and your "restore" is no longer identical at the volume group level.

b) as to restore files from a "bff" (backup file format) file - these files will have identical information in the inodes - again, at a binary level - not necessarily at a user level. If UID and GID (i.e., /etc/password and /etc/group) are identical on "both" servers, the restore will appear identical, if the USER/GROUP information is not identical - the restored files will not appear as identical. At a binary level - they are identical.

In short, when you need identical information at an INODE level (i.e, OS specific knowledge about special files and/or ACL, permission bits (e.g., tcb-bit) use the commands backup and restore for saving files, not applications such as ftp, scp, cpio, tar, rsync as they do not copy inode data at an OS level. They might work for an AIX to AIX copy, but there is no guarantee.

p.s. - if you goal is to copy a filesystem, e.g., through a pipe - feel free to look at a script I used (I generally just typeSmilie
Code:
# find . | backup -if - | (cd /some/where/new; restore -xqf -)

Look at: http://www.rootvg.net/content/view/301/309/ (from 2009!)
 

8 More Discussions You Might Find Interesting

1. AIX

How to apply aix 5.3 TL8 properly on ML5 aix system ?

Is it necessary to put system into single user mode for applying aix 5.3 TL8 on a aix 5.3.5.0 system ? Is the TL8 installation not totally safe ? thank you. (6 Replies)
Discussion started by: astjen
6 Replies

2. AIX

IY17981 fix required for aix 4.3.3 to aix 5L migration but not found

Hi, redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages. - My system is ML11 : oslevel –r 4330-11 - But xlC.rte is on wrong version : lslpp -L xlC.rte xlC.rte ... (3 Replies)
Discussion started by: astjen
3 Replies

3. AIX

How to upgrade AIX Firmware & TL Maintenance Level in AIX

Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS ) This article or post covers upgrades for - Hardware Management Console ( HMC ) - Firmware ( also known as microcode ) - VIO ( Virtual I/O Server = PowerVM ) - AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies

4. AIX

Nim on AIX 7.1 used to migrate AIX 5.3 to AIX 6.1...is possible?

Using nimadm: nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y Initializing the NIM master. Initializing NIM client sap024. 0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Discussion started by: sciacca75
2 Replies

5. AIX

Using restorevgfiles to restore entire directory from rootvg problems

I am trying to restore a specific directory and all sub-directories therein using a rootvg tape. I am using the following command to make the backup: mksysb -m -i -v /dev/rmt0 However, I am getting the following result: tctl status rmt0 Available 04-08-00-0,0 LVD SCSI 4mm Tape Drive... (10 Replies)
Discussion started by: herot
10 Replies

6. AIX

Will it affect my AIX LPAR security, when i set up email alerts on AIX server.

Hello, I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior. for example 1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert. 2) disk usage alerts 3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies

7. UNIX for Beginners Questions & Answers

New to AIX: How do I setup high availability on an AIX System

I am new to AIX but not new to unix. I have an interview for an AIX systems admin position and I know they want someone who has knowledge of High Availability, Failover and LPARs From my research so far, It appear powerha is used to setup high availability and failover on Power systems but is... (2 Replies)
Discussion started by: mathisecure
2 Replies

8. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
VGCFGRESTORE(8) 					      System Manager's Manual						   VGCFGRESTORE(8)

NAME
vgcfgrestore - restore volume group descriptor area SYNOPSIS
vgcfgrestore [-b|--backup_number VolumeGroupBackupNumber] [-d|--debug] [-f|--file VGConfPath] [-l[l]|--list [--list]] [-h|--help] [-i|--ignore_size] [-n|--name VolumeGroupName] [-o|--oldpath OldPhysicalVolumePath] [-t|--test] [-v|--verbose] [PhysicalVolumePath] DESCRIPTION
vgcfgrestore allows you to restore the volume group descriptor area from backup files in /etc/lvmconf or from VGConfPath to the given Phys- icalVolumePath. The default backup file is /etc/lvmconf/VolumeGroupName.conf. This command DOES NOT restore data contained in logical volume(s), only the LVM configuration metadata! OPTIONS -b, --backup_numberVolumeGroupBackupNumber Restore from the specified backup number. Use together with option -n which gives the name of the volume group. See examples below. -d, --debug Enables additional debugging output (if compiled with DEBUG). -f, --file VGConfPath Restore from the specified path. Useful for selection of specific backups in the backup history or for copies of VGDA backups. -i, --ignore_size Restore though the size of the physical volume doesn't match the one in the backup. -l, --list Display volume group information contained in the backup file. If given twice, the physical and logical volume information con- tained in the backup file is also shown. -h, --help Print a usage message on standard output and exit successfully. -n, --name VolumeGroupName Do a restore for this volume group name. -o, --oldpath OldPhysicalVolumePath If the path to the physical volume has changed between backup time and restore time, this option enables you to choose the corre- sponding physical volume path in the backup file. -t, --test Do a test run reading the volume group backup WITHOUT trying to restore it -v, --verbose Give verbose runtime information about vgcfgrestore's activities. --version Output the version number and exit successfully. Examples To display information like with "vgdisplay vg00" stored in the backup file /etc/lvmconf/vg00.conf: vgcfgrestore -n vg00 -l To restore the VGDA of vg00 from the alternative backup file /tmp/vg00-old to physical volume /dev/sdn1: vgcfgrestore -f /tmp/vg00-old -n vg00 /dev/sdn1 To restore the VGDA of vg00 from the alternative backup file /etc/lvmconf/vg00.conf.5.old to physical volume /dev/sda5 : vgcfgrestore -n vg00 -b 5 /dev/sda5 DIAGNOSTICS
vgcfgrestore returns an exit code of 0 for success and > 0 for error: 1 no physical volume on command line 2 invalid physical volume name 3 volume group is active 4 error doing restore to physical volume 5 backup is invalid for this volume group 6 volume group is inconsistent 7 physical volume doesn't belong to volume group backup 8 error reading physical volume 9 error getting size of physical volume 10 error writing VGDA to physical volume(s) 11 error removing special files of volume group 12 error setting volume group into lvmtab 13 error doing backup 95 driver/module not in kernel 96 invalid I/O protocol version 97 error locking logical volume manager 98 invalid lvmtab (run vgscan(8)) 99 invalid command line SEE ALSO
lvm(8), vgcfgbackup(8), vgcreate(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS VGCFGRESTORE(8)
All times are GMT -4. The time now is 10:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy