|
NetWorker V4.2C for Digital UNIX
Licensing Guidelines
18 February 1997 (updated to include HSM licensing) |02/18
With V3.2 and later of NetWorker, it is now possible to back up
ASE and TruCluster environments. This complicates the licensing
of NetWorker and related products. This note is intended to
summarize the information in the SPDs, clarify the capabilities
of the various licenses, explain how licensing works in a cluster
environment, and to provide some examples of cluster licensing.
This information is specific to NetWorker servers for Digital
UNIX Alpha systems.
Reference information:
POLYCENTER NetWorker Save and Restore for Digital UNIX, SPD 50.98
Digital UNIX Operating System, SPD 41.61
Server Licenses
---------------
SingleServer - SingleServer capability allows a system to backup
its local disks to a single device. Other limitations are
described in the SingleServer documentation (Singleserver.ps in
the FTP and Web areas). SingleServer capability is included with
the Digital UNIX base operating system license.
Server license - Enables networked server functionality. This
license is tiered by system type (workgroup = tier 1,
departmental = tier 2 and enterprise = tier 3) and is included in
NAS 200/300 or may be ordered separately. This license is a
prerequisite for server add-ons.
Archive license - An archive is a set of files/directories which
is saved/restored as a single entity. It is useful for saving
software releases, sets of architectural drawings, etc. This
server add-on enables archive services. This license is also
tiered by system type.
HSM license - An HSM operation automatically migrates files from |02/18
disk to another storage medium, based on a set of rules, in order |02/18
to conserve network storage resources. This server add-on enables |02/18
HSM services. This license is also tiered by system type. |02/18
Save Set Consolidation (SSC) - This server add-on enables SSC.
This license is not tiered. SSC is available in environments
where both the client and server are Digital UNIX systems.
Jukebox license - This server add-on enables jukebox random
access. This license is tiered by jukebox slot capacity. For
tapes, tier 1 = 1-16 slots, tier 2 = 1-64 slots, tier 3 = 64+
slots. See the NetWorker SPD (50.98) for optical jukebox tiers.
Each jukebox requires a separate license of the appropriate tier.
A jukebox license is now required for all autochangers and
libraries.
Client Licenses
---------------
UNIX and PC client - These licenses allow a NetWorker server
to service backup connections from UNIX and PC client systems.
A server does not require a client license to back up its own
local disks. An additional client license is required for each
client that has archiving enabled. An additional client license |02/18
is required for each client that has HSM enabled. |02/18
Cluster Client - Allows a server to provide backup/archive
services to client systems and cluster services that are part of
a cluster. Any UNIX client node which is in a cluster requires a
cluster client license. However, a server which is a member of a
cluster does not require a cluster client license to backup its
own disks. A minimum of one cluster client license is required
to enable backup of cluster services. Cluster Client licenses
are tiered by system type.
Data Module for Oracle (DMO) - Allows a client to backup Oracle
databases using NetWorker in cooperation with the Oracle
Enterprise Backup Utility (OEBU). This license is tiered by
system type and is loaded on the client system.
Note: All client licenses are loaded on the server and enable
that server to provide the licensed services to a client systems.
Client licenses are statically assigned to a specific client
systems and cannot be dynamically shared among client systems.
The Data Module for Oracle (DMO) client license is the exception,
as it is loaded on the client system.
Overview of Cluster Licensing
-----------------------------
Cluster client capability simplifies backup and restore
operations for ASE services. In the diagram below, cluster
client capability allows the volume services C, D and E to be
backed up and restored independent of the node where they are
currently mounted.
+--------------+
|network client|
+--------------+
network |
+--------------------------------+
| |
private SCSI +---------+ +---------+
bus | Node | shared SCSI bus | Node | private SCSI bus
=======| A |=======================| B |=========
| | | | | | | | |
| +---------+ | | | +---------+ |
| | | | _-_
_-_ | | | |-_-|
|-_-| | | | | |
| | _-_ | _-_ | |
| | |-_-| | |-_-| -_-
-_- | C | | | D | (Node B's
(Node A's | | | | | private data)
private data) -_- | -_-
|
_-_
|-_-|
| E |
| |
-_-
Cluster Licensing Issues
------------------------
NetWorker for Digital UNIX provides a cluster-knowledgable
client, not a cluster-capable server. At this time:
. The NetWorker databases cannot be shared between cluster nodes.
. Placing the NetWorker databases on a cluster service for
failover to the other cluster node is NOT SUPPORTED.
. Tape drives cannot be placed on the shared SCSI bus.
. LMF databases are not shared between cluster systems
. If different servers backup a single client, the backups are
totally independent.
. Using system "A" to restore a backup performed by system "B"
will require scanning the system "B" media. It is NOT SUPPORTED
to use the system "B" NetWorker database files on system "A".
Ordering NetWorker for a cluster
--------------------------------
To order NetWorker for a cluster:
Step 1: Order the appropriate tier of server license(s) (via NAS
or separately) and any add-on server licenses desired.
Step 2: Order a cluster client license for each cluster node.
You may reduce the number by one if the NetWorker server is on
one of the cluster nodes. At least one cluster client license is
required if any cluster services are to be backed up. Additional
cluster client licenses *are not* required for archive or HSM |02/18
capability.
Step 3: Order sufficient client licenses for non-cluster
networked client systems. An additional client license is
required for each client that uses archive capabilities.
Remember that client licenses are loaded on the server system,
and enable the server to handle connections from the various
clients.
Cluster Licensing Examples
--------------------------
The following examples attempt to cover common cluster
situations:
Example 1 - Dual AlphaServer 8000 cluster, two network clients,
tape drive on one cluster system.
The 8000 system with the tape drive will be the NetWorker server
and needs the following licenses -- tier 3 server (enabling full
server capability and local disk backup), tier 3 cluster client
(to backup cluster services and the other cluster node), two
network clients (for the network systems).
Example 2 - Dual 2100 cluster, plus an AlphaServer 1000
non-cluster system with tape drive for backup.
The AlphaServer 1000 will be the backup server and needs the
following licenses -- tier 1 server, two tier 2 cluster client
(to allow backup of cluster services through either cluster
node).
Example 3 - Two separate two-node AlphaServer 2100 clusters. No
network clients, tape drive on one system to back up all systems.
The server node requires the following licenses: tier 2 server,
three tier 2 cluster clients.
Example 4 - Dual AlphaServer 8000 cluster, two network clients,
tape drives on both systems, both systems to be capable of
backing up all systems.
The following licenses are required on BOTH cluster systems:
tier 3 server, tier 3 cluster client, two network client. Note
that the cluster nodes WILL NOT share the NetWorker database,
NetWorker server failover is not supported, and using one system
to restore a backup taken by the other system will require use of
the NetWorker Scanner.
Example 5 - Three node AlphaServer 2100 cluster, ten network
clients, tape drives on all systems, all systems to be capable of
backing up all systems.
All THREE cluster systems require the following licenses: tier 2
server, TWO tier 2 cluster clients, TEN network clients.
|
| NetWorker V4.3 for Digital UNIX
Licensing Guidelines
Last revised 23 May 1997
This note is intended as a NetWorker licensing "cookbook", and as
such, it summarizes the licensing information in the SPDs,
clarifies the capabilities of the various licenses, explains how
licensing works in a cluster environment, and provides some
examples of cluster licensing.
This information is specific to NetWorker servers for Digital
UNIX Alpha systems.
Reference information:
NetWorker Save and Restore for Digital UNIX, SPD 50.98
NetWorker Save and Restore Database Modules for Windows NT Alpha, SPD 55.04
NetWorker Save and Restore Database Module for Oracle, SPD 64.46
NetWorker Save and Restore Database Module for SAP R/3, SPD 64.66
Digital UNIX Operating System, SPD 41.61
Server Licenses
---------------
SingleServer - SingleServer capability allows a system to backup
its local disks to a single device. Other limitations are
described in the SingleServer documentation (Singleserver.ps in
the FTP and Web areas). SingleServer capability is included with
the Digital UNIX base operating system license.
Server license - Enables networked server functionality. This
license is tiered by system type (workgroup = tier 1,
departmental = tier 2 and enterprise = tier 3) and is included in
the StorageWorks Plus software package or may be ordered
separately. This license is a prerequisite for server add-ons.
NetWorker server is no longer bundled with systems as part of a
NAS package, and must now be ordered as line item software,
either separately or as part of the StorageWorks Plus software
package. NetWorker SingleServer is still bundled with Digital
UNIX.
Server Add-Ons
--------------
Archive license - An archive is a set of files/directories which
is saved/restored as a single entity. It is useful for saving
software releases, sets of architectural drawings, etc. This
server add-on enables archive services. This license is also
tiered by system type.
HSM license - An HSM operation automatically migrates files from
disk to another storage medium, based on a set of rules, in order
to conserve network storage resources. This server add-on enables
HSM services. This license is also tiered by system type.
Save Set Consolidation (SSC) - This server add-on enables SSC.
This license is not tiered. SSC is available in environments
where both the client and server are Digital UNIX systems.
Jukebox license - This server add-on enables jukebox random
access. This license is tiered by jukebox slot capacity. For
tapes, tier 1 = 1-16 slots, tier 2 = 1-64 slots, tier 3 = 64+
slots. See the NetWorker SPD (50.98) for optical jukebox tiers.
Each jukebox requires a separate license of the appropriate tier.
A jukebox license is now required for all autochangers and
libraries.
Client Licenses
---------------
UNIX and PC client - These licenses allow a NetWorker server
to service backup connections from UNIX and PC client systems.
A server does not require a client license to back up its own
local disks. An additional client license is required for each
client that has archiving enabled. An additional client license
is required for each client that has HSM enabled.
Cluster Client - Allows a server to provide backup/archive
services to client systems and cluster services that are part of
a cluster. Any UNIX client node which is in a cluster requires a
cluster client license. However, a server which is a member of a
cluster does not require a cluster client license to backup its
own disks. A minimum of one cluster client license is required
to enable backup of cluster services. Cluster Client licenses
are tiered by system type.
SAP R/3 Module - Allows a client to backup a SAP R/3 system via
the SAP backint backup interface. This license is tiered by
system type and is loaded on the client system.
Data Module for Oracle (DMO) - Allows a client to backup Oracle
databases using NetWorker in cooperation with the Oracle
Enterprise Backup Utility (OEBU). This license is tiered by
system type and is loaded on the client system.
Exchange - Allows the NetWorker Server to backup an Exchange
Server database on a Windows NT client system using the NetWorker
Module for Microsoft Exchange Server product. This license is
per-client and is not tiered.
SQL Server - Allows the NetWorker Server to backup a SQL Server
database on a Windows NT client system using the NetWorker Module
for Microsoft SQL Server product. This license is per-client and
is not tiered.
Note: In general, client licenses are loaded on the server and
enable that server to provide the licensed services to a client
system. Client licenses are statically assigned to a specific
client systems and cannot be dynamically shared among client
systems. The Data Module for Oracle (DMO) and SAP R/3 client
licenses are the exception, as they are loaded on the client
system.
Overview of Cluster Licensing
-----------------------------
Cluster client capability simplifies backup and restore
operations for ASE services. In the diagram below, cluster
client capability allows the volume services C, D and E to be
backed up and restored independent of the node where they are
currently mounted.
+--------------+
|network client|
+--------------+
network |
+--------------------------------+
| |
private SCSI +---------+ +---------+
bus | Node | shared SCSI bus | Node | private SCSI bus
=======| A |=======================| B |=========
| | | | | | | | |
| +---------+ | | | +---------+ |
| | | | _-_
_-_ | | | |-_-|
|-_-| | | | | |
| | _-_ | _-_ | |
| | |-_-| | |-_-| -_-
-_- | C | | | D | (Node B's
(Node A's | | | | | private data)
private data) -_- | -_-
|
_-_
|-_-|
| E |
| |
-_-
Cluster Licensing Issues
------------------------
NetWorker for Digital UNIX provides a cluster-knowledgable
client, not a cluster-capable server. At this time:
. The NetWorker databases cannot be shared between cluster nodes.
. Placing the NetWorker databases on a cluster service for
failover to the other cluster node is NOT SUPPORTED.
. Tape drives cannot be placed on the shared SCSI bus.
. LMF databases are not shared between cluster systems
. If different servers backup a single client, the backups are
totally independent.
. Using system "A" to restore a backup performed by system "B"
will require scanning the system "B" media. It is NOT SUPPORTED
to use the system "B" NetWorker database files on system "A".
Ordering NetWorker for a cluster
--------------------------------
To order NetWorker for a cluster:
Step 1: Order the appropriate tier of server license(s) (via NAS
or separately) and any add-on server licenses desired.
Step 2: Order a cluster client license for each cluster node.
You may reduce the number by one if the NetWorker server is on
one of the cluster nodes. At least one cluster client license is
required if any cluster services are to be backed up. Additional
cluster client licenses *are not* required for archive or HSM
capability.
Step 3: Order sufficient client licenses for non-cluster
networked client systems. An additional client license is
required for each client that uses archive capabilities.
Remember that client licenses are loaded on the server system,
and enable the server to handle connections from the various
clients.
Cluster Licensing Examples
--------------------------
The following examples attempt to cover common cluster
situations:
Example 1 - Dual AlphaServer 8000 cluster, two network clients,
tape drive on one cluster system.
The 8000 system with the tape drive will be the NetWorker server
and needs the following licenses -- tier 3 server (enabling full
server capability and local disk backup), tier 3 cluster client
(to backup cluster services and the other cluster node), two
network clients (for the network systems).
Example 2 - Dual 2100 cluster, plus an AlphaServer 1000
non-cluster system with tape drive for backup.
The AlphaServer 1000 will be the backup server and needs the
following licenses -- tier 1 server, two tier 2 cluster client
(to allow backup of cluster services through either cluster
node).
Example 3 - Two separate two-node AlphaServer 2100 clusters. No
network clients, tape drive on one system to back up all systems.
The server node requires the following licenses: tier 2 server,
three tier 2 cluster clients.
Example 4 - Dual AlphaServer 8000 cluster, two network clients,
tape drives on both systems, both systems to be capable of
backing up all systems.
The following licenses are required on BOTH cluster systems:
tier 3 server, tier 3 cluster client, two network client. Note
that the cluster nodes WILL NOT share the NetWorker database,
NetWorker server failover is not supported, and using one system
to restore a backup taken by the other system will require use of
the NetWorker Scanner.
Example 5 - Three node AlphaServer 2100 cluster, ten network
clients, tape drives on all systems, all systems to be capable of
backing up all systems.
All THREE cluster systems require the following licenses: tier 2
server, TWO tier 2 cluster clients, TEN network clients.
|