|
|
Sponsored Content
Operating Systems
AIX
AIX's restorevgfiles
Post 303002003 by MichaelFelt on Wednesday 16th of August 2017 03:21:00 AM
08-16-2017
Quote:
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?
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?
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 type
Code:
# find . | backup -if - | (cd /some/where/new; restore -xqf -)
|
|
8 More Discussions You Might Find Interesting
1. AIX
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
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
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
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
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
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
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
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
LEARN ABOUT REDHAT
vgrename
VGRENAME(8) System Manager's Manual VGRENAME(8) NAME
vgrename - rename a volume group SYNOPSIS
vgrename [-A|--autobackup{y|n}] [-d|--debug] [-h|--help] [-v|--verbose] { OldVolumeGroupPath NewVolumeGroupPath | OldVolumeName NewVol- umeGroupName } DESCRIPTION
vgrename renames an existing (see vgcreate(8) ) volume group. OPTIONS -A, --autobackup y/n Controls automatic backup of VG metadata after the change ( see vgcfgbackup(8) ). Default is yes. -d, --debug Enables additional debugging output (if compiled with DEBUG). -h, --help Print a usage message on standard output and exit successfully. -v, --verbose Gives verbose information about vgrename's activities. Examples "vgrename /dev/vg02 /dev/my_volume_group" renames existing volume group "vg02" to "my_volume_group". "vgrename vg02 my_volume_group" does the same. DIAGNOSTICS
vgrename returns an exit code of 0 for success and > 0 for error: 1 new volume group directory for device special files already exists 2 old volume group directory for device special files doesn't exist 3 new volume group name is invalid 4 old volume group name is invalid 5 error checking existence of old volume group 7 volume group names are identical 8 new volume group already exists 9 error reading VGDA 10 error removing old VGDA from kernel 11 error removing old VGDA from lvmtab 12 error removing device special files for old volume group 13 error creating device special files for new volume group 14 error inserting new volume group name into lvmtab 15 error backinp up VGDA 16 error writing VGDA to lvmtab 17 error renaming volume group in kernel 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 ENVIRONMENT VARIABLES
LVM_AUTOBACKUP If this variable is set to "no" then the automatic backup of VG metadata is turned off. LVM_VG_MAX_BACKUPS This variable determines the backup history depth of kept VGDA copy files in /etc/lvmconf. It can be set to a positive number between 0 and 999. The higher this number is, the more changes you can restore using vgcfgrestore(8). See also lvm(8), vgchange(8), vgcreate(8), lvrename(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS VGRENAME(8)