Rapid Recovery 6.9 and newer supports object locking (immutability) for Amazon AWS S3, this applies to one-time and schedule archives.
Visit the next article for more details on how to use this feature Setting Up S3 Object Locking (Immutable Storage) for Rapid Recovery Archives (4376845) (quest.com)
Immutable storage is not fully supported in Rapid Recovery for Google Cloud and Microsoft Azure, however, here is how Rapid Recovery one-time and schedule archive behave with Google Cloud and Microsoft Azure.
Google Cloud: the task fails at the end with the following error message
Exception chain:
- An invalid request URL was provided. The request URL must either be an absolute URL or BaseAddress must be set.
- One or more errors occurred.
Microsoft Azure: It works.
do not work with immutable storage due to the nature of how the archive to immutable storage works.
Scheduled archives will work the first archive in Microsoft Azure, but the subsequent archive won't work this is because when a scheduled archive runs the 2nd time and onwards it requires deleting a file (backup.end) from the last archive folder created and creating the file (backup.end) into a new folder that will be created.
If you try a scheduled archive you will see an error similar to the following:
ErrorThe remote server returned an error: (409) Conflict.
- The remote server returned an error: (409) Conflict.
- Failed to delete file 'SQL2019\AABackup\7bfd8661-349b-4185-a444-24ea117efc12\backup.end' from 'immutablearchive'.
- One or more errors occurred.
Currently, there are 2 feature requests for immutable storage
Feel free to vote for one or both if you support the ideas.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center