Regarding SANs, new LUNs and migration

[vlaurenz]

Hi all,

I'm planning on moving my information store to a new LUN on our SAN with more capacity and LVM capabilities.

I'm wondering if and how, when I copy the data from the old LUN to the new LUN, I can stop a certain set of services/daemons such that the state of the information store will not change during the course of the copy, AND any incoming mail will be queued/deferred until I resume said set of Scalix services/daemons.

I have tried to search the forums and the wiki for an answer and have come up short. Has anyone done something similar? Does anyone have a definitive answer?

Thanks in advance.

[jcaudell]

I'm no expert, but when I stopped scalix to redo my LVMs, the sendmail smtp queued up messages for me (I sent one from outside specifically), and I received the message when I restarted Scalix. I'd make sure that Scalix is totally stopped before changing around drives/partitions, etc. Hope this helps.

[vlaurenz]

I'm no expert, but when I stopped scalix to redo my LVMs, the sendmail smtp queued up messages for me (I sent one from outside specifically), and I received the message when I restarted Scalix. I'd make sure that Scalix is totally stopped before changing around drives/partitions, etc. Hope this helps.

Really? I'm wondering how that would be possible. In a standard Scalix setup, sendmail is the MTA for outgoing mail only. I guess with Scalix off, sendmail is "allowed" to listen to incoming mail and spool it?

Can anyone confirm this behaviour?

[ScalixSupport]

Please see:

Stopping all scalix services and moving /var/opt/scalix to the new partition is the way to go. Make sure you maintain permissions.

When your host is not listening on port 25 any host trying to send to you will not be able to. The sending mta will then queue the messages destined to you and will try periodically to resend. Once you've brought scalix services back up the sending mta will deliver your messages.

Regards,
Don