Subject: WMHKALL backup migration – impact check
Hi Team,
I assume we do not have any database infrastructure hosted in WMHKALL and that all database servers are under IBHKALL.
I also expect no impact to Commvault database backups, assuming this activity is limited to Qtree migration. However, it would be good to perform a quick impact assessment and confirm whether any database backup or restore services could be affected.
Regards,
Nikhil
Thank you for your patience while we checked this internally.
We have now received confirmation that the Key Vault migration has been put on hold for the time being. Once the remaining resources have been removed from the subscription, the subscription will be assigned to the database team for ownership.
Therefore, no immediate migration action is required from your side at this stage. We will share a further update once the next steps and timeline are confirmed.
Emerging DB content, including diagrams and internal engineering session recordings, has been migrated from the existing SharePoint location to the secure ITD SharePoint.
Confluence documents have been reviewed, classified and copied to ITD. The original content will be removed from Confluence after final validation.
Azure Managed Redis: Validating the RBAC onboarding and migration approach through a dedicated test deployment before wider adoption.
Azure Managed Redis: Enabled and tested Premium SSD v2 with CMK using the latest Microsoft updates to improve storage performance.
Emerging DB pipelines: Validated the removal of legacy AzureRmAlias and AzureRM module dependencies with no portfolio impact; the changes are expected to improve pipeline execution time and reduce waiting time and associated costs.
MongoDB vCore: Enhancing automated role assignment through the Red Zone Function App.
Oracle Alert Incident Closure Analysis – W25 to W28
Hi Ranjit,
Please find below the Oracle alert incident closure analysis for W25 to W28.
The data has been grouped based on the week in which the incident was either resolved or cancelled, rather than the week in which the ticket was originally opened.
| Week | Total Incidents | Human Intervention | Automation Resolved | Human Intervention % | Automation Resolution % |
|---|---|---|---|---|---|
| W25 | 181 | 112 | 69 | 61.88% | 38.12% |
| W26 | 296 | 203 | 93 | 68.58% | 31.42% |
| W27 | 235 | 144 | 91 | 61.28% | 38.72% |
| W28 | 359 | 209 | 150 | 58.22% | 41.78% |
| Total | 1,071 | 668 | 403 | 62.37% | 37.63% |
Human intervention includes incidents cancelled or marked as resolved by a human, including cases assigned to automation but ultimately handled manually.
To create Power BI versus Validated Result, first prepare a summary table for each week.
| Week | Power BI – Human | Validated – Human | Power BI – Automation | Validated – Automation |
|---|---|---|---|---|
| W25 | 12 | 15 | 38 | 35 |
| W26 | 10 | 8 | 40 | 42 |
| W27 | 14 | 16 | 36 | 34 |
| W28 | 9 | 11 | 41 | 39 |
For a clean management view, create two separate charts.
Use:
For every week, two bars will appear side by side:
This makes differences immediately visible.
Use:
Power BI vs Validated Automation Closures – Weekly
Repeat the same process for human closures.
This shows how much the Power BI report differs from your validation.
| Week | Power BI Automation | Validated Automation | Variance |
|---|---|---|---|
| W25 | 38 | 35 | 3 |
| W26 | 40 | 42 | -2 |
Excel formula:
=B2-C2
Interpretation:
You can also calculate the absolute mismatch:
=ABS(B2-C2)
Show:
Add one observation below the charts, such as:
Power BI broadly aligns with the validated results; however, differences were identified where service accounts were used after manual intervention or where automatically resolved incidents were manually closed by engineers.
Hi Vikram and Ranjit,
I wanted to share some context regarding a production support discussion that took place earlier.
Sunil added me to the group based on Prashant’s suggestion, as I was the DM and had CS access. After reviewing the issue and discussing it with the user, it appeared to be related to application/configuration rather than the database.
I explained this to the user and also included the EMEA DBA team for assistance, but there was no acknowledgement at the time. As the user continued reaching out for support, I added Prashant back to help with coordination. However, he subsequently left the group again, so I included both of you for visibility before leaving the chat.
The situation was difficult to manage due to access dependencies, limited documentation on the support process, and uncertainty around the correct ownership and escalation path. This resulted in the issue continuing to be directed to available individuals, even though it was outside their area of responsibility.
I am sharing this for awareness and to request clearer guidance on the appropriate ownership and escalation process for similar production issues going forward.
Regards,
Nikhil
Hello Friends! I am aliena part time blogger from Bihar. I am a student and I manage my study as well as my blog. I am 14 years old and I want to help those people who really want to do something on internet.
Copyright © 201. Metro UI Theme. Designed by: Templateism
