API & Integrations - Profile Group Backup, Restore & Export Endpoints - FAQ

This article contains FAQs about Mimecast's Configuration Backup, Restore, and Export API endpoints, addressing common questions on profile group management, backup, export, restore operations, and key considerations for maintaining data integrity and hierarchy.

Q:	Can profile groups be deleted?
A:	Yes, except when a Profile Group has been used in a policy communication pair within a definition or Application Setting. In this case, an alert is displayed.
Q:	How can I back up my organization's Profile Groups?
A:	You can use the Configuration Backup and Restore Create API endpoint for Profile Group Backup. This allows you to preserve a record of the current state in a controlled location for up to 90 days. During this period, you may browse (list), export, or restore from this backup.
Q:	How can I export my organization's Profile Groups?
A:	You can use the Configuration Backup and Restore Export API endpoint for Profile Group export. This produces an uncontrolled copy of the Profile Groups contained within a backup, which could be used for change control or audit purposes. It also enables the admin to identify which profile groups to include in the scope of a restore operation.
Q:	How can I browse my organization's Profile Group backups?
A:	You can use the Configuration Backup and Restore List API endpoint to get a list of all available backups for your Profile Groups.
Q:	I need to restore a Profile Group and it's hierarchy which has been deleted. How can I do this?
A:	You can use the Configuration Backup and Restore Restore API endpoint for Profile Group Restore. There are few rules of recovery that will help users identify and set correct expectations around profile group restore operations. Profile Group Backup always includes the complete set of Profile Groups and their members with the backup and restore operation. Restore operations are performed from Top to Bottom. i.e., the group closest to the root is considered first, and any subgroups are recreated or restored to their original state in top-down order based on the mode selected by the user: In Overwrite mode, Profile Groups that are currently subgroups of groups listed in the restore operation but that are not part of the source will be deleted to restore the relevant part of the Profile Group hierarchy back the state described in the backup source. In Append mode, Profile Groups that are not part of the backup source but which are subgroups of in-scope groups will be left as-is. If their parents are moved, then they will move with them Profile groups will always be restored back to their original parent, if it still exists. If not, then they will be restored to the root. If a group needs to be moved to comply with the restore operation, then all its subgroups will also move with their parent. We will never orphan a group by moving its parent. Internal users cannot be restored as members if they no longer exist on the account. We will never create internal addresses as part of a restore operation. If we see the domain is external (or does not exist), then we will create domain and address as external and link to the group