9.4 Cloning an OES Server Post OES Installation and Configuration

This section describes the procedures to clone an OES server post OES installation and configuration. When there is a server crash, you can use this procedure to reinstall the server with the same configurations that existed before the crash. This is a two step task: generate the autoinst.xml file post OES installation and configuration, use that XML file to reinstall and configure the server.

9.4.1 Generating the autoinst.xml File

The autoinst.xml file contains all the configuration details of the components, passwords, IP address, and so on. Store this file in a secure location, and use it to reinstall and reconfigure your OES server when there is a crash.

To generate the autoinst.xml file:

Log on to the OES server with administrative privileges and execute the following command: yast2 clone_system.

This generates an autoinst.xml file at /root. Generate this file as and when you make some configuration changes to the server.
Store this file in a secure location for future use.

NOTE:The generated autoinst.xml file will have the XML tags of the OES components that you have not installed and configured. This does not affect any functionality. When you use the generated autoinst.xml file, only the components that are available under the <patterns> tag will be installed.

9.4.2 Using the autoinst.xml to Install or Reinstall an OES Server

To install or reinstall an OES server using autoinst.xml:

Edit the autoinst.xml file, and modify the following:

Replace all instances of “Replace this text with the real password” with eDirectory password.
Specify eDirectory password inside runtime_admin_password and admin_password under oes-ldap tag.
If you install or re-install DSfW server, see Installing DSfW Using AutoYaST.

Locate and remove the entire net-udev section that has the details about the MAC address.

<net-udev config:type="list">
    <rule>
        <name>eth0</name>
        <rule>ATTR{address}</rule>
        <value>00:0c:29:4d:e0:72</value>
    </rule>
</net-udev>

Locate and remove the user and group gdm entries. For more information, see TID 7006641 Error: Could not update ICEauthority file /var/lib/gdm/.ICEauthority.

 <group>root
      <encrypted config:type="boolean">true</encrypted>
      <gid>112</gid>
      <group_password>!</group_password>
      <groupname>gdm</groupname>
      <userlist></userlist>
 </group>  

 <user>
      <encrypted config:type="boolean">true</encrypted>
      <fullname>Gnome Display Manager daemon</fullname>
      <gid>112</gid>
      <home>/var/lib/gdm</home>
      <password_settings>
        <expire></expire>
        <flag></flag>
        <inact></inact>
        <max>99999</max>
        <min>0</min>
        <warn>7</warn>
      </password_settings>
      <shell>/bin/false</shell>
      <uid>107</uid>
      <user_password>*</user_password>
      <username>gdm</username>
    </user>

Host the modified autoinst.xml file in a HTTP server.
Boot the OES server with OES24.4-DVD-x86_64-DVD1.iso.
In the installation screen, select Install, and specify the following information:

autoyast=<The HTTP location where the autoinst.xml file is hosted> netsetup=hostip hostip=<enter machine IP> netmask=<enter the netmask> gateway=<enter the gateway>

or

autoyast=<The HTTP location where the autoinst.xml file is hosted> ifcfg="eth0=<ip_address/<netmask>, <gateway>, <nameserver>" sethostname=0 install=<install_source_location_if_network_based>

For example:

autoyast=http://198.162.1.1/autoinst.xml netsetup=hostip hostip=192.168.1.2 netmask=255.255.254.0 gateway=192.164.1.254

or

autoyast=http://198.162.1.1/autoinst.xml ifcfg="eth0=192.168.1.2/23, 192.164.1.254, 192.164.1.1" sethostname=0
Press Enter and the OES installation and configuration starts and completes without any user intervention.

If OES is running in a UEFI Secure Boot environment, you need to perform additional steps, see Section 11.0, Deploying OES in a UEFI Secure Boot Environment.

NOTE:Cloud Integrated Storage (CIS) does not work, if autoinst.xml file is copied from already installed and configured OES 2018 or later server (without CIS) and manually add the CIS tags into autoinst.xml and then install OES 2018 or later server using the modified autoinst.xml. For CIS to work, along with adding the CIS tags, ensure to enable the ipv4_forward and FW_MASQUERADE attributes under firewall section in the autoinst.xml file and then install the OES 2018 or later server.

For example:

<ipv4_forward config:type="boolean">true</ipv4_forward>

<FW_MASQUERADE>yes</FW_MASQUERADE>

However, if OES 2018 or later server is installed using autoinst.xml created from already installed OES 2018 or later server (with CIS), then CIS works fine.