I'm really struggling with a school project that involves using Azure's Recovery Services to create backups and restore VMs. My goal is to set up a system that allows me to monitor these backups in real-time or at short intervals. I want to track information like how long each backup takes, the size of the backups, and the status of each process (whether it's still running or completed). Ultimately, I intend to display this information on a website, showing a list of all ongoing backups and their statuses. I've tried to figure things out with ChatGPT but have ended up wasting a lot of time without making progress, and I'm feeling really frustrated as my deadline approaches. If anyone can lend a hand, I'd greatly appreciate it!
3 Answers
You might find that the Azure Backup Center already does a lot of what you need natively. I'd recommend breaking your project down into smaller tasks instead of trying to tackle everything at once. Start with the Backup Center, get that set up, and then move onto the next part!
Make sure you’re actually using the Recovery Services Vault (RSV) instead of the Recovery File Service. Also, Azure Backup job logs can take a few minutes to land in Log Analytics, so be aware there's a bit of a delay. I’d suggest using ChatGPT to double-check what Azure can do natively as well.
You're right! I accidentally misspelled it. I think I have a plan now: 1. Set up the Recovery Services Vault, 2. Enable logs in Diagnostic settings, 3. Monitor with Azure Monitor and KQL queries, and 4. Use Workbooks or the Log Analytics API for visualization. Does that sound good?
You can totally solve this with ChatGPT! Have you thought about breaking down your project into smaller tasks? For example, create VMs, set up the backup service, and then focus on monitoring that service. Just take it step by step, and you'll feel less overwhelmed!
I appreciate the encouragement! I know it's not rocket science, but I really need to keep my cool and tackle each part one at a time.
Thanks for the tip! I'll focus on configuring the Backup Center first—didn't even realize it existed!