Tutorial: How to Back Up Access Server Configuration⁠

• An installed Access Server.

• Console access and the ability to get root access.

Use the commands below to create configuration file backups while Access Server is live. You don’t need to stop the Access Server for this; it can continue running.

1. Sign in to the Access Server console and get root privileges.

2. Run these commands to create Access Server configuration backups:

   which apt > /dev/null 2>&1 && apt -y install sqlite3
   which yum > /dev/null 2>&1 && yum -y install sqlite
   cd /usr/local/openvpn_as/etc/db
   [ -e config.db ]&&sqlite3 config.db .dump>../../config.db.bak
   [ -e certs.db ]&&sqlite3 certs.db .dump>../../certs.db.bak
   [ -e userprop.db ]&&sqlite3 userprop.db .dump>../../userprop.db.bak
   [ -e log.db ]&&sqlite3 log.db .dump>../../log.db.bak
   [ -e config_local.db ]&&sqlite3 config_local.db .dump>../../config_local.db.bak
   [ -e cluster.db ]&&sqlite3 cluster.db .dump>../../cluster.db.bak
   [ -e notification.db ]&&sqlite3 notification.db .dump>../../notification.db.bak
   cp ../as.conf ../../as.conf.bak

   • After running these commands, the backup files ending in .bak can be found in the /usr/local/openvpn_as/ directory. The files contain everything unique about your Access Server installation.

You can restore the resulting backup files to another Access Server, including a higher version of Access Server, as we try to maintain backward compatibility.

Refer to Tutorial: How to Recover a Server with SQLite3 Dump Backup Files.

If the configuration becomes completely lost at any point, all currently installed OpenVPN clients will be unable to connect to this server. Unique information stored in the certificates database cannot be recreated. Each installation of Access Server has unique certificates, and if you lose this information without a backup, you must completely reinstall Access Server and the VPN clients.