Sponsored Content
Operating Systems AIX AIX break rootvg mirror from system down Post 302942148 by sshapiro on Friday 24th of April 2015 05:59:19 PM
Old 04-24-2015
That's what I was just coming to grips with. Ok - first time for everything. I've got a mksysb from a couple of weeks ago. I've burned it (volumes 1 of 3) to a DVD and am trying to do the (re)install. interestingly enough I happen to have a new disk which I've swapped into as a replacement for the bad disk.

ok so far. Boot to that cd which works nicely thank you very much.

Trying to do the restore to the new disk and it is circling around a
image.data has invalid file system data.
Can not continue.

I suppose I could try to extract the image.data and look at it, but even if I could, I doubt I'd be able to "put it back" into the mksysb.

I see two options. (1) try to restore to what I think is a good disk and hope for the best, or (2) do a fresh install, then restore from backups, etc. Kind like not to do that one, but I may not have a choice.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Break mirror so that it can be used later

Hello again, We need to install patches to HP-UX B.11.11 but would like to break the mirror it has (with out damaging it) so that in case of failure we can use this a meassure procedure. Any ideas on how to do this Thank you! (2 Replies)
Discussion started by: AQG
2 Replies

2. Solaris

patch update and break mirror

Hi All, How do you know if you need to break the mirror on solaris 8 patch update? Here's the patch example, 117350-54. On the site, it's just a low type update and not a medium or critical. Is breaking a mirror a best practice only or really a requirement to some patch? Thanks, itik (1 Reply)
Discussion started by: itik
1 Replies

3. Solaris

break solaris mirror

Hi All, How do I break the solaris 8 mirror? And how do I make sure I will point the first hd mirror on reboot. If the first break mirror won't boot. How do I make the copy mirror to boot? Thanks in advance, itik (2 Replies)
Discussion started by: itik
2 Replies

4. AIX

mirror rootvg

Hello I have a question I have a box with Aix 5.3 with rootvg on mirror. I deleted a filesystem and I create a new one to install some software but when I type lsvg -l rootvg all my filesystems has mirror unless the new one. My question is I can mirror this fs only ??? or I have to... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies

5. AIX

AIX 5.2/5.3 - rootvg on SAN disk - pros and cons

We are considering a DR strategy of booting AIX 5.3 and 5.3 logical partitions from EMC Symmetrix SAN disks, so that we can replicate via SRDF to a recovery site. Has anyone tried configuring AIX 5.x systems to boot from SAN disk? If so, can you provide any information on the pros and cons of... (6 Replies)
Discussion started by: jjgarrot
6 Replies

6. AIX

AIX Rootvg mirror and sysdumplv

Guys, In my AIX 6.1 box the rootvg was on hdisk2, I tried to migrated it to hdisk0 Added hisk0 to rootvg , mirrored rootvg and changed bootlist and and sucessfully rebooted from hdisk0 Now I tried to remove the hdisk2 from rootvg so breaked mirror -bash-3.00# unmirrorvg rootvg hdisk2... (3 Replies)
Discussion started by: kkeng808
3 Replies

7. AIX

Erase AIX rootvg system disk

Hello all, I need help for erasing IBM P5 machine running AIX 5.3. I have 2 system disks (Hardware mirror) and i'm looking for a way like a LIVE CD bootable CD so I can boot with the cd and then format the system disks with a "secure erase" software. (7 Replies)
Discussion started by: kobi gabai
7 Replies

8. Solaris

Solaris Volume Manager: Break Mirror and use to make a 2nd machine

Hello: I have a machine built on 2 drives and mirrors have been created to a second set of 2 drives (4 total) on the same platform. SVM. Might anyone provide guidance to create a second machine by breaking the mirrored set, moving the two mirrors (2) to another machine (same platform type),... (1 Reply)
Discussion started by: 4dailyrunner
1 Replies

9. AIX

How to restore rootvg archive after AIX 6.1 crash

Hello, Few days ago I created both mksysb and savevg archives of rootvg. How can I restore this rootvg now because the AIX crashed during some software tests. There is no way to start from hdisk0 because most of the system files are deleted (this includes libc.a). I tough it will be trivial... (6 Replies)
Discussion started by: +Yan
6 Replies

10. Linux

LVM - break mirror taking out orignal copy

Hi Guys, I have a mirrored LVM volume, and wish to break the mirror leaving only copy1 (effectively removing copy 0). Here's the config: # lvs -a -o +devices lvdata vg01 mwi-ao 2.19T lvdata_mlog 100.00 lvdata_mimage_0(0),lvdata_mimage_1(0) vg01... (0 Replies)
Discussion started by: badoshi
0 Replies
Commands Reference, Volume 3, i - m

