Solstice Backup Licensing Overview

The aim of this document is to shed some light on the types of licenses (enabler codes) available within Solstice Backup (SBU). What this document does NOT do is discuss the workings of SBU, however I have incorporated a small section covering common queries in relation to SBU licensing.

This document is also relevant to other OEM branded releases of Legato NetWorker.

NOTE: The Solstice Backup product can be installed without a license and will provide full functionality for 30 days.

After 30 days the product will disable itself, you will however, be allowed to perform restores of data after this period. Once the server has been disabled you will require enabler codes in order for SBU to become functional again.

What are the SBU licenses?

nwadmin gui SBU handles licensing at various levels, namely:

  • The Server
  • Storage Nodes
  • Jukeboxes
  • Clients
  • Specialised Modules
  • Update Codes

Server Licenses

This license (also known as the 'Base Enabler') is the most important SBU license of all. An incorrectly installed server license can cause a wide range of problems with an SBU server.

Currently there are three different types of server enablers (workgroup, network and power editions), however, in previous versions of SBU other base versions existed, so it is important to understand what functionality is granted by each type of enabler. We will examine each type of server enabler and what it does.

  • Network Edition w/o Turbo functionality (SBU versions 4.2 and earlier) This type of enabler will allow SBU interface with up to 10 clients (including the server itself), but will not allow a Jukebox, clients of other UNIX flavours, or clients of other Operating Systems such as DOS, NT, or NetWare. It allows the use of up to 2 drives. As the name implies, these codes are for use only on SBU 4.2 and EARLIER. A "Turbo" enabler will allow this type of server to use a jukebox or some of the speciality modules.
  • Server Edition This type of enabler will have slightly different functions for SBU versions 4.2.2 and above versus versions below 4.2.2. At all versions of SBU, this enabler is NOT network aware and does not allow clients, other than the server itself, this is true regardless of how many client pack enablers are installed. Below SBU 4.2.2, this enabler allows the use of 1 tape drive on the Sun server only with no added functionality. Starting at SBU version 4.2.2, this enabler supports up to 16 tape drives, Jukeboxes of various sizes, and speciality modules.
  • Data Backup Utility Like the Server Edition, the DBU provides the basic functions for backup and recovery of data on a single system to a single tape drive, you cannot install additional capabilities like client packs or jukebox enablers, customers need to purchase one of the SBU enablers for workgroup/network or even power edition for these functions.
  • Workgroup Edition This enabler is network aware and supports up to 7 client connections in addition to the server, without additional client packs. It supports up to 4 tape devices, and jukeboxes to a maximum of 12 slots, additional client packs, clients from different Operating Systems, storage nodes, and speciality modules.
  • Network Edition / Turbo 10 (versions: 4.2.6, 5.0.1, 5.1, 5.5.1, 6.0.1) This is the enabler that most customers use. It is network aware and supports up to 9 clients in addition to the server, without additional client packs. It supports up to 16 tape drives, additional client packs, Jukeboxes of various sizes, clients from different Operating Systems, storage nodes, and speciality modules.
  • Power Edition The Power Edition does everything that the Network Edition / Turbo 10 enabler does with some added benefits. The Power Edition supports up to 32 tape drives, parallelism up to 64 (up to 32 for Network Edition / Turbo 10 ), buffers the backups to enhance data streaming, and includes the "High-Speed Device" speciality module.

The Turbo Enabler

What is this "Turbo" Enabler? Simply, it is a code that allows access to more features than the original server enabler code. It is an old concept in SBU, starting in version 4.1.2. The "Turbo" functions were incorporated into the "Network Edition / Turbo 10" server enabler as of version 4.2.6. The only times that you are likely to see the use of a separate Turbo enabler is in the event that a given server was upgraded several times and, eventually, the nsr.res file has become corrupt.

The Client Pack Enablers

A network aware SBU server will come with native support for a limited number of clients, usually 4, 8 or 10, of the same platform as the server. A client pack simply allows the network aware server to back up additional machines of the same platform as the server.

The Jukebox Storage Module (JSM) Enablers

