No, no backups. Some issues in Windows Server 2019 resulted in a lost directory. Data survived bc storage servers aren't Windows-based but while things finish settling up a few extra cautions are taken when using our own self-hosted services when they're non-redundant or have Microsoft code.
It actually occurred to me using some Set-
-type cmdlet but the thing is that it's still hard to get every mailbox as they are lot used by the system that have some obscure way of dealing with them. Setting the mailboxes to another database was way to easy for Exchange. Additionally I ran:
[PS] D:\>Get-Mailbox -PublicFolder | Disable-Mailbox
[PS] D:\>Get-Mailbox -Archive | Disable-Mailbox
[PS] D:\>Get-Mailbox -AuditLog | Disable-Mailbox
[PS] D:\>Get-Mailbox -RemoteArchive | Disable-Mailbox
[PS] D:\>Get-Mailbox -Archive | Disable-Mailbox
…and the database is still locked. I skipped the tone thing because I don't need to recover data at all.
I guess I'll have to spent the next days manually removing Exchange from the directory and setting up a new server. That sucks. It's not all bad though, I have some space old Macs with macOS Server that connects with AD and it takes about 10-12-click to set up a mail server and that's counting the clicks to login. It'll have to take Exchange's place. No webmail, though, it's the only feature we use Exchange for.
Nevertheless, thank you for answering. Like I said earlier, I'm truly grateful for that. Have a nice week!
…and I'm off to the freezing server room…