How To Migrate From Legacy Mode To Shield (Kubernetes)¶
To migrate existing legacy systems to Shield running on Kubernetes, please follow these steps:
Note
For any help in this process, please contact Ericom Shield Professional Services.
- Backup the legacy system. Modify something in the admin console (this will create a new backup file) or use the latest daily backup file from the /usr/local/ericomshield/backup/daily 
- Shield supports SFTP as a remote storage for backups and uses it for restoring purposes. Create a dedicated account for this purpose. The required details are the server IP and username. 
- Place the backup file (from the legacy system) under the SFTP account 
- On the SFTP server, create a SSH key. For more details about SSH keys go here. 
- Create a new Shield system. Form a new Shield Kubernetes cluster as described in here. Additional steps are required prior to deploying Shield, so stop before deploying it. 
- On the Master machine, download the custom-management file to the current folder: - curl -s -o custom-management.yaml https://raw.githubusercontent.com/EricomSoftwareLtd/Shield/Rel-19.07.1/Kube/scripts/custom-management.yaml 
- Edit the file to configure the SFTP account (path, IP & username) and copy the SSH private key. (Missing settings are marked with - <>):- remotePath: "<BACKUP_PATH>" config: | rclone.conf: | [SFTPStorage] type = sftp host = <SFTP_SERVER_IP> user = <SFTP_USERNAME> key: key_file.pem: | ----BEGIN RSA PRIVATE KEY----- <PRIVATE_KEY> ----END RSA PRIVATE KEY----- 
- Continue with the deployment instructions. The deployment will refer to the updated custom-management file. Go here. 
- Use Shield in the new, Kubernetes deployment.