User Tools

Site Tools

You are here: Home » Start Searching Anything About CloudBacko Here! » Modules » microsoft365-v5 » Microsoft 365 Backup Module for CloudBacko Pro » 2 Preparation
public:module:microsoft365-v5:pro:preparation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
public:module:microsoft365-v5:pro:preparation [2022/06/30 10:37]
anam.gumba 		public:module:microsoft365-v5:pro:preparation [2022/07/06 15:05] (current)
anam.gumba
Line 1: Line 1:
-====== 2. Preparation ======+====== 2  Preparation ======
  
 ===== 2.1 Hardware Requirement ===== ===== 2.1 Hardware Requirement =====
Line 69: Line 69:
 As the value of 4 concurrent backup threads is found to be the optimal setting for Microsoft 365 backups, to ensure best backup performance,​ minimal resource usage, and lowest probability of throttling of backup requests by Microsoft 365. As the value of 4 concurrent backup threads is found to be the optimal setting for Microsoft 365 backups, to ensure best backup performance,​ minimal resource usage, and lowest probability of throttling of backup requests by Microsoft 365.
  
-For more detailed information on how to change the Java heap size, please refer to [[public:​edition:​cloudbacko_pro:​faq:​how_to_increase_java_heap_size|here]].+For more detailed ​information on how to increase the backup thread, please refer to [[public:​module:​microsoft365-v5:​pro:​appendix-e|Appendix E: How to Increase the Number of Concurrent Backup Threads]]. While for information on how to change the Java heap size, please refer to [[public:​edition:​cloudbacko_pro:​faq:​how_to_increase_java_heap_size|here]].
  
 ===== 2.10 Microsoft 365 License Requirements ===== ===== 2.10 Microsoft 365 License Requirements =====
Line 123: Line 123:
 To assign the Global Admin role to accounts, follow the steps below: To assign the Global Admin role to accounts, follow the steps below:
  
-  - Click the App launcher in the upper left side then click **Admin** to go to the Microsoft 365 admin center.\\ ​ {{public:​module:​microsoft365-v5:​permission-18.png}}\\ ​ {{public:​module:​microsoft365-v5:​permission-02.png}} ​    ​ +  - Click the App launcher in the upper left side then click **Admin** to go to the Microsoft 365 admin center.\\ ​ {{public:​module:​microsoft365-v5:​permission-18.png}}\\ ​ {{public:​module:​microsoft365-v5:​permission-02.png}}\\  \\        ​ 
-  - In the Microsoft 365 admin center, on the left panel click **Users**. Find the user you want to assign the Global Admin role and select **Manage roles**.\\ ​ {{public:​module:​microsoft365-v5:​permission-03.png?​600}}\\ ​ {{public:​module:​microsoft365-v5:​permission-04.png?​600}} ​    ​ +  - In the Microsoft 365 admin center, on the left panel click **Users**. Find the user you want to assign the Global Admin role and select **Manage roles**.\\ ​ {{public:​module:​microsoft365-v5:​permission-03.png?​600}}\\ ​ {{public:​module:​microsoft365-v5:​permission-04.png?​600}}\\  \\          
-  - In the Manage roles window, select **Admin center access** then check the box beside **Global admin**. Click **Save Changes** to save the role you assigned.\\ ​ {{public:​module:​microsoft365-v5:​permission-05.png}} ​  ​+  - In the Manage roles window, select **Admin center access** then check the box beside **Global admin**. Click **Save Changes** to save the role you assigned.\\ ​ {{public:​module:​microsoft365-v5:​permission-05.png}}\\  \\     
  
 ==== 2.11.2 Granting Term Store Administrator Role ==== ==== 2.11.2 Granting Term Store Administrator Role ====
Line 131: Line 131:
 To add Term Store Administrator role to the Microsoft 365 user account used to authenticate the Microsoft 365 backup set. To add Term Store Administrator role to the Microsoft 365 user account used to authenticate the Microsoft 365 backup set.
  
-  - In the SharePoint admin center, under Content services, click **Term store**. \\  {{public:​module:​microsoft365-v5:​permission-06.png}} +  - In the SharePoint admin center, under Content services, click **Term store**. \\  {{public:​module:​microsoft365-v5:​permission-06.png}}\\  \\  ​ 
-  - In the tree view pane on the left, select **Taxonomy**.\\ ​ {{public:​module:​microsoft365-v5:​permission-07.png}} +  - In the tree view pane on the left, select **Taxonomy**.\\ ​ {{public:​module:​microsoft365-v5:​permission-07.png}}\\  \\  ​ 
-  - In the Term store page, for Admins, select Edit. The Edit term store admins panel appears.\\ ​ {{public:​module:​microsoft365-v5:​permission-08.png?​600}} +  - In the Term store page, for Admins, select Edit. The Edit term store admins panel appears.\\ ​ {{public:​module:​microsoft365-v5:​permission-08.png?​600}}\\  \\  ​ 
-  - Enter the names or email addresses of the Microsoft 365 user who you want to add as term store admins. Select **Save**.+  - Enter the names or email addresses of the Microsoft 365 user who you want to add as term store admins. Select **Save**.\\  \\  ​
  
 ==== 2.11.3 Granting Permission Discovery Management Group ==== ==== 2.11.3 Granting Permission Discovery Management Group ====
Line 140: Line 140:
 This permission allows users added under the **Members** section of the **Discovery Management** group (refer to 2.11.4 for setup) to back up and/or restore user item(s) not only for their own account, but also the accounts of other users in the same **Members** section. This permission allows users added under the **Members** section of the **Discovery Management** group (refer to 2.11.4 for setup) to back up and/or restore user item(s) not only for their own account, but also the accounts of other users in the same **Members** section.
  
