StoreOnce VSA

QuickSpecs
HPE StoreOnce VSA Software
Standard Features
Page
7
APLS operation
•
To acquire and maintain use of licenses the StoreOnce VSA must be connected to the APLS. The connected StoreOnce VSAs
are polled approximately each hour to check connection to the APLS.
• On connection to the APLS a 1 TB capacity license is allocated to the StoreOnce VSA.
•
Licenses returned, using the StoreOnce VSA management console, are added back to the APLS pool and available for
allocation to any connected StoreOnce VSA.
•
If the StoreOnce VSA is disconnected from the APLS, the allocated licenses remain with the StoreOnce VSA for 7 days from
the most recent connection and all capacity and features enabled by the allocated licenses remain usable.
• If the StoreOn
ce VSA is disconnected for more than 7 days the allocated licenses are returned to the APLS and the StoreOnce
VSA moves to an unlicensed (read only) state.
• After 7 days and for up to 60 days from the most recent connection, the StoreOnce VSA can reconnecte
d to licenses be
allocated to the StoreOnce VSA to return it to a licensed state.
- If the StoreOnce VSA is not connected to the APLS for 60 days it moves to an unlicensed and unusable state.
Use of Cloud Bank Storage with StoreOnce VSA
Operation
The
usable capacity of the StoreOnce VSA can be expanded up to 1,500 TB by using Cloud Bank Storage to connect up to 1,000 TB
of object storage. A bucket/container from the connected object storage is associated with a Catalyst store. This Catalyst store is us
ed
as a Catalyst Copy target in the same way as a regular Catalyst store. The translation of the backup data to object storage f
ormat is
efficiently handled by StoreOnce and transparent to the data protection application.
Host resources
Resources shoul
d be allocated to the StoreOnce VSA to host the Cloud Bank store(s) as laid out in the resource requirements section
above.
Detach
Many object storage vendors offer ‘cold’ storage tiers with reduced costs. The performance of ‘cold’ tiers is not
sufficient for Cloud
Bank Storage operations. For Cloud Bank stores with backup data that has to be retained but access requests are unlikely, the
Cloud
Bank store can be detached to enable it to be moved to a cold tier. On detach the Cloud Bank store is p
ut into a read only state and
is no longer visible to the StoreOnce system or the data protection application. The bucket/container associated with the det
ached
store can then be moved, independently of StoreOnce and the data protection application, using
the object storage console, to a ‘cold’
tier or other location for long term low cost retention.
If the detached store needs to be read it has to be moved back to a supported storage tier and reconnected to a StoreOnce sys
tem.
This can be the original Sto
reOnce VSA or any StoreOnce system running the same or newer version of the StoreOnce software. A
detached store is reconnected read only. To reconnect, details and credentials of the object storage provider and bucket/cont
ainer
are required. For encrypte
d Cloud Bank stores the encryption key needs to be provided if it is not stored on the host StoreOnce
system.
Licensing
Cloud Bank Storage and the Cloud Bank Storage Detach feature are licensed features. The licenses are capacity based with the
licensed capacity measured as the capacity written after deduplication and compression. The Cloud Bank licenses are added in
any
multiple of 1 TB up to 1,000 TB. The Cloud Bank Storage Detach licenses are added in any multiple of 1 TB with no upper limit.
See
the licensing and part numbers section below.
Supported object storage
Most leading cloud and on-
premises object storage services are supported for use with Cloud Bank Storage. For information on the
current supported object storage systems and services see the StoreOnce support matrix*.
NOTE:*This requires a HPE Passport account – the single sign on for HPE websites and services. Create an account
here.