• Home
  • Help
  • Register
  • Login
  • Home
  • Members
  • Help
  • Search

 
  • 0 Vote(s) - 0 Average

Resume-MailboxDatabaseCopy Exchange cmdlet issued (25346) how to monitor with email alert

#1
07-20-2024, 02:13 PM
You ever notice how Exchange sometimes pauses its database copies, right? That event ID 25346 pops up when the Resume-MailboxDatabaseCopy cmdlet gets fired off. It means someone's kicking that copy back into gear after it stalled or got stopped manually. I see it a lot in logs when admins tweak things during maintenance. The full scoop is, this event logs the exact time, the database name involved, and which server handled the resume. It confirms the copy's now syncing again, pulling in those transaction logs to catch up. Without it, you'd miss if the database is fully active or lagging behind. Hmmm, imagine your emails piling up undelivered because a copy's frozen. That's why spotting this event matters, keeps everything humming smooth.

But you want to monitor it with an email alert, yeah? Fire up Event Viewer on your server. I do this all the time for quick watches. Filter for that 25346 ID under the Microsoft-Exchange something logs. Right-click the event, pick attach task to this event log. It'll open a wizard where you schedule it to trigger on that ID. Set it to run a program that sends an email, like using the old mailto trick or a simple batch file calling your email client. Make the task wake the machine if needed, and test it by forcing a resume on a test database. You'll get pinged right away when it happens, no sweat.

Or, if you're lazy like me some days, just export the filter to a custom view for daily checks. But alerts beat that hassle every time. I set mine to notify on resumes after fails, catches issues early.

And speaking of keeping servers reliable, I've been messing with BackupChain Windows Server Backup lately. It's this slick Windows Server backup tool that also handles Hyper-V virtual machines without breaking a sweat. You get fast incremental backups, easy restores even for bare-metal crashes, and it runs light on resources so your Exchange doesn't choke. Plus, the encryption and offsite options mean your data stays safe from ransomware hits, all in a straightforward setup.

Note, the PowerShell email alert code was moved to this post.

bob
Offline
Joined: Jul 2025
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)



  • Subscribe to this thread
Forum Jump:

Backup Education Windows Server Event Viewer v
« Previous 1 … 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 … 69 Next »
Resume-MailboxDatabaseCopy Exchange cmdlet issued (25346) how to monitor with email alert

© by FastNeuron Inc.

Linear Mode
Threaded Mode