HP 1032 ClusterPack V2.4 Tutorial - Page 57

information. By default, files in /tmp and most files in /var/adm and /var/tmp are excluded.

Get HP 1032 PDF manuals and user guides View all HP 1032 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 57 highlights

z Ensure that the system is not being used. It is advisable that the system stop accepting new LSF jobs while the archive is being made: % badmin hclose z In addition, you should either wait until all running jobs complete, or suspend them: % bstop -a -u all -m z Execute sysimage_create on the Management Server and pass the name of the file from which you would like the image to be made. For example: % /opt/clusterpack/bin/sysimage_create z Monitor the output for possible error conditions. The image will be stored in /var/opt/ignite/archives/ After the image creation is complete, the Compute Node should be opened for accepting Clusterware jobs.: % badmin hopen If the system you want to archive was not installed as part of the HP Technical Cluster, it will not contain the sysimage_create tool. In this case, the make_sys_command should be used directly to create the golden image. Verify that Ignite-UX is installed on the system: % swlist -l product Ignite-UX If it is not, you will need to obtain and install this product first. http://software.hp.com Read the man pages for make_sys_image(1m) to find out more about creating system images. The user can control what files are included in an image through the use of the -l, -g and -f arguments to make_sys_image. See the man pages for make_sys_image(1m) for more information. By default, files in /tmp and most files in /var/adm and /var/tmp are excluded. More importantly, many of the system configuration files in /etc are replaced by "newconfig" versions. The reasoning behind this is that the archive may be used on a different system where the settings from the "golden" machine will be incorrect. A complete list of files which will be excluded from an image can be viewed by using the command: % /opt/ignite/data/scripts/make_sys_image -x -s local Users may wish to exclude additional files by using the -f option to make_sys_image. If the archive is only intended to reinstall the machine where it was made, make_sys_image -l may be used to include all configuration files in their current state. Back to Top

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
Ensure that the system is not being used. It is advisable that the system stop
accepting new LSF jobs while the archive is being made:
%
badmin hclose <hostname>
In addition, you should either wait until all running jobs complete, or
suspend them:
%
bstop -a -u all -m <hostname>
Execute sysimage_create on the Management Server and pass the name of
the file from which you would like the image to be made. For example:
%
/opt/clusterpack/bin/sysimage_create <hostname>
Monitor the output for possible error conditions. The image will be stored
in /var/opt/ignite/archives/<hostname>
After the image creation is complete, the Compute Node should be opened for accepting
Clusterware jobs.:
%
badmin hopen <hostname>
If the system you want to archive was not installed as part of the HP Technical Cluster, it will
not contain the sysimage_create tool. In this case, the make_sys_command should be used
directly to create the golden image. Verify that Ignite-UX is installed on the system:
%
swlist -l product Ignite-UX
If it is not, you will need to obtain and install this product first.
Read the man pages for make_sys_image(1m) to find out more about creating system images.
The user can control what files are included in an image through the use of the -l, -g and -f
arguments to make_sys_image. See the man pages for make_sys_image(1m) for more
information. By default, files in /tmp and most files in /var/adm and /var/tmp are excluded.
More importantly, many of the system configuration files in /etc are replaced by "newconfig"
versions. The reasoning behind this is that the archive may be used on a different system where
the settings from the "golden" machine will be incorrect. A complete list of files which will be
excluded from an image can be viewed by using the command:
%
/opt/ignite/data/scripts/make_sys_image -x -s local
Users may wish to exclude additional files by using the -f option to make_sys_image. If the
archive is only intended to reinstall the machine where it was made, make_sys_image -l may be
used to include all configuration files in their current state.
Back to Top