A JSM enabler is required for SBU to make use of any type of automated tape library. JSM enablers come in a large variety of sizes to accommodate different sized jukeboxes. The number associated with a JSM enabler is equal to the MAXIMUM number of tape slots that a library can hold. Each library (jukebox) must have it's own JSM enabler.

NOTE: A JSM enabler must be used in a single instance per jukebox. You cannot install 2x 32 slots JSM enablers totalling 64 slots in order to utilise a jukebox with 60 slots, you will need to acquire a single 64 slot JSM enabler code. This is also true if you have an L9 jukebox with 9 slots and a 32 slot JSM, you cannot use the remaining 23 slots for another jukebox.

Storage Nodes Enablers

A storage node is simply a SBU client, other than the server, that has some sort of tape device that you want to use to do SBU backups. You will require a storage node license to use this tape unit under SBU. A storage node will support up to 16 tape drives, but will need it's own JSM enablers (installed on the server) if a jukebox is to be used. A storage node cannot be used unless the server has at least one tape drive configured. Bootstrap information will not get saved to a storage node.

Specialised Module Enablers

These modules include the Business Suite Modules for Oracle, Informix, SAP, Sybase, and Lotus Notes in order to provide hot backups. There are modules to allow for clients that are PC, NT, NetWare, other platforms and other UNIX flavours. Modules also exist for Hierarchical Storage Management (HSM), data archiving and SNMP.

Update Enablers

Update enablers are required to upgrade SBU from one version to another. Customers pay for the 'update enabler code', there are no "temporary update enablers."

  • Update/1 Required to upgrade from 4.0.2 to 4.1.2
  • Update/2 Required to upgrade from 4.0.2 or 4.1.2 to 4.2.2
  • Update/5 Required to upgrade from 4.2.x to 5.0.1, 5.1, to 5.1.1
  • Update/6 Required to upgrade from 5.0.1, 5.1, or 5.1.1 to 5.5.1
  • Update/7 Required to upgrade from 5.5.1 to 6.x

NOTE: If you are upgrading from 5.1 to 6.x you will need both 'Update/6' and 'Update/7' licenses

Entering/Removing Enabler Codes

All SBU licenses are installed on the SBU server. NO licenses are installed on clients or storage nodes. Enabler codes are installed in either of two ways; through the command line or using the SBU administration GUI.

To enter the enabler code from the command line, use the nsrcap command. The nsrcap command has several options:

# /usr/sbin/nsr/nsrcap -help
usage: nsrcap [-vn] -{c|u|d|l} [enabler-code]
-c     Used to enter a new enabler code for a feature that is not
       currently installed 
-u     Used to Upgrade an existing server, or base, enabler.
-d     Downgrades a base enabler. Once downgraded, an enabler cannot 
       go back to the old level.
-v     Displays verbose information about the enabler entered.
-n     Used to check if an enabler is valid. Does not actually enter the

Thus, the commands to check the validity and type of enabler code would be:

# /usr/sbin/nsr/nsrcap -vn -c <new_enabler_samp>

and, then to enter a new enabler code would be:

# /usr/sbin/nsr/nsrcap -c <new_enabler_samp>

To install enabler codes through the nwadmin GUI:

  • pull down the Server menu and select Registration
  • Click on the Create button
  • Enter the enabler code in the box, click Apply

Deleting an enabler code should only be done through the GUI. Once an enabler is deleted, that function will no longer exist until the enabler is re-entered.

  • pull down the Server menu and open the Registration window,
  • select the enabler, and click the Delete button

NOTE: A server license (base enabler) cannot be deleted in the GUI. They can be upgraded or downgraded through the command line using nsrcap. These licenses can ONLY deleted using the nsradmin command-line based administrative utility.

Getting Enabler Codes Authorised

Once an enabler code is entered, it is valid for a period up to 45 days. To make the enabler permanent, it must still be Authorised. Authorisation is done by the Sun Licensing Centre. They can be contacted via phone or email.:

  • Phone 00800 664 664 66
  • E-mail

