@AshipaEK0@IkejaElectric Dear Valued Customer,
We apologize for the inconvenience.
Please make your complaints via the channel - https://t.co/OQmuYFsraz
Manage your electricity by downloading the EKEDP POWER APP.
Use referral code IOPB-TFLX when signing up!
Regards,
MA
As an IT Manager who is forced to give updates to the entire company when systems are down, I have mad respect for how empty these updates are. So often we have no clue what's going on but still have to push out an update. I'm definitely incorporating this into my future comms.
**shudders**
Earlier in my career, I worked at a place where I inherited a Windows SBS, on which they had also installed Exchange 🥹
I survived the 2am alerts without PTSD. Exchange was the only software I had to solicit external help to fix
I've been managing Exchange servers for nearly 2 decades.
It is one of the most complex pieces of infrastructure to manage because its databases are enormous and take a long time to repair and rebuild under disaster situations.
Additionally, if the majority of a Database Availability Group (DAG) failed simultaneously, users could experience data loss.
Recovering from backups is an extremely long process and backups could be outdated by a few hours (this is how Exchange backups work).
Imagine moving hundreds of petabytes of data over iSCSI storage. Regardless of how fast the iSCSI and links are, the sheer amount of data makes this a daunting task.
I wouldn't be surprised if this recovery took multiple days and ended up with data loss for multiple users.
I do not miss the days when I'd be woken up at 2am because an Exchange server failed and the DAG was offline.