StoreOnce VSA

QuickSpecs
HPE StoreOnce VSA Software
Configuration Information
Page
13
Supported configurations and best practices for high availability (HA) deployments
For a high performance and high availability deployment the StoreOnce VSAs and the StoreOnce High Availability Manager should
follow these best practices.
• The VMware
vCenter Server and the StoreOnce High Availability Manager should be deployed on a VMware vSphere High
Availability cluster.
• All hosts in the cluster have the same or similar specification and are running the same VMware vSphere version.
• For Fibre Channel
data connections, each host has supported Fibre Channel HBAs available for the hosted StoreOnce VSA.
See the StoreOnce support matrix * for supported HBAs.
• The VMware vSphere cluster(s) that
host the StoreOnce VSAs should be dedicated to the StoreOnce VSA(s) and not host
other virtual machines except a StoreOnce High Availability Manager.
• The hosts and shared storage have sufficient resources to enable the performance and capacity required –
as defined in the
resource requirements section above.
•
The cluster should have a spare host that does not host any StoreOnce VSAs. This spare host can act as a failover destination
for StoreOnce VSAs on one, two or three other hosts in the cluster.
• Each vSphere host can have maximum 5 StoreOnce VSAs. A maximum of 2 of these can use Fibre Channel data connections.
• Redundant data connections from the data protection software to all the hosts in the vSphere cluster.
• StoreOnce federated management is used with
the StoreOnce High Availability Manager configured as the federation lead
and all StoreOnce VSAs in the high availability configured as federation members.
• Each StoreOnce High Availability Manager can manage the failover of StoreOnce VSAs in up to 10 vSphere Clusters.
Data protection software compatibility
During a failover process, the StoreOnce VSA will appear as offline/unavailable to the data protection software. Different da
ta
protection software will handle this unavailability differently for
the resumption of backup, restore or copy jobs. Settings in the backup
software for timeouts and restart options need to accommodate this.
If it is required to return a failed over StoreOnce VSA to a repaired or replaced host, it can be manually failed
over to that host using
the High Availability Manager console.
See the StoreOnce support matrix
* for details of the data protection software supported for StoreOnce VSA in HA deployments.
NOTE:
*This requires a HPE Passport account – the single sign on for HPE websites and services. Create an account
here.
Licensing and Part Numbers
Licensing overview
The StoreOnce VSA has a simple and flexible, capacity-
based license scheme. All purchased licenses are perpetual and include 3
years HPE Pointnext support entitlement.
On installation, a unique serial number is created for the StoreOnce VSA and a 90-day, instant-
on demo license is activated. Before
the end of this 90 days the StoreOnce VSA must have one of the three licenses below added:
• Individual license
• License from a license server
• Freeware license
For an individual license and a freeware license, th
e StoreOnce VSA serial number is needed to acquire the license. These StoreOnce
VSA licenses are locked to the serial number and cannot be transferred to another StoreOnce VSA.
For the StoreOnce license server the Locking Code (on the APLS GUI License Mana
gement page) is needed to acquire the StoreOnce
License Server licenses. The StoreOnce VSA deployment and license option are shown in the diagram below.
NOTE: Once a licensing mode (individual license | connect to license server) is selected it cannot b
e changed. After a StoreOnce
VSA is given a freeware license it cannot be connected to a license server.
NOTE: When using the 90-day, instant-
on demo license up to 500 TB of capacity can be configured. When licenses are added to
continue use beyond the 90 day demo period the licensed capacity must be greater or equal to the configured capacity.