| KB ID: | 4176 |
| Product: | Veeam Backup for Microsoft Office 365 5.0, Veeam Backup for Microsoft Office 365 4.0, Veeam Backup for Microsoft Office 365 3.0 |
Challenge
When a repository extended to object storage that was initially created using PowerShell or REST API is removed from Veeam Backup for Microsoft Office 365 and then added back, the retention type changes to item-level. This change in retention type after such a repository has been re-added may cause certain items to not be in retention.
This issue applies to versions of Veeam Backup for Microsoft Office 365 between 3.0 GA (3.0.0.422 ) and 5b cumulative patch KB4135 (5.0.1.225). The currently installed build number can be found in the main menu under Help and Support > About.
Cause
This issue only affects repositories that meet the following criteria:
- Initially created using Veeam Backup for Microsoft Office 365 3.0.0.422 through 5.0.1.225.
- Initially created with REST API or PowerShell.
- Configured with the snapshot-based retention.
- Extended to object storage
Solution
Install the latest version of Veeam Backup for Microsoft Office 365 to avoid the issue on existing and new repositories. This issue was initially corrected in build 5.0.1.252.
If any repositories are experiencing this issue, the following steps will allow the repository to be re-added with snapshot-based retention. These steps are to be performed after updating Veeam Backup for Microsoft Office 365 to version 5.0.1.252 or higher.
- Open the Veeam Backup for Microsoft Office 365 console and stop any active backup jobs.
- Open the Services.msc console on the Veeam Backup for Microsoft Office 365 server.
- In the Services.msc console, stop the following Veeam services:
- Veeam.Archiver.Service
- Veeam.Archiver.Proxy
- Veeam.Archiver.RESTful.Service
- Copy C:\ProgramData\Veeam\Backup365\Proxy.xml to another location to create a backup of it.
- Run Notepad as Administrator and use File > Open to open C:\ProgramData\Veeam\Backup365\Proxy.xml.
- Add the following line in the <Archiver> section. If this line already exists, ensure that its value equals True.
<RepositoryConfig AllowChangeRetentionType="True" />
Example:
<Veeam>
<Archiver>
<RepositoryConfig AllowChangeRetentionType="True" />
</Archiver>
</Veeam>Do not apply this if a different issue is occurring.