[SOLVED] URGENT! zmSetServerName killed Production Server?

[alapierre]

Ok, I've really screwed up here. I was trying to setup a Test server to play with backup/restores, and I ran ZmSetServerName on my test server while my Live server was up. I believe it did something bad. It was working at that moment, but then I issued the commands

zmprov ms mail.domain.com zimbraLmtpAdvertisedName testmail.domain.com
zmprov ms mail.domain.com zimbraServiceHostname testmail.domain.com

immediately, things went bad. I tried to fix it with

zmprov ms testmail.domain.com zimbraLmtpAdvertisedName mail.domain.com
zmprov ms testmail.domain.com zimbraServiceHostname mail.domain.com

and zmSetServerName mail.domain.com, but I can't connect still. webmail won't even load...it just sits there with the loading screen. Please help!

[alapierre]

Ok. I only tried running those commands on my test server, since that's where I had issued them originally. I dumped my production ldap and searched for my test server hostname. I found those two entries at the bottom. zimbraLmtpAdvertisedName and zimbraServiceHostname both set to testmail.domain.com. I immediately issued

zmprov ms testmail.domain.com zimbraLmtpAdvertisedName mail.domain.com

but it said testmail.domain.com didn't exist. So I did

zmprov ms mail.domain.com zimbraLmtpAdvertisedName mail.domain.com

for both settings, and that brought everything back up. Whew!