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
vgexport(1M)															      vgexport(1M)

NAME
vgexport - export an LVM volume group and its associated logical volumes SYNOPSIS
mapfile] outfile] vg_name mapfile vg_name DESCRIPTION
Using the format of the first command line of the above, the command can be used to remove a volume group from the system. The volume group will be removed without modifying the logical volume information found on the physical volumes. The volume group identified by vg_name is removed from the or file, and the associated device files including the vg_name directory and file are removed from the system. The volume group information and data is untouched on the physical volume. These disks can be imported to another system with the command (see vgimport(1M)). Scan Option Using the format of the second command line of the above, the command generates a mapfile that can be copied to other systems that are part of a high availability cluster (use the option if you do not want to remove the volume group from the system the command is being run from) and the command (see vgimport(1M)) can be used to recreate the volume group. See also vgchange(1M). The mapfile contains a description of the volume group and its associated logical volume(s) (if any). The logical volume information found on the physical volumes is not modi- fied. Options and Arguments recognizes the following options and arguments: vg_name The path name of the volume group. By default, a file named is created in the current directory. This file contains a description of the volume group and its associated logical volume(s) (if any). Use this option to specify a different name for the file, mapfile. This file can be used as input to (see vgimport(1M)). When used with the option, the volume group specified in the mapfile can be shared with other systems in the high availability cluster. Preview the actions to be taken but do not update the or file or remove the devices file. This option is best used in conjunction with the option. Print verbose messages including the names of the physical volumes associated with this volume group. Scan option. When the option is specified, then the options must also be specified. A mapfile is created that can be used to cre- ate volume group entries on other systems in the high availability cluster (with the command). Write the current set of pv_paths for the volume group to the outfile. The outfile may then be used as the infile for the option. If used together with the option the volume group is not exported but the list of pv_paths is still written to the outfile. This may be useful to derive a list of pv_paths for the volume group or to use on another system which is sharing the volume group and which has an identical configuration. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Export the volume group into mapfile The volume group will be removed from the exporting system. Export the volume group and write the disk names into the file Create a mapfile to be copied to other systems in a high availability cluster to build the volume group information for the volume group, Note that the volume group is not removed from the exporting system. The importing systems will create the volume group with the command using the and options. SEE ALSO
vgimport(1M), vgscan(1M). vgexport(1M)
All times are GMT -4. The time now is 09:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy