Be aware that if the critical config is restored it is a full clone, including such things as appliance name, SMTP settings etc – these will need to be changed if you are doing a clone rather than disaster recovery and want both Foundation instances on the network!
The only way to upgrade is by the officially supported upgrade tools. The upgrade tool will take a snapshot first if required, but this is to support the client in reverting if anything fails. A good use of snapshot during upgrade would be to clone the production appliance to a UAT VM and do a trial upgrade on the VM.
Snapshot creation may take several minutes. Please do not refresh or navigate away from the snapshot & restore page manually.
Upload and Download are a little confusing. You are “downloading” the snapshot from this appliance to another appliance or uploading a snapshot from a remote host to this appliance. No upload or download is done to the desktop that the UI is being accessed from.
This will place the snapshot in the remote appliance snapshot archive. Note: the migrate user is a unix user not a tideway application user. For security reasons the migrate user has no password set on default VA’s. migrate user passwd on the training demo VA’s is: demosnapshot If not using the training demo VA set the migrate user’s passwd as root on both tideway appliances.
The scp command is listed here so that it can be run manually to help investigation. The snapshot system tries it’s best to suggest what might be wrong but cannot cover every failure condition.
Notice the options ticked from the previous slide show up here under the “options” section
Snapshot disk threshold: The amount of disk space to reserve for the appliance snapshot. When the available disk space falls below this value, this is flagged on the Appliance Snapshot page.
![What is Appliance Snapshot? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)