-  - Open [[https://​outlook.office365.com/​ecp]] +  - Open [[https://​outlook.office365.com/​ecp]]\\  \\  ​ 
-  - Log in to Microsoft 365 as an account administrator.\\ ​ {{public:​module:​microsoft365-v5:​permission-09.png}}\\ ​ \\  {{public:​module:​microsoft365-v5:​permission-10.png}}  +  - Log in to Microsoft 365 as an account administrator.\\ ​ {{public:​module:​microsoft365-v5:​permission-09.png}}\\ ​ \\  {{public:​module:​microsoft365-v5:​permission-10.png}}\\  \\    
-  - Select the **permissions** menu on the left, then double click on **Discovery Management** on the right.\\ ​ {{public:​module:​microsoft365-v5:​permission-11.png?​600}} ​+  - Select the **permissions** menu on the left, then double click on **Discovery Management** on the right.\\ ​ {{public:​module:​microsoft365-v5:​permission-11.png?​600}}\\  \\   
   - Click the **+** icon under the Roles section. These are the following roles:   - Click the **+** icon under the Roles section. These are the following roles:
       * ApplicationImpersonation       * ApplicationImpersonation
Line 148: Line 148:
       * Mailbox Import Export       * Mailbox Import Export
       * Mailbox Search       * Mailbox Search
-      * Public Folders\\ ​ {{public:​module:​microsoft365-v5:​permission-12.png}}  +      * Public Folders\\ ​ {{public:​module:​microsoft365-v5:​permission-12.png}}\\  \\    
-  - Click **Save** to confirm and exit the setting. ​+  - Click **Save** to confirm and exit the setting.\\  \\   
  
 ==== 2.11.4 Granting Permission to Accounts for Creating Backup Set ==== ==== 2.11.4 Granting Permission to Accounts for Creating Backup Set ====
  
-  - Open [[https://​outlook.office365.com/​ecp]] +  - Open [[https://​outlook.office365.com/​ecp]]\\  \\  ​ 
-  - Log in to Microsoft 365 as an account administrator.\\ ​ {{public:​module:​microsoft365-v5:​permission-09.png}}\\ ​ \\  {{public:​module:​microsoft365-v5:​permission-10.png}}  +  - Log in to Microsoft 365 as an account administrator.\\ ​ {{public:​module:​microsoft365-v5:​permission-09.png}}\\ ​ \\  {{public:​module:​microsoft365-v5:​permission-10.png}}\\  \\    
-  - Select the **permissions** menu on the left, then double click on **Discovery Management** on the right.\\ ​ {{public:​module:​microsoft365-v5:​permission-11.png?​600}}  +  - Select the **permissions** menu on the left, then double click on **Discovery Management** on the right.\\ ​ {{public:​module:​microsoft365-v5:​permission-11.png?​600}}\\  \\  ​ 
-  - You can now add users to this group. Click the **+** icon under the Members section.\\ ​ {{public:​module:​microsoft365-v5:​permission-16.png}} +  - You can now add users to this group. Click the **+** icon under the Members section.\\ ​ {{public:​module:​microsoft365-v5:​permission-16.png}}\\  \\  ​ 
-  - Look for the username(s) of the account that you would like to add permission for, then click **add** > **OK** to add the corresponding user(s) to the permission group.\\ ​ {{public:​module:​microsoft365-v5:​permission-17.png?​600}} +  - Look for the username(s) of the account that you would like to add permission for, then click **add** > **OK** to add the corresponding user(s) to the permission group.\\ ​ {{public:​module:​microsoft365-v5:​permission-17.png?​600}}\\  \\  ​ 
-  - Click **Save** to confirm and exit the setting.+  - Click **Save** to confirm and exit the setting.\\  \\  ​
  
 ==== 2.11.5 Granting Permission to restore all share link types to alternate location in Microsoft 365 ==== ==== 2.11.5 Granting Permission to restore all share link types to alternate location in Microsoft 365 ====
Line 167: Line 167:
 === 2.11.5.1 Allowing anonymous users to access application pages === === 2.11.5.1 Allowing anonymous users to access application pages ===
  
-  - Click the App launcher in the upper left side.\\ ​ {{public:​module:​microsoft365-v5:​permission-18.png}} +  - Click the App launcher in the upper left side.\\ ​ {{public:​module:​microsoft365-v5:​permission-18.png}}\\  \\  ​ 
-  - Click **SharePoint** to go to the SharePoint page.\\ ​ {{public:​module:​microsoft365-v5:​permission-19.png}}  +  - Click **SharePoint** to go to the SharePoint page.\\ ​ {{public:​module:​microsoft365-v5:​permission-19.png}}\\  \\    
-  - Click **Settings** > **Site Settings**.\\ ​ {{public:​module:​microsoft365-v5:​permission-20.png}}  +  - Click **Settings** > **Site Settings**.\\ ​ {{public:​module:​microsoft365-v5:​permission-20.png}}\\  \\    
-  - Under Site Collection Administration,​ click **Site collection features**.\\ ​ {{public:​module:​microsoft365-v5:​permission-21.png?​600}}  +  - Under Site Collection Administration,​ click **Site collection features**.\\ ​ {{public:​module:​microsoft365-v5:​permission-21.png?​600}}\\  \\    
-  - Scroll down and look for “**Limited-Access user permission lockdown mode**”, click the **Deactivate** button.\\ ​ {{public:​module:​microsoft365-v5:​permission-22.png?​600}} +  - Scroll down and look for “**Limited-Access user permission lockdown mode**”, click the **Deactivate** button.\\ ​ {{public:​module:​microsoft365-v5:​permission-22.png?​600}}\\  \\  ​ 
-  - Click **Deactivate this feature**.\\ ​ {{public:​module:​microsoft365-v5:​permission-23.png?​600}}\\ ​ {{public:​module:​microsoft365-v5:​permission-24.png>600}}\\  ​Once deactivated,​ the Deactivate button will no longer be available.+  - Click **Deactivate this feature**.\\ ​ {{public:​module:​microsoft365-v5:​permission-23.png?​600}}\\  Once deactivated,​ the Deactivate button will no longer be available.\\  {{public:​module:​microsoft365-v5:​permission-24.png?600}}\\  ​\\  ​
  
    
 === 2.11.5.2 Allowing sharing to external users === === 2.11.5.2 Allowing sharing to external users ===
  
-  - Go to your **Microsoft 365 Admin Center** > **All admin centers** > in the right pane select **SharePoint**.\\ ​ {{public:​module:​microsoft365-v5:​permission-25.png?​600}} +  - Go to your **Microsoft 365 Admin Center** > **All admin centers** > in the right pane select **SharePoint**.\\ ​ {{public:​module:​microsoft365-v5:​permission-25.png?​600}}\\  \\  ​ 
-  - Go to **Policies** > **Sharing**.\\ ​ {{public:​module:​microsoft365-v5:​permission-26.png?​600}}  +  - Go to **Policies** > **Sharing**.\\ ​ {{public:​module:​microsoft365-v5:​permission-26.png?​600}}\\  \\    
-  - Under __External Sharing__ the button must be in line with “Existing guests” and click **Save**.\\ ​ {{public:​module:​microsoft365-v5:​permission-29.png?​600}} ​+  - Under __External Sharing__ the button must be in line with “Existing guests” and click **Save**.\\ ​ {{public:​module:​microsoft365-v5:​permission-29.png?​600}}\\  \\   
 </​WRAP>​ </​WRAP>​
  
Line 205: Line 205:
 To disable the data synchronization check, follow the instructions below: To disable the data synchronization check, follow the instructions below:
  
-1. Make sure there are no active backup or restore job running. +  - Make sure there are no active backup or restore job running.\\ \\  ​ 
- +  ​- ​Close the CloudBacko Pro UI.\\  \\  ​ 
-2. Close the CloudBacko Pro UI. +  ​- ​Stop the CloudBacko Pro services.\\  \\   
- +  - Go to C:\Program Files\CloudBacko Pro\ folder.\\  \\  ​ 
-3. Stop the CloudBacko Pro services +  ​- ​Open cb.opt file using a text editor such as Notepad or Notepad++.\\  \\  ​ 
- +  ​- ​Add this line, **Office365.DSCInterval=-1**.\\  ​A value of -1 indicates data synchronization check is disabled.\\  \\  ​ 
-4. Go to C:\Program Files\CloudBacko Pro\ folder.  +  ​- ​Start the CloudBacko Pro services.\\  \\
- +
-5. Open cb.opt file using a text editor such as Notepad or Notepad++. +
- +
-6. Add this line, Office365.DSCInterval=-1 +
-A value of -1 indicates data synchronization check is disabled. +
- +
-7. Start the CloudBacko Pro services+
  
 To check if the DSC is enabled, follow the instructions below: To check if the DSC is enabled, follow the instructions below:
  
-1. Go to C:\Program Files\CloudBacko Pro\ folder. +  - Go to C:\Program Files\CloudBacko Pro\ folder.\\  \\  ​ 
- +  ​- ​Open cb.opt file using a text editor such as Notepad or Notepad++.\\  \\  ​ 
-2. Open cb.opt file using a text editor such as Notepad or Notepad++. +  ​- ​Look for this line, **Office365.DSCInterval=xx**.\\  **Note:** If xx is a positive value this indicates the DSC is enabled ​ and represents the interval number of days until the next run of data synchronization check.\\  ​-OR-\\  ​If the interval value is not -1.\\  \\  ​
- +
-3. Look for this line, //Office365.DSCInterval=xx//.  +
- +
-Note: +
-If xx is a positive value this indicates the DSC is enabled ​ and represents the interval number of days until the next run of data synchronization check. +
--OR- +
-If the interval value is not -1.+
  
 To adjust the interval number of days, follow the instructions below: To adjust the interval number of days, follow the instructions below:
  
-1. Make sure there are no active backup/​restore job running. +  - Make sure there are no active backup/​restore job running.\\  \\  ​ 
- +  ​- ​Close CloudBacko Pro UI.\\  \\  ​ 
-2. Close CloudBacko Pro UI. +  ​- ​Stop the CloudBacko Pro services.\\  \\   
- +  - Go to C:\Program Files\CloudBacko Pro\ folder.\\  \\  ​ 
-3. Stop the CloudBacko Pro services +  ​- ​Open cb.opt file using a text editor such as Notepad or Notepad++.\\  \\  ​ 
- +  ​- ​Change the interval number.\\  ​For example: Current interval: Office365.DSCInterval=60\\  ​Updated interval: Office365.DSCInterval=10\\  ​Explanation:​ On the current interval, the number of days is 60. While, the updated interval, the number of days is reduced to 10.\\  <color #​ed1c24>​**WARNING!** If the interval value is 0, Office365.DSCInterval=0,​ then the DSC will run for every backup job.</​color>​\\ ​ \\  ​ 
-4. Go to C:\Program Files\CloudBacko Pro\ folder. +  ​- ​Start the CloudBacko Pro services.\\  \\  ​
- +
-5. Open cb.opt file using a text editor such as Notepad or Notepad++. +
- +
-6. Change the interval number. +
- +
-For example: ​ +
-Current interval: Office365.DSCInterval=60 +
-Updated interval: Office365.DSCInterval=10 +
- +
-Explanation: ​ +
-On the current interval, the number of days is 60. While, the updated interval, the number of days is reduced to 10. +
- +
-WARNING! ​ +
-If the interval value is 0, Office365.DSCInterval=0,​ then the DSC will run for every backup job. +
- +
-7. Start the CloudBacko Pro services+
 </​WRAP>​ </​WRAP>​
  
Line 267: Line 237:
 Modern Authentication provides a more secure user authentication by using app token for authentication aside from using the Microsoft 365 login credentials. ​ In order to use Modern Authentication,​ the Microsoft 365 account is registered under Global region and the Microsoft 365 backup is configured to use Global region. ​   ​ Modern Authentication provides a more secure user authentication by using app token for authentication aside from using the Microsoft 365 login credentials. ​ In order to use Modern Authentication,​ the Microsoft 365 account is registered under Global region and the Microsoft 365 backup is configured to use Global region. ​   ​
  
-Existing backup sets using Basic Authentication can be migrated to Modern Authentication. ​ However, once the authentication process is completed, the authentication can never be reverted back to Basic Authentication. ​ For more information on how to migrate to Modern Authentication please refer to Appendix ​I:  Re-Authentication of Microsoft 365 Backup Set.  After the upgrade to CloudBacko Pro v5.3.2.0 or above, the backup and restore process of existing Microsoft 365 backup sets still using Basic Authentication will not be affected during this transition period since Modern Authentication ​ is not yet enforced by Microsoft.+Existing backup sets using Basic Authentication can be migrated to Modern Authentication. ​ However, once the authentication process is completed, the authentication can never be reverted back to Basic Authentication. ​ For more information on how to migrate to Modern Authentication please refer to [[public:​module:​microsoft365-v5:​pro:​appendix-g|Appendix ​G:  Re-Authentication of Microsoft 365 Backup Set]].  After the upgrade to CloudBacko Pro v5.3.2.0 or above, the backup and restore process of existing Microsoft 365 backup sets still using Basic Authentication will not be affected during this transition period since Modern Authentication ​ is not yet enforced by Microsoft.
  
 In order to migrate existing backup sets to Modern Authentication there are two (2) methods: In order to migrate existing backup sets to Modern Authentication there are two (2) methods:
Line 287: Line 257:
                                                                                                    
 ===== 2.14 Supported Services ===== ===== 2.14 Supported Services =====
-Below are the supported services of Microsoft 365 Backup module. It is also specified in the table some services that are currently not yet supported by the Microsoft 365 Backup module.+Below are the supported services of Microsoft 365 Backup module. It is also specified in the table some services that are currently not yet supported by the Microsoft 365 Backup module.\\  {{public:​module:​microsoft365-v5:​permission-31.png?​800}} \\  \\  ​
    
-{{public:​module:​microsoft365-v5:​permission-31.png?​800}} ​ +Below are the supported Outlook Mailbox types of Microsoft 365 Backup.\\  ​{{public:​module:​microsoft365-v5:​permission-32.png?800}}\\  \\   
-  +
-Below are the supported Outlook Mailbox types of Microsoft 365 Backup.+
  
-{{public:​module:​microsoft365-v5:​permission-32.png?​800}} ​ +Below are the items that you can back up or restore from a Microsoft mailbox.\\  ​{{public:​module:​microsoft365-v5:​permission-34.png?800}}\\  \\  ​
- +
-Below are the items that you can back up or restore from a Microsoft mailbox.+
    
-{{public:​module:​microsoft365-v5:​permission-34.png?​800}} ​ +Below are the items that you can back up or restore from OneDrive.\\  ​{{public:​module:​office365-v4:​permission-35.png?800}}\\  \\    ​
-  +
-Below are the items that you can back up or restore from OneDrive.+
  
-{{public:​module:​office365-v4:​permission-35.png?​800}}  +Below are the items that you can backup or restore from Teams Chat / Channel.\\  ​{{public:​module:​microsoft365-v5:​permission-33.png?​800}}\\  \\  ​
- +
-Below are the items that you can backup or restore from Teams Chat / Channel. +
- +
-{{public:​module:​microsoft365-v5:​permission-33.png?​800}} ​+
    
-Below are the Site Collections/​Personal Site items that you can back up or restore from a Microsoft 365 backup set. +Below are the Site Collections/​Personal Site items that you can back up or restore from a Microsoft 365 backup set.\\  ​{{public:​module:​microsoft365-v5:​permission-36.png?​800}}\\  \\   
- +
-{{public:​module:​microsoft365-v5:​permission-36.png?​800}} ​+
    
-Below are the SharePoint Site Collections template that you can back up or restore from a Microsoft 365 backup set. +Below are the SharePoint Site Collections template that you can back up or restore from a Microsoft 365 backup set.\\  ​{{public:​module:​office365-v4:​permission-37.png?​800}}\\  \\  ​
-  +
-{{public:​module:​office365-v4:​permission-37.png?​800}} ​ +
- +
-Below is the Site Column Type that you can back up or restore from a Microsoft 365 backup set. +
- +
-{{public:​module:​microsoft365-v5:​permission-38.png?​800}} ​+
  
-Below are the items from the Public Folder ​that you can backup and restore from a Microsoft 365 backup set.+Below is the Site Column Type that you can back up or restore from a Microsoft 365 backup set.\\  {{public:​module:​microsoft365-v5:​permission-38.png?​800}}\\ ​ \\   
  
-{{public:​module:​office365-v4:​permission-39.png?​800}} ​+Below are the items from the Public Folder that you can backup and restore from a Microsoft 365 backup set.\\  ​{{public:​module:​office365-v4:​permission-39.png?​800}}\\  \\   
  
 ===== 2.15 Maximum Supported File Size ===== ===== 2.15 Maximum Supported File Size =====
Line 341: Line 293:
   * Backup sets using Modern Authentication do not support backup of external content types (through the linkage from selected lists).   * Backup sets using Modern Authentication do not support backup of external content types (through the linkage from selected lists).
   * Backup sets using Modern Authentication do not support backup and restore of the following:   * Backup sets using Modern Authentication do not support backup and restore of the following:
-<WRAP indent>​ +      ​* Some list settings, currently known as Survey Options on survey list. 
-  ​* Some list settings, currently known as Survey Options on survey list. +      * Feature setting for SharePoint Site and Personal Site. 
-  * Feature setting for SharePoint Site and Personal Site. +
-</​WRAP>​+
     
 === SharePoint === === SharePoint ===
Line 359: Line 310:
   * The restore of SharePoint documents or folders with the following characters: / \ | * : “ < > in item name to a Windows local computer is not supported. As Windows does not support these characters for either a file or folder name.   * The restore of SharePoint documents or folders with the following characters: / \ | * : “ < > in item name to a Windows local computer is not supported. As Windows does not support these characters for either a file or folder name.
   * Restoring Newsfeed items in Modern Team Site will not publish the items to Homepage automatically,​ user will need to navigate to Site Content > Page Library> click on each individual news item and “Post” the news one by one manually.   * Restoring Newsfeed items in Modern Team Site will not publish the items to Homepage automatically,​ user will need to navigate to Site Content > Page Library> click on each individual news item and “Post” the news one by one manually.
-<WRAP indent>​ +      ​* Backup User (except for Global Admin) may not have permission to back up the site collection even if he/she can view it in the backup source tree. FOR EACH site collection, the user can backup it only if he/she is assigned as a site admin of that site collection. 
-  ​* Backup User (except for Global Admin) may not have permission to back up the site collection even if he/she can view it in the backup source tree. FOR EACH site collection, the user can backup it only if he/she is assigned as a site admin of that site collection. +        * If the user is assigned as site admin of the root level site collection only, he/she is not automatically added as site admin of other site collection under that root level site collection (i.e. If user is to backup specific site collection under the root, he/she has to be added as site admin of that specific site collection under the root also). 
-<WRAP indent>​ +        * For site collection that can be viewed by user in the source tree which he/she is not yet assigned as a site administrator:​ 
-  ​* If the user is assigned as site admin of the root level site collection only, he/she is not automatically added as site admin of other site collection under that root level site collection (i.e. If user is to backup specific site collection under the root, he/she has to be added as site admin of that specific site collection under the root also). +            * when user expand the node of that site collection, access denied error pop up will be given. 
-  * For site collection that can be viewed by user in the source tree which he/she is not yet assigned as a site administrator:​ +            * when user tick such site collection to backup, access denied error will be given in the backup log. 
-<WRAP indent>​ +
-  ​* when user expand the node of that site collection, access denied error pop up will be given. +
-  * when user tick such site collection to backup, access denied error will be given in the backup log. +
-</​WRAP>​ +
-</​WRAP>​ +
-</​WRAP>​+
     
 === OneDrive === === OneDrive ===
Line 380: Line 326:
        * In the backup source tree of the same backup set:        * In the backup source tree of the same backup set:
           * the original ticked item still use the old mail ID to reference and becomes red item.           * the original ticked item still use the old mail ID to reference and becomes red item.
-          * there is another item (with the new mail ID) created for that mail item   +          * there is another item (with the new mail ID) created for that mail item.   
-  ​* ​To avoid future backup error/​warning,​ the user will need to deselect the red item and tick the mail item again (new mail ID) in the backup source tree. This re-selection of backup source is not automatically done after you restore under overwrite to original location scenario.+<WRAP indent>​ 
 +<WRAP indent>​ 
 +To avoid future backup error/​warning,​ the user will need to deselect the red item and tick the mail item again (new mail ID) in the backup source tree. This re-selection of backup source is not automatically done after you restore under overwrite to original location scenario. 
 +</​WRAP>​ 
 +</​WRAP>​
  
  
Line 394: Line 344:
   * Restore of item(s) in public folder to an alternate location public folder is not supported. \\ Example: Restore of item(s) in public folder from User-A to alternate location User-B is not supported.   * Restore of item(s) in public folder to an alternate location public folder is not supported. \\ Example: Restore of item(s) in public folder from User-A to alternate location User-B is not supported.
   * When restoring to alternate location, data type “Person or Group” will not be restored. Following restore, it is suggested revisiting the relevant settings if necessary. This also affects “Assigned To” column values of some list templates (e.g. Tasks list), and “Target Audience” column values of some list templates (e.g. Content and Structure Reports).   * When restoring to alternate location, data type “Person or Group” will not be restored. Following restore, it is suggested revisiting the relevant settings if necessary. This also affects “Assigned To” column values of some list templates (e.g. Tasks list), and “Target Audience” column values of some list templates (e.g. Content and Structure Reports).
-  * If you are trying to restore item(s) from several users to an alternate location user, CloudBacko Pro will restore the item(s) to their respective destination folder(s) in alternate location user with the same name as the original folder(s). ​ +  * If you are trying to restore item(s) from several users to an alternate location user, CloudBacko Pro will restore the item(s) to their respective destination folder(s) in alternate location user with the same name as the original folder(s).\\  \\  ​{{public:​module:​office365-v4:​permission-41.png}}\\  \\  ​Example: Item from Outlook of User-A and User-B will be restored to the Outlook of the alternate location User-C.
- +
-{{public:​module:​office365-v4:​permission-41.png}} +
-  +
-Example: Item from Outlook of User-A and User-B will be restored to the Outlook of the alternate location User-C.+
  
 === Restore to Alternate Microsoft 365 account === === Restore to Alternate Microsoft 365 account ===
Line 501: Line 447:
 However, the actual number of Microsoft 365 users in a backup set may vary depending on the total number of Outlook, OneDrive, and SharePoint items, as well as the total size of these items. The actual number of Microsoft 365 users in a backup set could be considerably less or could be more than 2000. However, the actual number of Microsoft 365 users in a backup set may vary depending on the total number of Outlook, OneDrive, and SharePoint items, as well as the total size of these items. The actual number of Microsoft 365 users in a backup set could be considerably less or could be more than 2000.
  
-For details on the actual item count and size of Microsoft 365 user, it is recommended to check in the Microsoft 365 Admin Centre, please refer to Appendix ​H: How to view Item count and Storage used in Microsoft 365 Admin Center. ​+For details on the actual item count and size of Microsoft 365 user, it is recommended to check in the Microsoft 365 Admin Centre, please refer to [[public:​module:​microsoft365-v5:​pro:​appendix-f|Appendix ​F: How to view Item count and Storage used in Microsoft 365 Admin Center]]. 
  
 Also, by splitting up all the users into separate backup sets, the more backup sets, the faster the backup process can achieve. Also, by splitting up all the users into separate backup sets, the more backup sets, the faster the backup process can achieve.
Line 509: Line 455:
 Example: If there are 10 split backup sets, then there should be 10 unique user accounts for authentication. Example: If there are 10 split backup sets, then there should be 10 unique user accounts for authentication.
  
-For more detailed example, refer to Appendix B: Example for backup of large numbers of Microsoft 365 users.+For more detailed example, refer to [[public:​module:​microsoft365-v5:​pro:​appendix-b|Appendix B: Example for backup of large numbers of Microsoft 365 users]].
  
 ==== Concurrent Backup Thread ====  ==== Concurrent Backup Thread ==== 
Line 517: Line 463:
 For Microsoft 365 backup sets there are two approaches for backup source selection. Below are the sample screenshots of the selection __All Microsoft 365 users__ and __Selective Microsoft 365 user__. For Microsoft 365 backup sets there are two approaches for backup source selection. Below are the sample screenshots of the selection __All Microsoft 365 users__ and __Selective Microsoft 365 user__.
  
-**All Microsoft 365 users** ​ +**All Microsoft 365 users**\\  ​{{public:​module:​microsoft365-v5:​permission-43.png}} ​ 
-| {{public:​module:​microsoft365-v5:​permission-43.png}} ​| +
  
-**Selective Microsoft 365 user** ​ +**Selective Microsoft 365 user**\\  ​{{public:​module:​microsoft365-v5:​permission-44.png?800}} 
-  +
-| {{public:​module:​microsoft365-v5:​permission-44.png}} ​|+
  
      
Line 529: Line 472:
 ^  ^ All Microsoft 365 users ^ Selective Microsoft 365 user ^ ^  ^ All Microsoft 365 users ^ Selective Microsoft 365 user ^
 ^ Backup Set Maintenance | The Admin does not need to manage the backup set, i.e. to select or unselect use when a Microsoft 365 user account was added or removed, the changes are automatically updated in the backup source. | The Admin will have to select or unselect users manually when a Microsoft 365 user account was added or removed, as the changes are not automatically updated in the backup source this can be very time consuming. \\ If a Microsoft 365 user account is removed from the domain and the admin forgets to unselect the Microsoft 365 user account from the backup source, then this will cause a warning that the user does not exist. |  ^ Backup Set Maintenance | The Admin does not need to manage the backup set, i.e. to select or unselect use when a Microsoft 365 user account was added or removed, the changes are automatically updated in the backup source. | The Admin will have to select or unselect users manually when a Microsoft 365 user account was added or removed, as the changes are not automatically updated in the backup source this can be very time consuming. \\ If a Microsoft 365 user account is removed from the domain and the admin forgets to unselect the Microsoft 365 user account from the backup source, then this will cause a warning that the user does not exist. | 
-^ Microsoft 365 License | The backup user account must have additional Microsoft 365 license modules assigned to cover any increase in Microsoft 365 users. Otherwise, if additional users are added without sufficient modules, then this will cause backup quota exceeded warning and additional users will not be backed up. | This will allow the admin to easily control or manage the number of license modules used for the backup set. |+^ Microsoft 365 License | The backup user account must have additional Microsoft 365 license modules assigned to cover any increase in Microsoft 365 users. Otherwise, if additional users are added without sufficient modules, then this will cause backup quota exceeded warning and additional users will not be backed up.\\  For more details on the computation on the required license please see [[public:​module:​microsoft365-v5:​pro:​appendix-a|Appendix A: Example Scenarios for Microsoft 365 License Requirement and Usage]] ​| This will allow the admin to easily control or manage the number of license modules used for the backup set. |
 ^ Backup Time | All Microsoft 365 user accounts will be backed up. This means the initial full backup job will take longer, any subsequent incremental backup will take longer. | Only selective Microsoft 365 user accounts will be backed up. This will mean the initial full backup job will be faster, any subsequent incremental backup will be faster. | ^ Backup Time | All Microsoft 365 user accounts will be backed up. This means the initial full backup job will take longer, any subsequent incremental backup will take longer. | Only selective Microsoft 365 user accounts will be backed up. This will mean the initial full backup job will be faster, any subsequent incremental backup will be faster. |
 ^ Storage | As all Microsoft 365 user accounts are backed up, more storage will be required. | As only selective Microsoft 365 user accounts will be backed up, the backup set will require relatively less storage. |  ​ ^ Storage | As all Microsoft 365 user accounts are backed up, more storage will be required. | As only selective Microsoft 365 user accounts will be backed up, the backup set will require relatively less storage. |  ​
-^ Data Synchronization Check | As all Microsoft 365 user accounts are selected for backup, regular DSC may not be required. | As only selective files and/or folders are selected for backup, DSC is highly recommended to synchronize de-selected files and/or folders in the backup source with the backup destination(s). ​ \\  To know more about the DSC, please refer to Appendix ​E: Example Scenario for Data Synchronization Check (DSC) with sample backup reports. |+^ Data Synchronization Check | As all Microsoft 365 user accounts are selected for backup, regular DSC may not be required. | As only selective files and/or folders are selected for backup, DSC is highly recommended to synchronize de-selected files and/or folders in the backup source with the backup destination(s). ​ \\  To know more about the DSC, please refer to [[public:​module:​microsoft365-v5:​pro:​appendix-d|Appendix ​D: Example Scenario for Data Synchronization Check (DSC) with sample backup reports]]. |
public/module/microsoft365-v5/pro/preparation.1656556678.txt.gz · Last modified: 2022/06/30 10:37 by anam.gumba

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki