Immutable storage is not officially supported in Rapid Recovery however here is how Rapid Recovery features work with immutable objects in Amazon AWS, Google Cloud, and Microsoft Azure.
One-time archives
Amazon AWS: does not work
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: Worked during our testing
Scheduled archives 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 due to the fact that when a scheduled archive runs the 2nd time and onwards it requires deleting a file from the last archive folder created and creating the file 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.
One time export does not work
Virtual standby does not work
Azure repository does not work
Currently, there are 2 feature requests for immutable storage
Feel free to vote for one or both if you support the ideas.
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center