mksysb_Command

  Purpose

   Creates  an	installable image of the root volume group either
in a file or
   onto a bootable tape.

  Syntax

   mksysb [ -a ] [ -A ] [ -b Number ] [ -e ] [ -F filename ] [
   -i ] [ -m ] [ -p ] [ -t argument ] [ -v ] [ -V ] [
   -X ] Device | File

  Description

   Attention: Running the mkszfile or mksysb  commands	with  the
LC_All
   environment	variable  set  (especially  to a non-C value) can
cause
   unexpected system bahavior such as a mixture of character sets
in outputs.
   To  resolve the problem, unset the LC_ALL variable and restart
the program.

   The mksysb command creates a backup of  the	operating  system
(that is, the
   root  volume  group).  You  can use this backup to reinstall a
system to its
   original state after it has been corrupted. If you create  the
backup on
   tape,  the tape is bootable and includes the installation pro-
grams needed
   to install from the backup.

   The file-system image is in backup-file format. The tape  for-
mat includes a
   boot image, a bosinstall image, and an empty table of contents
followed by
   the system backup (root volume group) image. The  root  volume
group image
   is  in  backup-file	format,  starting with the data files and
then any
   optional map files.

   When a bootable backup of a root volume group is created,  the
boot image
   reflects  the  currently running kernel. If the current kernel
is the 64-bit
   kernel, the backup's boot image is also 64-bit,  and  it  only
boots 64-bit
   systems.  If  the current kernel is a 32-bit kernel, the back-
up's boot image
   is 32-bit, and it can boot both 32-bit and 64-bit systems.

   One of the data files mksysb uses is the  /bosinst.data  file.
If a
   /bosinst.data file doesn't exist, /var/adm/ras/bosinst.data is
copied to /
   (root). In AIX 4.3.3 and later versions, mksysb always updates
the
   target_disk_data  stanzas  in  bosinst.data to match the disks
currently in
   the root volume group of the system where the  mksysb  command
is running.

   If  you  are  using a customized /bosinst.data file and do not
want the
   target_disk_data stanzas updated, you must create the file
   /save_bosinst.data_file. The mksysb command	does  not  update
/bosinst.data
   if the /save_bosinst.data_file exists.

   Notes:

    1. The image the mksysb command creates does not include data
on raw
       devices or in user-defined paging spaces.
    2. If you are using a system with a remote-mounted /usr  file
system, you
       cannot reinstall your system from a backup image.
    3.	The  mksysb command may not restore all device configura-
tions for
       special features, such as  /dev/netbios	and  some  device
drivers not
       shipped with the product.
    4.	Some rspc systems for AIX^(R) 5.1 and earlier do not sup-
port booting
       from tape. When you make a bootable  mksysb  image  on  an
rspc system for
       AIX  5.1  and  earlier  that does not support booting from
tape, the
       mksysb command issues a warning indicating that	the  tape
will not be
       bootable.  You  can  install  a mksysb image from a system
that does not
       support booting from tape by booting from a CD and  enter-
ing
       maintenance  mode. In maintenance mode you will be able to
install the
       system backup from tape.
    5. The mksysb command uses the backup command to  create  its
archive
       image. The mksysb command will also save the EA format for
any JFS2
       filesystems being backed up. It uses the /usr/bin/mkvgdata
shell
       script to save this information.

   To create a backup of the operating system to CD, please refer
to the mkcd
   command.

  Flags

   -a	       Does not backup extended attributes or NFS4 ACLs.
   -A	       Backs up DMAPI file system files.
	       Specifies the number of 512-byte blocks	to  write
in a single
	       output  operation.  When the backup command writes
to tape
	       devices, the default is 100 for backups by name.

   -b Number   The write size is the number of blocks  multiplied
by the block
	       size.  The  default write size for the backup com-
mand writing to
	       tape devices is 51200 (100 * 512) for  backups  by
name. The
	       write  size must be an even multiple of the tape's
physical
	       block size.
	       Excludes files listed in  the  /etc/exclude.rootvg
file from
	       being  backed  up.  The rules for exclusion follow
the pattern
	       matching rules of the grep command.

	       If you want to  exclude	certain  files	from  the
backup, create
	       the  /etc/exclude.rootvg  file, with an ASCII edi-
tor, and enter
	       the patterns of file names that you  do	not  want
included in
	       your  system  backup  image.  The patterns in this
file are input
	       to the pattern matching conventions  of	the  grep
command to
	       determine  which  files	will be excluded from the
backup. If you
	       want to	exclude  files	listed	in  the  /etc/ex-
