Implement Long term backup
PITR of 35 days is not enough for our production databases.
We need long-term backup as it's done on Azure SQL Database.
The fact that there are no snapshots and no long term backup/PITR retention with managed instance leaves folks who are using TDE with no real option to pick an "older" point-in-time view of their database for audit/compliance/testing/debugging purposes. I have to imagine lots of folks are going to have a problem with that. And as Rob said below, turning off TDE to take a backup and then turning it back on is hardly an elegant (or compliant) solution.
My vote would be to just have a more sticky retention for the automatic backups, with the option to specify particular backups for "indefinite" storage. I might have a backup (lets say like the last day of the year) that I want to keep basically forever, but I don't need the daily's for every day in-between. Or give us access to the storage account where the backups live and the ability to manage that process on our own.
LTR is a top priority for us. once this is in place, we'll migrate our production to MI. in the meantime, we'll have to wait. Turning off TDE, then back up, then turn back on TDE is just not right. it defeats the purpose of TDE.
I don't suppose there is any further info as to when either COPY_ONLY with TDE or the LTR option will be available is there?
Doing a PITR then turning off TDE just to get backup retention over 35 days is not exactly elegant.
Michael Capobianco commented
Currently it's possible to take COPY-ONLY backups to long term blob storage. However, this is not supported for databases that are encrypted with TDE unless you use the BYOK (Bring Your Own Key) feature (Which is only in preview). Are there any plans to make COPY-ONLY backups possible without using BYOK?
Alexander (Sasha) Nosov commented
The work on the LTR support for MI is in progress and will have the same capabilities as with SQLDB. The restore performance from LTR backups should actually be better than point-in-time restore because it only involves a restore from full backup, no additional transaction redos as is the case with PITR.
We are using long term backup on Azure SQL Database and it's fine and cover our needs. If you can implement in same way long term backup on MI it will be fine.
Long term backup are usually to cover legal requirement. That means that time to restore is less important but surprising that PITR is faster than restore a backup without recover.
As backup are not accessible outside the MI the encryption is not the priority for us.
Clint H commented
This should be able to match how SQL Database LTR backups work.
Hitesh Patel commented
Should be same as Azure SQL Database to be able to implement same policies to managed instance.
Most compliance requirement is 7-10 Years. Longer data restore time in most cases are acceptable and can be based on archive tier in use.
Yes we need the feature to do long term backups on Managed Instances. Thnx