
15 Additional configuration tasks
Once you have completed configuration tasks for the StoreOnce System, be sure to save the
configuration. Depending upon your backup environment. it may also be necessary to configure
the media servers that are backing up to the StoreOnce System.
•
Saving the configuration and keystore (page 50)
•
Running a system confidence check (page 51)
•
Configuring media servers to use StoreOnce Catalyst (page 51)
•
Driver installation (VTL only) (page 52)
•
iSCSI Initiator (VTL only) (page 52)
Saving the configuration and keystore
Saving the configuration
It is strongly recommended to save the configuration whenever you make changes to it.
The configuration consists of two parts:
1.
A set of instructions in the form of a text file,
devconfig<timestamp>.txt
, for the user
to manually restore some of the network and device management configuration settings that
cannot be automatically restored.
2.
A zip file,
devconfig<timestamp>.zip
, containing StoreOnce device configuration
settings that automatically restore configuration settings that have been created for StoreOnce
VTL, NAS, Catalyst, Replication and housekeeping functions.
IMPORTANT:
If settings in the text file need to be restored, the manual restore should always
be carried out before the automatic restore. See the
StoreOnce System User Guide
for more
information about saving and restoring configurations.
To save the configuration:
1.
Open the
puTTy
(or other
ssh
) application and login to the StoreOnce CLI as an Admin
user. Save the configuration using the StoreOnce CLI command:
config save devices
2.
Using
sftp
protocol and an application, such as
filezilla
, copy the following files from
/config
to your local machine.
•
devconfig_<cluster ID and serial number><date and time>.zip
•
devconfig_<cluster ID and serial number><date and time>.txt
Saving the encryption keystore
Data at Rest and Data in flight encryption use encryption keys. Encryption keys are written to a
key store which may be managed locally on the StoreOnce System or externally using a Key
Manager utility. The key store should be backed up and saved securely offsite in case the original
key store is corrupted. However, be sure to keep only the latest version of the key store. See the
StoreOnce System User Guide
for more information and for detailed instructions a bout configuring
an External Key Manager..
The StoreOnce CLI command
config save keystore
that backs up the key store, also
encrypts it, ensuring that it can only be decrypted by the StoreOnce System, should you need
to restore it.
50
Additional configuration tasks