Backup and Restore
The following document will help an organization to take backup data at unplanned incidents and minimizing the effects of a disaster by restoring, so an organization will continue to operate or quickly resume key operations. Make sure the organization has use the same IP address as previous WME Instances for new WME Instances.
Data Backup
- WaveMaker Platform Stores its state into the disk. WaveMaker Platform administrators can take backups of those disk/directories and can restore them to any previous state.
- WaveMaker uses separate dedicated directory
/wm-data
in WaveMaker Platform Instance for storing data and/data
in StudioWorkspace Instance / AppDeployment Instance. - Create an AMI or use the latest AMI of WME Instance or VM for creating AMI for different cloud providers follow the below steps.
- We move all the data to Platform Instance(/wm-data dir or volume) so that backup will be easier. No need to take backups of any (volume/dir) in any of StudioWorkspace Instance / AppDeployment Instance.
AWS
- To create AMI of Instance in AWS cloud provider please refer AMI creation in aws.
- Stop WME EC2 instance and detach eth1 network interface follow the steps given here, make a note of interface ID or ENI ID
Azure
- For creating an Image of Instance in AZURE cloud provider please refer Image creation in azure.
- Stop WME VM and detach network interface follow the steps given here, make a note of interface ID.
GCP
- For creating an Image of Instance in GCP cloud provider please refer Image creation in GCP.
- Stop WME VM aESXietach IP address follow the steps given here, make a note of interface ID.
VMWARE ESXi
- For creating a snapshot of VM in VMware please refer snapshot creation in vmware.
Hyper-V
- for creating a snapshot of VM in Hyper-V please refer snapshot creation in Hyper-V
WME Instances Creation
Platform Instance
- Launch the instance or VM with the same IP address with the latest AMI Image. To create WME Platform Instance in the different cloud and on-premise environments please follow the below steps.
AWS
- To launch WME Platform instance in AWS cloud environment please refer WME Platform instance Infrastructure in AWS.
AZURE
- To launch WME Platform virtual machines in AZURE cloud environmet please refer WME Platform instance Infrastructure in AZURE.
GCP
- To launch WME Platform virtual machines in GCP cloud environment please refer WME Platform instance Infrastructure in GCP.
VMWARE ESXI
- To create WME Platform virtual machines in VMware Esxi please refer WME Platform instance Infrastructure in VMware Esxi.
Hyper-V
- To create WME Platform virtual machines in Hyper-V please refer WME Platform instance Infrastructure in Hyper-V.
Starting WME setup
Following are the steps to start the WME setup process from the configwizard
StudioWorkspace Instance / AppDeployment Instance
- Launch the instance or VM with the same IP address with the latest AMI Image.To create WME StudioWorkspace Instance / AppDeployment Instance in the different cloud and on-premise environments please follow the below steps
AWS
- To launch WME StudioWorkspace Instance / AppDeployment Instance in AWS cloud environment please refer WME StudioWorkspace Instance / AppDeployment Instance Infrastructure in AWS.
AZURE
- To launch WME StudioWorkspace Instance / AppDeployment Instance in AZURE cloud environmet please refer WME StudioWorkspace Instance / AppDeployment Instance Infrastructure in AZURE.
GCP
- To launch WME StudioWorkspace Instance / AppDeployment Instance in GCP cloud environment please refer WME StudioWorkspace Instance / AppDeployment Instance Infrastructure in GCP.
VMWARE ESXI
- To create WME StudioWorkspace Instance / AppDeployment Instance in VMware Esxi please refer WME StudioWorkspace Instance / AppDeployment Instance Infrastructure in VMware Esxi.
Hyper-V
- To create WME StudioWorkspace Instance / AppDeployment Instance in Hyper-V please refer WME StudioWorkspace Instance / AppDeployment Instance Infrastructure in Hyper-V.