clude.rootvg file,
	       select  the  Exclude Files field and press the Tab
key once to
	       change the default value to yes.

	       For example, to exclude all the	contents  of  the
directory
	       called  scratch,  edit the exclude file to read as
follows:

		    /scratch/
   -e
	       For example, to exclude the contents of the direc-
tory called
	       /tmp,  and  avoid  excluding any other directories
that have /tmp
	       in the pathname, edit the exclude file to read  as
follows:

		    ^./tmp/

	       All  files  are	backed	up relative to . (current
working
	       directory). To exclude any file or  directory  for
which it is
	       important  to  have the search match the string at
the beginning
	       of the line, use ^ (caret character) as the  first
character in
	       the  search string, followed by . (dot character),
followed by
	       the filename or directory to be excluded.

	       If the filename or directory being excluded  is	a
substring of
	       another filename or directory, use ^. (caret char-
acter
	       followed by dot character) to  indicate	that  the
search should
	       begin  at  the  beginning of the line and/or use $
(dollar sign
	       character) to indicate that the search should  end
at the end
	       of the line.
	       Specifies  a  previously created mksysb image from
which a
   -F filename backup tape will be created. An	attempt  will  be
made to make
	       the  backup tape bootable. Additionally, this flag
must be used
	       in conjunction with a tape device.
	       Calls the mkszfile command,  which  generates  the
/image.data
	       file. The /image.data file contains information on
volume
	       groups,	logical  volumes,  file  systems,  paging
space, and
	       physical  volumes. This information is included in
the backup
	       for future use by the installation process.
	       Note:
	       Before running the mkszfile command,  ensure  that
enough space
	       is  available in the /tmp file to store a boot im-
age. This
   -i	       space is needed during both backup  and	installa-
tion. To
	       determine  the  amount of space needed in the /tmp
file, issue
	       the following command:

	       bosboot -q -a -d device

	       If you use the -X flag with  the  mksysb  command,
you do not
	       need  to  run the bosboot command to determine the
amount of
	       space needed in the /tmp file.
	       Calls the mkszfile command, with the  -m  flag  to
generate map
	       files.
   -m	       Note:
	       The use of the -m flag causes the functions of the
-i flag to
	       be executed also.
	       Disables software packing of the files as they are
backed up.
   -p	       Some tape drives use their own packing or compres-
sion
	       algorithms.
	       Specifies the path to the directory or file system
used to
	       create a boot image from the mksysb file specified
by the -F
   -t argument flag. If the -t flag is not used with the -F flag,
the boot
	       image  is created in the /tmp file by default. Ap-
proximately
	       100 MB of free space is required. After	the  boot
image is
	       created, this space is freed.
   -v	       Verbose mode. Lists files as they are backed up.
	       Verifies a tape backup. This flag causes mksysb to
verify the
   -V	       file header of each file on the	backup	tape  and
report any
	       read errors as they occur.
	       Specifies  to  automatically  expand the /tmp file
system if
   -X	       necessary. The /tmp file system may need to be ex-
tended to
	       make  room  for	the  boot  image  when creating a
bootable backup
	       to tape.

  Parameters

   Device | File	   Specifies the name of  the  device  or
file.

  Examples

    1. To generate a system backup and create an /image.data file
(generated
       by the mkszfile command) to a tape device named /dev/rmt0,
type:

	 mksysb -i /dev/rmt0

    2. To generate a system backup and create an /image.data file
with map
       files (generated by the mkszfile command) to a tape device
named
       /dev/rmt1, type:

	 mksysb -m /dev/rmt1

    3.	To  generate a system backup with a new /image.data file,
but exclude
       the files in directory /home/user1/tmp, create the file
       /etc/exclude.rootvg containing the line	/home/user1/tmp/,
and type:

	 mksysb -i -e /dev/rmt1

       This command will backup the /home/user1/tmp directory but
not the
       files it contains.

    4.	To  generate  a  system  backup  file  named  /mksysb_im-
ages/node1 and a new
       /image.data file for that image, type:

	 mksysb -i /mksysb_images/node1"

       Note:
       This  file  will not be bootable and can only be installed
using Network
       Installation Management (NIM).
    5. To generate a system backup on the tape in /dev/rmt0,  and
then verify
       the readability of file headers, enter:

	 mksysb  /dev/rmt0 -V

  Files

   /usr/bin/mksysb		  Contains the mksysb command.

  Related Information

   The backup command, bosboot command, mkcd command,
   mkszfile command.

   The /image.data file.

   A  procedure  to  verify the mksysb backup can be found in the
article
   Creating system backups in the Installation and migration.

