Sponsored Content
Full Discussion: Backup and restore
Operating Systems AIX Backup and restore Post 302563224 by rbatte1 on Monday 10th of October 2011 11:29:26 AM
Old 10-10-2011
Hmmm, not a good starting point.

The good news is that the SAN definition of PP size should be irrelevant. It might cost you a little bit of usable space, but that's probably minimal. Your problem will be that you are moving from AIX LV mirrors to hardware mirrors (however the SAN protects the allocated disk) so I have a question about you backup process.

Do you use mkszfile before each mksysb? If so, then you may have got a way round things, but you are still exposing yourself to risks of hdisk0 failing during the backup before the mirror on hdisk1 is complete. Removing the mirrors will clear the disk, so it's not like a split mirror that some other systems have or Veritas can provide. You must also remember to use bosboot and check the bootlist after the mirror.

It might be better to:-
  1. Run mksysfile to generate an up-to-date configuration file, mirrors and all.
  2. Edit /image.data and set all COPIES= 2 statements to be COPIES= 1
  3. Run mksysb
Be aware that your tape will only create a single copy, so if you recover to a machine without hardware protected boot disk, you would need to manaully mirror afterwards, including the bosboot and edit of the bootlist If you have to recover to your live system, install to a single disk rather that risk the restore spreading out over both disks.


For your data volume group, it is unclear if the logical volumes are mirrored or how you back them up. If not mirrored, then you are exposed to hardware failure at any time. If they are, then you can perform similar actions, but it would be good to know the backup method for the data before I leap into something. What would your DR recovery procedure be like too? It's all well and good to say you have a backup, but have you tested your restore plan?


Let me know what you have in place and I will see about other suggestions to further protect you. Is it savevg, tar, cpio or perhaps a 3rd party backup tool?




Robin
Liverpool/Blackburn
UK
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cannot restore a TAR backup

I backed up a unix database using "tar -cvf /dev/rmt1 -N 800 /*" Normally I would restore this using "tar -xvf /dev/rmt1 -N 800" This is reporting an error about "not enough memory" I have done a new test backup and restore using the same commands and they work. ANY IDEAS ? (2 Replies)
Discussion started by: Ross.Goodman
2 Replies

2. Solaris

Backup / restore

Hi.... everyone could help me to understand how to do a backup of my servers .. operating systems is sun solaris 8 . I have some question about .... 1) Is better backup phisical disk or partition ??? i sow the command is ufsdump 0cfu /expbck/bcksunver/c0t0d0s5 dev/dsk/c0t0d0s5 to... (4 Replies)
Discussion started by: tt155
4 Replies

3. AIX

Backup and restore

I have several H80 machines, all with AIX 4.3.3. On these machines I have mksysb running for rootvg backups and savevg for non-rootvg backups. I'm trying to get a list of files on the tapes, but I can't seem to do it with tar for the mksysb images. I keep getting the directory checksum errors?... (3 Replies)
Discussion started by: uXion
3 Replies

4. HP-UX

F-Backup restore

Hello! i have a blank harddrive and a complete tape backup of the workstation. the backup is made with F-Backup. Now my question is: how can i restore my workstation? thanks for every idea! paul tittel hup-si (3 Replies)
Discussion started by: paultittel
3 Replies

5. AIX

How to restore from mksysb backup

system is not booting ... i want to restore from mksysb backup. (2 Replies)
Discussion started by: AIXlearner
2 Replies

6. Shell Programming and Scripting

Backup/restore scripts

hi people i am in need of some assistance here hoping to star a linux course in january to wanted to get some experiance before starting so got a hold of some old assessments from a mate at college so just working through them in my spare time for the past 8 weeks or so and this is the final ? that... (2 Replies)
Discussion started by: boabbyrab
2 Replies

7. Shell Programming and Scripting

Backup and restore in unix

Hello everybody, i am trying to make a script in UNIX to backup some compressed files to a tape drive. The thing is that i cannot use cpio command because some of these files are greater than 2GB. so i think the only solution left is backup command. to restore the files i should use the... (6 Replies)
Discussion started by: omonoiatis9
6 Replies

8. Solaris

Zpool backup and restore

hi, my requirement goes something like this: In current setup, we have SPARC server running Solaris10 5/08. Out of 3 HDD available, 2 HDD (other than root) were zpool-ed and 3 zones were created. Now, we have bought a new server with similar H/W config and planning to move the zones... (1 Reply)
Discussion started by: EmbedUX
1 Replies

9. Red Hat

Backup / Restore

Hi, I need to back up a RH file system (96G). The files are oracle .dbf format some of which are 5G in size. I know that tar has got a size restriction of 2G so I cannot use this. Can anyone recommend an alternative way of backuping up this FS? I have been looking at dump but this... (6 Replies)
Discussion started by: Duffs22
6 Replies

10. AIX

Backup and restore query

I have some old directories and files that I which to archive off. I have created archive using -p option with /usr/sbin/backup to a file. If I then do a du -g on the original directory and the archive differ as I'd expect due to using the p flag to compress the files < 2gb as part of the backup. ... (1 Reply)
Discussion started by: gefa
1 Replies
lvextend(1M)															      lvextend(1M)

