AvePoint Docs
Graph API
My support tickets
Graph API
My support tickets
English

    Home > Restore and Recover Your Data > AvePoint Cloud Backup > Restore Viva Engage Data

    Export to PDF

    Restore Viva Engage Data

    With AvePoint Cloud Backup, you can restore Viva Engage backup data to its original location, and restore Viva Engage communities and site collections to another location.

    Complete the steps below to restore Viva Engage data:

    1. Navigate to the Restore > AvePoint Cloud Backup page, and then click the Viva Engage tile.

    2. Select the data that you want to restore. You can choose one of the following methods to find the data to restore.

      • Search mode – Select a restore object scope and search for the data to restore. Follow steps 3 to 4.

      • Calendar mode – Select a recovery point (backup job) and select data from that backup to restore. Proceed to step 5.

    3. Define a Viva Engage community as the search scope. You can enter the Viva Engage community address or display name to search, and then select the Viva Engage community from the Name list. The default search condition is to search the backup data for the selected community within the last backup cycle.

    4. You can choose to use the properties on the same page to search for the contents within this community for granular data roll-back, or you can directly proceed to the next step to search and select the data to restore.

      For the details of using the properties on the first page or the Search feature on the Select and restore the data step, refer to the steps below:

      1. In the Name field, you can enter or select another Viva Engage community to change the search scope.

      2. In the Backup Time Range field, the time range of the last backup cycle is displayed by default. Click the Calendar button to customize the backup time range. The start date must be earlier than the end date. You can click Reset if you want to reset the settings. Click OK to save your customization.

      3. Select Viva Engage community, Site collection, Site, List/Library, App, Folder in SharePoint, Document, Plan, or Task from the Level list for the items you want to search. If you want to search for all objects at the level, you select from the selected Viva Engage community. You can leave the search conditions empty.

      4. Click Search to search the items according to the conditions you configured. The search conditions and the search results are displayed. The search results table will display a maximum of 2000 items. You can edit the search conditions and click Search to adjust the search results.

      5. Find and select the item you want to restore from the search results. In the Recovery point column, click the Calendar button to select a backup job that backed up this item at the status that you want to restore, and click Apply. Click the Restore button above the search result table to restore all selected items.

      6. Proceed to step 6 to continue with the Restore settings.

    5. Find a backup job that backed up the items at the time of the status you want to recover, and then search and select the items from the backup data of that backup job.

      1. In the calendar, all backup jobs of Viva Engage are displayed. You can select whether to display the finished with an exception or failed jobs in the calendar by selecting the Include jobs with only partial backup data option. Note that the data of these jobs may be incomplete. Hover over a backup job to show the backup job details.

      2. Select a backup job. All backup data are displayed in the table. You can select the Show data from this backup only (historical data in this scope from previous backups not included) option to only show the data backed up in the selected backup job.

      3. You can enter keywords to search the items, or you can click the backup data to browse the items you want to restore.

        Click the Restore button above the table to restore all selected items.

        Note that the restore settings will only show the options that support all the selected objects.

      4. Continue to step 6 to configure the Restore settings.

    6. If necessary, you can enter a description for this restore job in the Description text box.

    7. Choose where to restore the backup data to.

      • Restore the data to its original location – Restore the backup data to where the data is backed up.

      • Restore the data to another location – Restore the backup data to another destination. If you select a Viva Engage community or site collection, this option is available. Configure the following settings:

        • Select a restore destination – Select a container as the restore destination. You can enter keywords to search for the restore destination. The items that can be selected as the restore destination are listed under the Search box.

    Action – Select how the backup data will be restored to the destination. Select Attach to restore the contents as children beneath the selected node, or select Merge to add the contents to the destination node. For example, you want to restore a folder to another folder. If you select Attach, the restored folder will become the subfolder of the destination folder; if you select Merge, the subfolders and contents of the restored folder rather than itself will directly become the subfolders and contents of the destination folder.

    - **Restore the data to your storage** – If you have selected the Viva Engage conversations or files, and you have the BYOS subscription, this option is available. You can restore the Viva Engage conversations and files to your storage.

    8. Select how to handle conflicts in the restore job. The available conflict resolution options will vary for the items you select to restore.

    - Container level conflict resolution – Select how to handle conflicts at the container level. - **Skip** – The settings of the conflicting destination container will be retained in the destination. - **Merge** – The source container settings and the content will be merged to the conflicting destination container. With **Merge** as the container level conflict resolution, the **Privacy**, **Name**, and **Description** will be updated to the destination Viva Engage community, and the owner and members of the source Viva Engage community will be added to the destination. - **Replace** – The settings of the conflicting destination container will be deleted and replaced by the source container settings, as well as the content within the container. > ***Note**: The **Replace** option is unavailable when you select the whole Team to restore. - Content level conflict resolution – Select how to handle conflicts at the content level. - **Skip** – The conflicting destination content will be retained in the destination, and the backup data of the conflicting content will not be restored. - **Overwrite** – The conflicting destination content will be removed from the destination, and the backup data of the conflicting content will be restored. - **Overwrite by Last Modified Time** – If the last modified time of the conflicting destination content is earlier than that of the source content, the conflicting destination content will be removed from the destination, and the backup data of the conflicting content will be restored. - **Append an “_1” to the Item/Document** – If the last modified time of the conflicting destination content is the same, the restore will be skipped; if the last modified time is different, the conflicting destination content will be kept, and the backup data of the conflicting content will be added to the destination with a sequential number suffix added to the filename. > ***Note**: If you want to restore a single file version without affecting other versions, set the content level conflict resolution to **Append an “_1” to the Item/Document**. If the content level conflict resolution is set to **Overwrite**, the restore job will remove all the versions of this file from the destination and keep this file version as the latest and only version of the file. - Apps conflict resolution – Select how to handle the apps conflict. - **Skip** – The conflicting destination app and AppData will be retained in the destination, and the backup data of the conflicting content will not be restored. - **Overwrite** – The conflicting destination app and AppData will be removed from the destination, and the backup data of the conflicting content will be restored.

    9. Choose how you would like to restore the version history if file versions are backed up by AvePoint Cloud Backup. You can select to Restore the latest version only, or you can select the Restore the current and previous versions option and enter the maximum number of versions you want to restore in the box. AvePoint Cloud Backup service can restore up to 20 versions of one document. For the best performance and simplest experience, AvePoint recommends restoring only the latest version.

    1. Note the following:

      • By default, history versions of items and files are not backed up due to the regular recovery points created by backup jobs, as well as Microsoft 365 API overhead and limitations related to versions. In our experience, most user and legal requests are only for the most recent active version. In addition, we will capture multiple roll-back points during our daily backups to ensure you have a change history for this document outside native versioning. If you need to back up the versions for some reason and are willing to accept the performance impact, please contact AvePoint support to have it enabled. The backup job will include the most recent 10 versions by default.

      • If you want to restore earlier versions of a document, you can run an export job to export all versions of that document from the backup data.

      • This restore setting is not available when selecting documents.

    2. Select how you would like to restore the Managed Metadata Service.

      • If the containers or content you select to restore is under the site collection level, the Restore terms in site store only option and the Restore terms in both global term store and site term store option will only restore the terms and their parent terms associated directly with the data from the site store or both. Note that if the data is not restored due to the conflict resolutions you choose, the restored terms cannot be connected to the data either.

      • If you select at least the site collection level object to perform the restore, the Restore terms in site store only option will restore all the deleted terms in the site store and the Restore terms in both global term store and site term store option will restore all the deleted terms in both the global term store and site term store.

      • If you select to Use existing terms only, no terms will be restored.

      • If you want to perform a term store-only restore, refer to the FAQ: How do I perform term store-only restore

    3. Turn on/off the switch to define whether to restore the hub site connection. This option is only available when you select the Viva Engage community or community site to restore.

      *Note: Cloud Backup cannot restore the hub site connection for the selected site, if it is a cross-tenant restore or the destination hub site requires approval for the associated sites to join.

    4. Turn on/off the switch to define whether to allow restore jobs to rehydrate the data sets automatically when the backup data is stored in the Azure archive storage tier. This field is only functional for the BYOS subscription type. For AvePoint default storage, the restore job will automatically rehydrate data.

    5. Turn on/off the switch to define whether to enable the Custom Scripts setting during the restore. This feature allows you to restore data related to scripts to the destination Microsoft environment.

    6. Click Next to view the restore summary.

    7. Click Restore to restore the selected items. After the job has started, you can navigate to the Job monitor to view more job details. For details, refer to Job Monitor.