public:module:microsoft365-v5:pro:preparation
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:module:microsoft365-v5:pro:preparation [2022/06/30 11:15] 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 237: | 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 447: | 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 455: | 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 463: | 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 475: | 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.1656558920.txt.gz · Last modified: 2022/06/30 11:15 by anam.gumba
Page Tools
