Administration & Maintenance - Backup & Restore
A Luna SA 5.x HSM can have up to 20 partitions, with space for objects per HSM defaulting to 2MB, upgradable to 15.5MB. Each partition on the HSM has a share of that space and can have its own cloning domain as represented by a domain (red) PED Key.
The normal backup-and-restore option for Luna SA 5 partitions uses the external, locally connected or remotely linked (network) Luna Remote Backup HSM as the backup repository. The Luna Remote Backup HSM supports the same partition structure, storage size, and capacity as the Luna SA 5's onboard HSM.
In order to provide a migration path from earlier Luna SA and removable-token format HSMs, it is possible to externally connect a Luna DOCK 2 card reader for Luna PCM, Luna CA4, or Luna HSM Backup Token, and to restore/migrate legacy token and partition contents to the current-generation Luna SA.
Keys (objects) from multiple Luna CA4 tokens, Luna PCM tokens (Key Export Signing, RA), or with differing cloning domains can be consolidated onto one Luna SA 5.x HSM, where objects from every token HSM are restored onto a partition corresponding to each token (segregated by legacy cloning domain).
Go to www.safenet-inc.com and search the Customer Care Center for Luna HSM Key Migration instructions.
Or, if you could set up an HA group to include the legacy HSM(s) and the target HSM(s), and use the HA synchronization function. This still requires that the target HSM(s) must have their modern cloning domains associated with the legacy domains of the legacy source HSM(s) in the HA group.
To backup the HSM contents to a token-style HSM - - - this is not a supported operation for Luna SA 5.x.
Restore from a legacy backup token is effectively a data migration - one-way only.
To backup the HSM (SO space, not User partition) contents to a Luna Remote Backup HSM, go to "Backup Your HSM Contents".
To restore HSM SO space contents from a Luna Backup HSM, go to restore.