Go to main content

Using Unified Archives for System Recovery and Cloning in Oracle® Solaris 11.4

Exit Print View

Updated: September 2020

How to Deploy a System From a Unified Archive by Using AI

If you use Automated Installer (AI) to deploy an archive, ensure that you have a compatible AI service and AI manifest. For example, if the archived system is Oracle Solaris 11.3, any Oracle Solaris 11.3 or 11.3 SRU version AI service is compatible. Each archive does not require its own service. The specific archive deployed is determined by the manifest used for a specific deployment.

Before You Begin

You must be an administrator with the correct rights profiles to perform this task. See Using Rights Profiles with Unified Archives.

You must have an existing AI server with correct configurations, including the correct web server file directories. For details, see Configuring an AI Server in Automatically Installing Oracle Solaris 11.4 Systems.

  1. (Optional) If needed, create a new install service on the AI server.
    $ installadm create-service -n new-service -s iso-image

    Ensure that the ISO file includes the FMRI location for the current operating system version.

  2. (Optional) If needed, associate the install client with a service.
    $ installadm create-client -e client-MAC-address -n image-location
  3. Configure an AI manifest for the install client.

    Either edit the default manifest XML file or create a new manifest XML file referencing the archive changes. On the manifest, specify the following:

    1. For software type, specify ARCHIVE.
    2. For file uri, specify the location of the archive.

      See Example XML Manifests for Archive Deployment for reference.

    Refer to Creating and Customizing an AI Manifest in Customizing Automated Installations With Manifests and Profiles for different ways of creating and editing AI manifests.

  4. Create a new manifest with the updated manifest XML file.
    $ installadm create-manifest -n new-service -m manifest -f file
  5. Confirm both that the service was created and that the new manifest was applied to the service.
    1. Verify the new service.
      $ installadm list -n new-service
    2. Verify the new manifest.
      $ installadm list -n new-service -m
  6. Boot the install client.
    ok boot net:dhcp - install