NOTE: The License Centre will not authorise SBU demo licenses (evaluation enabler codes).

You will need to send the License Centre the following information:

  • The hostid (not the hostname) of the computer on which the SBU server executes.
  • The enabler codes of each product for which they wish to get codes.

They will ask for information that can be printed from the nwadmin GUI by going to:

  • Click Server -> Registration
  • Click View -> then click on Tabular
  • Select File -> Print

Have the print out on hand when calling.

Using the hostid and the enabler code of the specific product to enable, the License Centre computes an authorisation code, and sends this code back to you.

Once received enter the authorisation key against the enabler code through the GUI and the product is authorised.

NOTE: Authorisation Codes are 'hostid' specific. If the hostid is changed or the server is moved to another host, new Authorisation codes must be acquired from the License Centre and entered.<?p>

Other Enablers

Most enabler codes have 45 day evaluation periods. have an evaluation period. There are also enabler codes that do not These codes are given to customers only by the Licensing Group. These codes include:

  • All Update Enabler Codes
  • JSM-9 Enabler -> This enabler was specially made for the L9 library
  • Shared Library Enabler -> This is a new concept for SBU 6.x

NOTE: SBU demo licenses (evaluation enabler codes) cannot be authorised.

Basic License Troubleshooting

This is not a definitive guide to solving all SBU license issues, these are really the ones that I' have seen get logged in the Solution Centre by customers on a number of occasions:

Cannot load license resource

An attempt was made to manually modify a License resource, or an application failed to provide the required license attribute values to the service. This problem might have occurred because:

  1. An enabler for a different platform was entered to enable an SBU product or feature.
  2. The License resource is corrupted.


  1. Verify that the enabler code entered is correct, using the command:
    # nsrcap -c -v -n
  2. Recover a previous version of the SBU resource file (nsr.res) from backup or clone volumes.
Copy violation - servers '<hostname>' and '<hostname>' have the same software enabler code, '<enabler-samp>'.

The SBU server has detected another server on the LAN with the same enabler code.


  1. Stop the SBU server or delete the enabler from the offending server.
  2. Remove the offending enabler code on your server, then add a different enabler code on the host or the alternate host.
License enabler #<enbler-samp> (<product or feature>) will expire in <n> day(s)

The specified enabler code will expire in the specified number of days.


  1. Authorise the specified enabler code through the nwadmin GUI.
  2. If you do not have an authorisation code for this enabler, contact the License Centre.
Registration info event: server is disabled (copy violation)

The SBU server has multiple network interfaces.


  1. Add the additional aliases for the to the client resource for the server using nwadmin.
Server disabled; The evaluation enabler code for the expired. Install the permanent enabler code.

The evaluation period for the feature has expired.

If you received this message after you entered the permanent enabler and authorisation codes, this message might have appeared because:

  1. The enabler code that you entered is no longer valid.
  2. The nsr.res file is corrupted.


  1. Use the nsrcap command to verify the enabler code.
  2. Install license enablers to enable the feature.
  3. Recover the nsr.res file from backup or clone volumes.
The feature <feature> is not properly enabled

This error indicates a licensing problem with the backup server software and must be resolved on the backup server before you can use the specified feature. This problem might have occurred because:


  • The specified feature is not enabled.
  • The wrong operating system version of the enabler code for the feature was used.
  • The enabler code for the feature is faulty
  • The version of the enabler code does not match the version of the SBU module.


    1. Use the nsrcap command to verify the enabler code.
    2. Enable the feature.
    3. If you do not have an enabler code for the appropriate operating system, contact the License Centre. Use the evaluation enabler codes until permanent enabler codes can be provided.
    4. Remove and install the correct version of the SBU module.
    The jukebox <jukebox> is not properly licensed. Make sure the jukebox is properly enabled and authorised
    1. The Autochanger Module is not enabled.
    2. You have applied the wrong jukebox enabler code for the number of # in the library.


    1. Enter the enabler code for the Autochanger Module into the license resource.
    2. Obtain the correct enabler code for the # slots on the jukebox.