________________________________________________________________________________

		      Commands Reference, Volume 3, i - m

mksysb_Command

  Purpose

   Creates  an	installable image of the root volume group either
in a file or
   onto a bootable tape.

  Syntax

   mksysb [ -a ] [ -A ] [ -b Number ] [ -e ] [ -F filename ] [
   -i ] [ -m ] [ -p ] [ -t argument ] [ -v ] [ -V ] [
   -X ] Device | File

  Description

   Attention: Running the mkszfile or mksysb  commands	with  the
LC_All
   environment	variable  set  (especially  to a non-C value) can
cause
   unexpected system bahavior such as a mixture of character sets
in outputs.
   To  resolve the problem, unset the LC_ALL variable and restart
the program.

   The mksysb command creates a backup of  the	operating  system
(that is, the
   root  volume  group).  You  can use this backup to reinstall a
system to its
   original state after it has been corrupted. If you create  the
backup on
   tape,  the tape is bootable and includes the installation pro-
grams needed
   to install from the backup.

   The file-system image is in backup-file format. The tape  for-
mat includes a
   boot image, a bosinstall image, and an empty table of contents
followed by
   the system backup (root volume group) image. The  root  volume
group image
   is  in  backup-file	format,  starting with the data files and
then any
   optional map files.

   When a bootable backup of a root volume group is created,  the
boot image
   reflects  the  currently running kernel. If the current kernel
is the 64-bit
   kernel, the backup's boot image is also 64-bit,  and  it  only
boots 64-bit
   systems.  If  the current kernel is a 32-bit kernel, the back-
up's boot image
   is 32-bit, and it can boot both 32-bit and 64-bit systems.

   One of the data files mksysb uses is the  /bosinst.data  file.
If a
   /bosinst.data file doesn't exist, /var/adm/ras/bosinst.data is
copied to /
   (root). In AIX 4.3.3 and later versions, mksysb always updates
the
   target_disk_data  stanzas  in  bosinst.data to match the disks
currently in
   the root volume group of the system where the  mksysb  command
is running.

   If  you  are  using a customized /bosinst.data file and do not
want the
   target_disk_data stanzas updated, you must create the file
   /save_bosinst.data_file. The mksysb command	does  not  update
/bosinst.data
   if the /save_bosinst.data_file exists.

   Notes:

    1. The image the mksysb command creates does not include data
on raw
       devices or in user-defined paging spaces.
    2. If you are using a system with a remote-mounted /usr  file
system, you
       cannot reinstall your system from a backup image.
    3.	The  mksysb command may not restore all device configura-
tions for
       special features, such as  /dev/netbios	and  some  device
drivers not
       shipped with the product.
    4.	Some rspc systems for AIX^(R) 5.1 and earlier do not sup-
port booting
       from tape. When you make a bootable  mksysb  image  on  an
rspc system for
       AIX  5.1  and  earlier  that does not support booting from
tape, the
       mksysb command issues a warning indicating that	the  tape
will not be
       bootable.  You  can  install  a mksysb image from a system
that does not
       support booting from tape by booting from a CD and  enter-
ing
       maintenance  mode. In maintenance mode you will be able to
install the
       system backup from tape.
    5. The mksysb command uses the backup command to  create  its
archive
       image. The mksysb command will also save the EA format for
any JFS2
       filesystems being backed up. It uses the /usr/bin/mkvgdata
shell
       script to save this information.

   To create a backup of the operating system to CD, please refer
to the mkcd
   command.

  Flags

   -a	       Does not backup extended attributes or NFS4 ACLs.
   -A	       Backs up DMAPI file system files.
	       Specifies the number of 512-byte blocks	to  write
in a single
	       output  operation.  When the backup command writes
to tape
	       devices, the default is 100 for backups by name.

   -b Number   The write size is the number of blocks  multiplied
by the block
	       size.  The  default write size for the backup com-
mand writing to
	       tape devices is 51200 (100 * 512) for  backups  by
name. The
	       write  size must be an even multiple of the tape's
physical
	       block size.
	       Excludes files listed in  the  /etc/exclude.rootvg
file from
	       being  backed  up.  The rules for exclusion follow
the pattern
	       matching rules of the grep command.

	       If you want to  exclude	certain  files	from  the
backup, create
	       the  /etc/exclude.rootvg  file, with an ASCII edi-
tor, and enter
	       the patterns of file names that you  do	not  want
included in
	       your  system  backup  image.  The patterns in this
file are input
	       to the pattern matching conventions  of	the  grep
command to
	       determine  which  files	will be excluded from the
backup. If you
	       want to	exclude  files	listed	in  the  /etc/ex-
