Black Box ET1000A VM Server specifics, Restoring to factory defaults, Cluster notes, DR notes

If you changed the database userid or password, you will have to supply those options as well.

[root@policyserver log]# /opt/scripts/db-import.sh --help db-import.sh

--help

--dbUser=dbUser

--dbPass=dbPassword --dbType=dbType --importFile=importFile --disasterServer=[true/false]

Cluster notes

Restoring a cluster node should not include restoring the database if another cluster node with a database is still active. Instead, the database on the restored node should be synchronized via the ETM web application. On the Platform->Utilities page, on the DB Nodes tab, find the inactive database, right click on it and choose Activate.

DR notes

If restoring a DR datbase (which should really never be necessary, since the backup can be pushed from the main ETM site via the UI), you must supply the --disasterServer=true command line option.

Restoring to factory defaults

If for some reason a server needs to be set back to the state in which it was delivered from Black Box, the /opt/scripts/factory-restore.sh script can be run. The user will be prompted twice before proceeding. This script will stop the ETM server, delete the database and reset all configuration files to their original state. The installer can be re-run after performing this operation.

VM Server specifics

VMware specific information is found on the VMware website.

VMWare backup guide

http://www.vmware.com/pdf/vi3_301_201_vm_backup.pdf

NOTE

Note that VMWare does not consider VM snapshots backups. For more information about snapshots, read the following knowledge base articles.

Understanding VM snapshots

http://kb.vmware.com/selfservice/microsites/ search.do?language=en_US&cmd=displayKC&externalId=1015180

Best Practices for VM snapshots

http://kb.vmware.com/selfservice/microsites/ search.do?language=en_US&cmd=displayKC&externalId=1025279

30 EncrypTight Manager Installation Guide