June 28, 2021 at 9:00 pm
Hello,
Hopefully someone who manages and administers hundreds of SQL Server VM's in Azure can share their experience. We have a few dozen SQL Server VM's in Azure and a small handful of managed instances. One of the issues we run into is the lack of visibility into backup failures, as well as being able to clean up the backup history. The "black box" nature of this backup solution leaves us scratching our heads as to why we see failures, how to get alerted for failures and how to avoid failures(Some failures, we have found, may be attributed to the "parallelism" that the backup tool uses in simultaneously backing up n number of databases(referred to in Azure parlance as "concurrency"). While this may be helpful for sharepoint databases, they are not relevant for most Apps.
Restores using Azure portal is another problem. The portal always presents time in the users time zone(User using Azure portal), and show restore points in the same time zone as well. if the server on which I am doing the restore is in another time/availability zone, this always ends up with a lot of confusing math involving UTC. From traditional on prem, it's always intuitive to have backup times and restore points always displayed in the target server's local time. This is by far the most frustrating part. Looking to see what the rest of the word uses, especially teams managing a large # of SQL Servers.
June 29, 2021 at 9:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply