![]() ![]() All backup files are encrypted - the administrator supplies a passphrase and must remember this for any subsequent restoration.You can enable daily automatic backups, and you can also take a manual backup whenever it is appropriate, for example, before and after you make any configuration changes or perform a software upgrade. You can use Pexip Infinity's inbuilt backup and restore mechanism to backup and restore the configuration data on the Management Node. Using backup and restore via the Pexip Infinity Administrator interface VMware VDP - vSphere Data Protection) or similar, and restoration should be tested and verified (preferably after the inbuilt backup methods have been set up, to ensure that you have another way of recovering if your restoration fails).Ĭonsult your hypervisor documentation for more information about taking and restoring backups and snapshots. VM backups should use a proper hypervisor VM backup tool (e.g. Taking or removing snapshots can cause virtual machines to become unresponsive. You should only create and delete VMware snapshots at a time of minimal usage. ![]() Therefore, we recommend taking snapshots only when necessary (such as prior to an upgrade) and deleting the snapshot as soon as possible after the upgrade is confirmed to be successful. Snapshots are a tool to roll back to a given time. This backup can then be re-deployed at a later date if required.īe aware that snapshots are not backups. You can use your hypervisor's own backup tools, or any other third-party tool that supports VM backups, to create a full backup of the Management Node. Using your hypervisor's tools to take and restore backups However, if your Conferencing Nodes are geographically spread out and redeploying them would consume significant bandwidth or take a significant length of time, they can also be backed up with your hypervisor's backup tools. ![]() They receive all their configuration information from the Management Node and can simply be redeployed if necessary. Backing up Conferencing NodesĬonferencing Nodes do not need to be backed up. See Resilience strategies - redundancy, backing up and restoring data for more general guidance on resilience strategies. If you are using VMR Scheduling for Exchange, we recommend that you run the scheduling recovery script after restoring the Management Node to ensure that any meetings that were scheduled after the backup was taken are reinstated. You can also separately backup and restore just your Virtual Meeting Room and Virtual Auditorium configuration, see Bulk import/export of service configuration data. Cloud-based deployments ( Azure, AWS, GCP or Oracle) should use the Pexip Infinity backup and restore mechanism only VM snapshots on these deployments are not supported. ![]() The Pexip Infinity backup and restore mechanism is your fallback mechanism, as this allows you to preserve a copy of your data in an alternative location, in case you lose your VM environment. A VM snapshot should be your primary mechanism prior to an upgrade, as this allows you to easily restore your system back to its state at the time the snapshot was taken.
0 Comments
Leave a Reply. |