NAME
lvextend - increase space, increase mirrors for LVM logical volume SYNOPSIS
autobackup] le_number | lv_size | mirror_copies lv_path [pv_path ... | pvg_name ...] Remarks Mirrored disk operations require the installation of the optional HP MirrorDisk/UX software, which is not included in the standard HP-UX operating system. DESCRIPTION
The command can increase a logical volume's allocated extents, or increase its number of mirrored copies. Other logical volume characteristics can be modified with the and commands (see lvchange(1M) and lvreduce(1M)). To limit the allocation to specific physical volumes, specify the physical volume names as pv_path arguments or specify the physical volume group names as pvg_name arguments. Otherwise, all of the physical volumes in a volume group are available for allocating new physical extents. LVM always ensures that physical extent allocation can satisfy the current allocation policy or policies. If a physical volume is not suitable for use with a certain allocation policy, it is not used during physical extent allocation, even it is specified in a pv_path argument or indirectly in a pvg_name argument. The pvg_name argument is allowed only if one of the allocation policies of the logical volume is PVG-strict. Options and Arguments The option is only meaningful if the optional HP MirrorDisk/UX software has been installed. recognizes the following options and arguments: lv_path The block device path name of a logical volume. pv_path The block device path name of a physical volume. pvg_name The name of a physical volume group (see lvmpvg(4)). Set automatic backup for this invocation of this command. autobackup can have one of the following values: Automatically back up configuration changes made to the logical volume. This is the default. After this command executes, the command (see vgcfgbackup(1M)) is executed for the volume group to which the logical volume belongs. Do not back up configuration changes this time. Increase the space allocated to the logical volume, specified in logical extents. le_number is a decimal value greater than the current number of logical extents. le_number must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum number of logical extents for the volume group version. One, and only one, or option must be supplied. Increase the space allocated to the logical volume, specified in megabytes. lv_size is a decimal value greater than the current logical volume size. lv_size must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum logical volume size for the volume group version. lv_size is rounded up to the nearest multiple of the logical extent size, equivalent to the physical extent size defined for the volume group by the command (see vgcreate(1M)). One, and only one, or option must be specified. Set the number of mirror copies allocated for each logical extent. A mirror copy contains the same data as the original. mirror_copies must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum number of mirror copies for the volume group version. mirror_copies must be greater than the current value. Data in the new copies is synchronized unless the option is specified. The synchronization process can be time consuming, depending on hardware characteristics and the amount of data. One, and only one, or option must be specified. Do not synchronize the new mirror copies. This may affect data high availability so use or to synchronize the mirrors. The option must be specified along with this option. Striped Logical Volume considerations Striped and mirrored logical volumes are supported. An increase in size of a striped logical volume is done by increments of stripes logical extents. One increment corresponds to stripes physical extents if the volume is not mirrored or to stripes * (mirror_copies + 1) physical extents if the volume is mirrored. stripes is the number of disks the logical volume is striped across. It is set with the option stripes of the command. mirror_copies is the number of mirror copies allocated for each extent. It is set with the option of the and commands. LVM striped logical volumes are always allocated using the strict or PVG-strict allocation policies. Each physical extent of an increment is allocated on a different physical volume in the volume group. A size increase of a striped volume requires at least stripes (or stripes * (mirror_copies + 1) if the volume is mirrored) physical volumes with adequate free space and meeting the allocation policy. An increase of the number of mirror copies of a striped volume requires at least (stripes times the number of copies to add) physical vol- umes with adequate free space and meeting the allocation policy. Shared Volume Group Considerations For volume group version 1.0 and 2.0, cannot be used if the volume group is activated in shared mode. For volume groups version 2.1 (or higher), can be performed when activated in either shared, exclusive, or standalone mode. Note that the daemon must be running on all the nodes sharing a volume group activated in shared mode. See lvmpud(1M). If physical volume groups are passed as arguments, uses the physical volume group file of the system where the command is issued (the server). LVM shared mode is currently only available in Serviceguard clusters. 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
Increase the number of the logical extents of a logical volume to 100: Increase the logical volume size to 400 MB: Allocate two mirrors (that is, two copies of the original) for each logical extent of a logical volume: Mirror a logical volume onto a particular physical volume. Allocate one mirror and do not synchronize the new mirror copy: Increase the size of a file system existing on a logical volume. First, increase the size of the logical volume. Unmount the file system. Extend the file system to occupy the entire (larger) logical volume. Remount the file system. WARNINGS
The creation of striped and mirrored logical volume(s) may prevent the import and activation of the volume group on an earlier HP-UX release. See lvcreate(1M) on the earlier release to see if it explicitly states that striping and mirroring is supported. If the striped and mirrored logical volumes of the volume group are removed or un-mirrored, the volume group becomes again compatible with the older HP-UX releases. SEE ALSO
lvchange(1M), lvcreate(1M), lvdisplay(1M), lvmadm(1M), lvmpud(1M), lvreduce(1M), lvsync(1M), pvchange(1M), pvdisplay(1M), vgsync(1M), intro(7), lvm(7). lvextend(1M)
All times are GMT -4. The time now is 04:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy