Sponsored Content
Full Discussion: backup NIM client
Operating Systems AIX backup NIM client Post 302296779 by lo-lp-kl on Wednesday 11th of March 2009 08:35:32 PM
Old 03-11-2009
backup NIM client

Hello everyone

I would like to hear your opinions about this procedure to backup a client to my nim master

1.-I got a cron that make a mksysb from x machine
2.-This mksysb I send by ftp to my nim master.
3.-When I got it in the nim master machine. I create a mksysb resource from this mksysb, I do this

Perform NIM Administration Tasks => Manage Resources => Define a Resource
Next, select “mksysb” as the resource type.

* Resource Name [this name come from my mksysb that put by ftp]
* Resource Type mksysb
* Server of Resource [master]
* Location of Resource [your path export/xxx/xxx/this name come from my mksysb that put by ftp]

Now I got a mksysb resource from a client in my nim master

My questions are

If I got a problem with the partition that I got a mksysb in my nim master. I can boot with the nim and restore by this mksysb.

do you have another way to do this.

The idea in general is, I got mksysb from my partitions I send by ftp to my nim master and then create a mksysb resource and If I got a problem with some one I can restore by nim.

Thanks for your tips
 

10 More Discussions You Might Find Interesting

1. AIX

NIM client mksysb restore

Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies

2. AIX

problem adding NIM client

Hello All, While trying to add NIM client to the NIM environment from NIM client machine, I get the following error: 1800-109 There are currently no additional SMIT screen entries available for this item. This may require installation of additional software before it can be accessed. ... (1 Reply)
Discussion started by: solaix14
1 Replies

3. AIX

Back up a client NIM from nim master

Hello everyone Im trying to backup a nim client from nim master but I got this message COMMAND STATUS Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. 0042-001 nim:... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies

4. AIX

aix-configure nim client

:b:Hi... I need help to configure nim client on nim server.. can i define aix 5.3.4.0 on aix 5.3.7.0 nim server.. while i m configuring nim client on nim server its getting msg that images not same.. i need to confirm that both version should be same or not.. Thanks.. (5 Replies)
Discussion started by: sumathi.k
5 Replies

5. AIX

NIM client boot problem

Hi all, I have created VIO Server which serves 3 lpars. All of them are on VLAN ID 50. From one lpar I installed and set up NIM master server called testAIX1. I have created client and allocated resources to it: testAIX1:/ > lsnim -l test_lpar test_lpar: class = machines ... (4 Replies)
Discussion started by: phobus
4 Replies

6. AIX

filesets nim client

Hello everyone I was looking for the filesets to install a nim client on a linux box. (red hat 5 for power) I have the nim master on aix box and I have different nim client with aix. I download some filesets fron aix cd to linux box, but Im still hang up. Some one know where I can find... (1 Reply)
Discussion started by: lo-lp-kl
1 Replies

7. AIX

NIM : remove nim client info from the client

Hi. I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ? Tks (2 Replies)
Discussion started by: stephnane
2 Replies

8. AIX

Nim client with different subnet to Master

Iam attempting to add a client to NIM however the new client has a different subnet than master 10... & 193... , I've established from redbooks that it should be possible but can't find anything that states how? Does anyone use nim in this way? (5 Replies)
Discussion started by: gefa
5 Replies

9. AIX

Problem in communication nim client with nim master

Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client... (0 Replies)
Discussion started by: omonoiatis9
0 Replies

10. AIX

How to know NIM name from NIM client?

Friend's, I was playing around with NIM in my environment & had a quick question in mind which I didn't/couldn't find answer to, which is -- how to find the name of the NIM server sitting on the NIM client? All leads to the answer would be much appreciated, many thanks! -- Souvik (2 Replies)
Discussion started by: thisissouvik
2 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 10:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy