Rocket U2 License Requirements Guide · For more information, email your Rocket sales...

12
License Requirements Guide © Rocket Software, Inc. 2017 Page 1 of 12 Rocket Replication License Requirements Guide August 2017

Transcript of Rocket U2 License Requirements Guide · For more information, email your Rocket sales...

Page 1: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 1 of 12

Rocket Replication License

Requirements Guide

August 2017

Page 2: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 2 of 12

Table of Contents

Contents Table of Contents .................................................................................................... 2

Introduction ............................................................................................................ 3

Definitions .............................................................................................................. 3

License Guidelines ................................................................................................... 3

Standby Licenses .................................................................................................. 4

HA/DR Solutions ................................................................................................... 4

Configurations......................................................................................................... 4

Standard Backup .................................................................................................. 6

Virtualization Backup ............................................................................................ 6

Replication and Repurpose ..................................................................................... 7

U2 Replication – Single machine ............................................................................. 7

U2 Replication – Separate machine(s) ..................................................................... 8

D3 Hot Backup ..................................................................................................... 8

3rd Party Replication ............................................................................................. 9

Switching SAN #1 ................................................................................................. 9

Switching SAN #2 ................................................................................................ 10

Standard Virtualization ......................................................................................... 10

Multi-site Datacenter #1 ....................................................................................... 11

Multi-site Datacenter #2 ....................................................................................... 11

Conclusion .......................................................................................................... 12

Document History ................................................................................................... 12

Page 3: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 3 of 12

Introduction This document describes several common Rocket MV Replication software configurations

and their impact on software license requirements.

These guidelines discuss how to determine if your configuration requires the acquisition of

additional matching or non-matching license(s) based on your license usage.

For more information, email your Rocket sales representative, Rocket MV Distributor, or

[email protected] with any questions related to this document.

Definitions For the purposes of this document, the following definitions apply:

Disaster Recovery – infrastructure set up to restore operations after a natural or

human-induced disaster.

High Availability – a machine architected to recover quickly in case of individual

component failures.

Installed/Installation – Rocket Software programs are considered to be installed if

they are placed in a position that does not require transfer from any other media

and are ready to use. They do not need to be authorized to be ready to use.

License – the specific configuration of options, features and user counts authorized

and used by the client.

Serial Number – a unique number associated with the License that is issued to help

ensure that the License is installed one time and using only the authorized options,

features and user counts.

Standard License – a license that has no usage limitations.

Standby License – a limited use license available for High Availability/Disaster

Recovery (HA/DR) solutions.

License Guidelines In order to understand how many Licenses (Serial Numbers) are required and whether the

Licenses must match, two basic questions must be answered:

1) How many machines have software installed simultaneously?

2) Is the software configured to support HA/DR?

The basic guidelines for License acquisition are:

• A unique Serial Number for each installed program must be acquired for each machine.

This includes stand-alone machines, replicated/mirrored machines (regardless of

technology) and virtual machines (Workload Partitions (WPARs), Logical Partitions

(LPARs), zones, etc.).

• If your configuration supports High Availability AND Disaster Recovery your Licenses

must have matching options, features and user counts.

Finally, if two (2) Licenses, or more, of software are required and they must match, there

are two options:

Page 4: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 4 of 12

1) Standard Licenses – Same software; options, features and user counts must match;

no usage restrictions; standard pricing.

2) Standby Licenses – Same software; options, features and user counts must match;

limited use; discounted pricing.

Standby Licenses Standby Licenses support UniData and UniVerse in a HA/DR configuration. Rocket Software

offers U2 Replication and Recoverable File System (RFS) technologies as well as

Professional Services to assist in implementation of high availability solutions.

Regardless of the technology used to protect your D3, UniData or UniVerse solution with

both High Availability and Disaster Recovery, matching Licenses are required. Matching

Licenses can be either Standard Licenses or Standby Licenses. Standby Licenses, as

described below, may also be used, if desired, for solutions that provide:

i) only High Availability, or

ii) only Disaster Recovery.

➢ A Standby License can mirror data, update files, and synchronize programs, data or

other resources from the publisher machine.

➢ A Standby License can be used for development and testing (including failover

testing).

➢ A Standby license may also be used for the following read-only activities:

• reporting

• dashboards

• replication

• extraction

The Standby License may not be used for production or other operational uses.

HA/DR Solutions When you are running Rocket MV machine-based programs in a HA/DR configuration you

must acquire matching Licenses. The Licenses must have unique Serial Numbers and be

configured identically (e.g. options, features, user counts and, maintenance status).

Matching Licenses can be either Standard Licenses with no usage restrictions or Standby

Licenses with usage limitations as described below.

Rocket MV machine-based programs comprise D3, UniData, UniVerse, U2 Web DE,

SystemBuilder, and SB/XA.

Note: This replaces all previous policies regarding Backup Programs.

Configurations You may have Rocket MV machine-based programs installed on one or more machines for

a variety of purposes including, but not limited to, report machine, data warehouse,

development, testing, production, high availability and/or disaster recovery. An installation

of Rocket MV machine-based programs may serve one or more of the above-mentioned

uses.

Depending on the configuration you may or may not be required to have a second unique

License (Serial Number). If you are required to have a second License, it may or may not

be required to match.

Page 5: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 5 of 12

The following Configuration table summarizes some of the combinations of uses and their

License requirements. Each configuration will be explained in more detail below the table:

Configuration High

Availability

Disaster

Recovery

Additional

License

Required

Licenses

Must

Match

Unique

Serial

Numbers

Standard

Backup

No Yes No N/A No1

Virtualization

Backup

No Yes No N/A No1

Replication &

Repurpose

No No Yes No2 Yes

U2 Replication

Single Database

No No N/A N/A N/A

U2 Replication

Separate

Database(s)

Yes Yes Yes Yes Yes

D3 Hot Backup Yes Yes Yes Yes Yes

3rd Party

Replication

Yes Yes Yes Yes Yes

Switching SAN

#1

Yes No No N/A

Switching SAN

#2

Yes No Yes No

Standard

Virtualization

Yes No No N/A

Multi-site

Datacenter #1

Yes Yes Yes Yes Yes

Multi-site

Datacenter #2

Yes Yes Yes Yes Yes

1 – If the backup of your publisher machine is restored to another actively running

machine while the publisher is still active, an additional unique serial number is required.

2 - If you are replicating the entire publisher machine to the subscriber machine for the

purpose of HA/DR, you need multiple unique Serial Numbers and the License

configurations must match.

Page 6: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 6 of 12

Standard Backup In a standard backup configuration, the software is installed on only one machine. The

machine is periodically backed up to a separate media (e.g. tape or hard drive). This

scenario supports disaster recovery but not high availability.

In case of a disaster there are two options, 1) the backup may be restored to the publisher

machine or, 2) if the publisher machine is not reparable, the data machine may have to be

installed and configured on a subscriber machine before restoring the backup.

For a standard backup configuration, only one license is required.

Virtualization Backup Backups can also be done using virtualization technologies such as snapshots. In this case,

the database is only installed on one machine at a time. In the example below, snapshots

were used to do the backup and restore in the case of a disaster. If the snapshot is

restored to a second machine, MV software may have to be installed and configured. In

this scenario, only one License is required. This usage is considered to be disaster recovery

only.

Page 7: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 7 of 12

Replication and Repurpose MV software may be installed on two machines for the purpose of replicating data from the

publisher machine to be repurposed for reporting, etc. on a subscriber machine. In this

case, there will be a selected subset of data being replicated for this subscriber purpose.

This usage is neither high availability nor disaster recovery.

In this configuration, you need two unique Serial Numbers and the Licenses do not need to

match.

U2 Replication – Single machine In this configuration, the software is installed on a single, partitioned machine and U2

Replication is being used to keep the installs in sync.

In this configuration, there can only be a single unique Serial Number.

Page 8: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 8 of 12

U2 Replication – Separate machine(s) In this configuration software is installed on two or more machines at the same time and

U2 Replication is being used to keep the machines in sync. This configuration supports

both HA/DR with the ability to quickly failover to the subscriber machine in case of a

disaster as well as the ability to quickly fail back to the publisher machine upon recovery.

In this configuration, you need multiple unique Serial Numbers and the License

configurations must match. They can either be Standard Licenses or Standby Licenses.

D3 Hot Backup In this configuration software is installed on two or more machines at the same time and

D3 Hot Backup is being used to keep the machines in sync. This configuration supports

both HA/DR with the ability to quickly failover to the subscriber machine in case of a

disaster, as well as the ability to quickly fail back to the publisher machine upon recovery.

Each subscriber requires a unique Serial Number, the License configurations must match

and they must be Standby Licenses.

D3 Hot Backup on AIX and Linux supports the ability to daisy chain multiple subscribers,

providing the capability to have subscribers in multiple locations for HA/DR capabilities. D3

Hot Backup on Windows is limited to a single subscriber.

Page 9: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 9 of 12

3rd Party Replication In this configuration, software is installed on two machines and third party replication

technology is being used to keep the machines in sync. This configuration supports both

high availability and disaster recovery.

In this configuration, you need unique Serial Numbers and the License configurations must

match. They can be either Standard Licenses or Standby Licenses.

Switching SAN #1 In this configuration, the MV database is installed on the Storage Attached Network (SAN)

drive that is shared between two machines. In this scenario, only one machine can be

actively accessing the MV database at any one time. This supports high availability but

not disaster recovery.

In this configuration, only one Serial Number is required.

Page 10: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 10 of 12

Switching SAN #2 In this configuration, the MV database is installed on two machines at the same time. The

application data is stored on a shared SAN drive. This scenario supports high availability

but not disaster recovery.

This configuration requires two unique Serial Numbers and the Licenses are not required to

match.

Standard Virtualization In this configuration, the software is installed on one virtual machine at a time. The

application data is stored on a shared SAN. In the case of a machine outage, the virtual

machine may be migrated from one physical machine to another. This scenario supports

high availability but not disaster recovery.

In this scenario, only one software License is required.

Page 11: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 11 of 12

Multi-site Datacenter #1 In this configuration, MV is installed on both SANs and the two SANs are being kept in

sync via mirroring or replication.

This scenario supports both high availability and disaster recovery.

In this scenario, two Licenses are required and they must match. The second License may

be either a Standard License or a Standby License.

Multi-site Datacenter #2 In this configuration, the software is installed on both the publisher and subscriber

machine. The application files and data are stored on a SAN which is kept in sync with a

second SAN via mirroring or replication. This scenario supports both high availability and

disaster recovery.

In this scenario, two MV software Licenses are required and they must match. The second

license may be either a Standard License or a Standby License.

Page 12: Rocket U2 License Requirements Guide · For more information, email your Rocket sales representative, Rocket MV Distributor, or u2askus@rocketsoftware.com with any questions related

License Requirements Guide © Rocket Software, Inc. 2017 Page 12 of 12

Conclusion This document shows several common Rocket configurations and their licensing

requirements; however, it is not possible to cover all configurations. If you are unsure if

your configuration matches one of these, please see the general guidelines above. If you

have additional questions, please contact your Rocket software provider.

Document History This section highlights the major changes in the current version

August 2017

• Revised the Configuration table

• Added U2 Replication – Single database

• Added U2 Replication – Separate database(s)

• Added D3 Hot Backup