
UNSOLVED
EmailXtender backup - split installation
Hello all,
newbie here ...
One of our customers has a EmailXtender installed with SQL on the other box. Question is, how to backup this configuration.
I know (from the books) that I can suspend the operation using ExSuspend utility (placed in pre-backup script) so data processing is stopped. (Am I right when I think all the messages queued in the meantime are processed after services resume?)
With SQL installed on the other server there is a timing problem.What I figured out is
1) suspending EX
2) backup EX server (with containers)
3) running backup of SQL (using psexec or other way of remote execution)
4) resuming EX
That remote execution is the thing I would like to rid off.
What happens if I backup the SQL BEFORE I suspend the EX? After restore I have SQL and containers with valid data and few messages SQL does not know about (which does not worry me - they are going to be backed up next day) - so I should be able to "see" to the point of SQL backup ... but what happens when new message is processed? Will the EX start witting at the end of the container or offset of that file (so that abundant data is overwritten) ....
Or am I just trying to make my life more complicated?
Thanks
Harry
Message was edited by:
HarryR
newbie here ...
One of our customers has a EmailXtender installed with SQL on the other box. Question is, how to backup this configuration.
I know (from the books) that I can suspend the operation using ExSuspend utility (placed in pre-backup script) so data processing is stopped. (Am I right when I think all the messages queued in the meantime are processed after services resume?)
With SQL installed on the other server there is a timing problem.What I figured out is
1) suspending EX
2) backup EX server (with containers)
3) running backup of SQL (using psexec or other way of remote execution)
4) resuming EX
That remote execution is the thing I would like to rid off.
What happens if I backup the SQL BEFORE I suspend the EX? After restore I have SQL and containers with valid data and few messages SQL does not know about (which does not worry me - they are going to be backed up next day) - so I should be able to "see" to the point of SQL backup ... but what happens when new message is processed? Will the EX start witting at the end of the container or offset of that file (so that abundant data is overwritten) ....
Or am I just trying to make my life more complicated?
Thanks
Harry
Message was edited by:
HarryR
Responses (0)
Solutions (0)
