Snapshot Solution
Snapshot is a copy of the virtual machine's disk data, configurations, and disk files at a particular point in time. We suggest that you create a snapshot to safeguard against a disaster.
Scenarios
You can use snapshots in the following scenarios:
- YMP or SBC system failures
If the YMP or SBC server is down and cannot return to work in a short time, you can use a snapshot to restore data to the original server.
- Disaster Backup
If a natural disaster occurs in the region where the primary server was set up, you can restore data to the secondary server in a different region.
Snapshot planing
- Prepare a secondary instance for YMP and a secondary instance for SBC in a
different region.Note:
- The YMP server should meets the YMP system requirements; The SBC server should meets the SBC system requirements.
- Make sure the network configurations on the secondary
servers are the same as the primary servers.
If the network configurations are different, you need to contact Yeastar senior engineer to recover the servers, which requires professional technical knowledge and takes time. We don't recommend you configure different network settings on secondary servers.
- Schedule auto snapshot on the cloud platform or data center.Note: Make a schedule to create snapshots everyday and keep each snapshot stored for at least 7 days.
Recover your server by a snapshot
- YMP or SBC system failure
Restore the snapshot to the original server yourself. The server will return to work in a few minutes.
- Disaster recovery
- Restore the SBC snapshot to the secondary SBC server.
- Restore the YMP snapshot to the secondary YMP server.
- Unbind the elastic IP (public IP) with the primary SBC server, and bind the same IP with the secondary SBC server.
Result: Your customers' PBXs will return to work and run normally for 7 days while the YMP server is inactivated and the YMP web GUI is unaccessible.
Note: Contact Yeastar in 7 days to activate the secondary YMP server to ensure that your customers' business is keep running.