clude.rootvg file,
	       select  the  Exclude Files field and press the Tab
key once to
	       change the default value to yes.

	       For example, to exclude all the	contents  of  the
directory
	       called  scratch,  edit the exclude file to read as
follows:

		    /scratch/
   -e
	       For example, to exclude the contents of the direc-
tory called
	       /tmp,  and  avoid  excluding any other directories
that have /tmp
	       in the pathname, edit the exclude file to read  as
follows:

		    ^./tmp/

	       All  files  are	backed	up relative to . (current
working
	       directory). To exclude any file or  directory  for
which it is
	       important  to  have the search match the string at
the beginning
	       of the line, use ^ (caret character) as the  first
character in
	       the  search string, followed by . (dot character),
followed by
	       the filename or directory to be excluded.

	       If the filename or directory being excluded  is	a
substring of
	       another filename or directory, use ^. (caret char-
acter
	       followed by dot character) to  indicate	that  the
search should
	       begin  at  the  beginning of the line and/or use $
(dollar sign
	       character) to indicate that the search should  end
at the end
	       of the line.
	       Specifies  a  previously created mksysb image from
which a
   -F filename backup tape will be created. An	attempt  will  be
made to make
	       the  backup tape bootable. Additionally, this flag
must be used
	       in conjunction with a tape device.
	       Calls the mkszfile command,  which  generates  the
/image.data
	       file. The /image.data file contains information on
volume
	       groups,	logical  volumes,  file  systems,  paging
space, and
	       physical  volumes. This information is included in
the backup
	       for future use by the installation process.
	       Note:
	       Before running the mkszfile command,  ensure  that
enough space
	       is  available in the /tmp file to store a boot im-
age. This
   -i	       space is needed during both backup  and	installa-
tion. To
	       determine  the  amount of space needed in the /tmp
file, issue
	       the following command:

	       bosboot -q -a -d device

	       If you use the -X flag with  the  mksysb  command,
you do not
	       need  to  run the bosboot command to determine the
amount of
	       space needed in the /tmp file.
	       Calls the mkszfile command, with the  -m  flag  to
generate map
	       files.
   -m	       Note:
	       The use of the -m flag causes the functions of the
-i flag to
	       be executed also.
	       Disables software packing of the files as they are
backed up.
   -p	       Some tape drives use their own packing or compres-
sion
	       algorithms.
	       Specifies the path to the directory or file system
used to
	       create a boot image from the mksysb file specified
by the -F
   -t argument flag. If the -t flag is not used with the -F flag,
the boot
	       image  is created in the /tmp file by default. Ap-
proximately
	       100 MB of free space is required. After	the  boot
image is
	       created, this space is freed.
   -v	       Verbose mode. Lists files as they are backed up.
	       Verifies a tape backup. This flag causes mksysb to
verify the
   -V	       file header of each file on the	backup	tape  and
report any
	       read errors as they occur.
	       Specifies  to  automatically  expand the /tmp file
system if
   -X	       necessary. The /tmp file system may need to be ex-
tended to
	       make  room  for	the  boot  image  when creating a
bootable backup
	       to tape.

  Parameters

   Device | File	   Specifies the name of  the  device  or
file.

  Examples

    1. To generate a system backup and create an /image.data file
(generated
       by the mkszfile command) to a tape device named /dev/rmt0,
type:

	 mksysb -i /dev/rmt0

    2. To generate a system backup and create an /image.data file
with map
       files (generated by the mkszfile command) to a tape device
named
       /dev/rmt1, type:

	 mksysb -m /dev/rmt1

    3.	To  generate a system backup with a new /image.data file,
but exclude
       the files in directory /home/user1/tmp, create the file
       /etc/exclude.rootvg containing the line	/home/user1/tmp/,
and type:

	 mksysb -i -e /dev/rmt1

       This command will backup the /home/user1/tmp directory but
not the
       files it contains.

    4.	To  generate  a  system  backup  file  named  /mksysb_im-
ages/node1 and a new
       /image.data file for that image, type:

	 mksysb -i /mksysb_images/node1"

       Note:
       This  file  will not be bootable and can only be installed
using Network
       Installation Management (NIM).
    5. To generate a system backup on the tape in /dev/rmt0,  and
then verify
       the readability of file headers, enter:

	 mksysb  /dev/rmt0 -V

  Files

   /usr/bin/mksysb		  Contains the mksysb command.

  Related Information

   The backup command, bosboot command, mkcd command,
   mkszfile command.

   The /image.data file.

   A  procedure  to  verify the mksysb backup can be found in the
article
   Creating system backups in the Installation and migration.
All times are GMT -4. The time now is 08:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy