Unsolved
This post is more than 5 years old
2 Posts
0
458
June 17th, 2008 01:00
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
No Events found!
jskoecher
2 Intern
•
204 Posts
0
June 20th, 2008 05:00
in case you are using DX to move data further, don't forget to make the DX meta data backup as well... otherwise, you have your EX-Server and SQL-backup, but miss the storage "representatives" for EX!
The way you solved the problem is good. Have done this in various implementations as well... no other way to get this done (at least not from EX side).
Regards,
Jochen.
HarryR1
2 Posts
0
June 20th, 2008 05:00
yes, that is what ExSuspend do - but my problem is that I need to backup EX AND SQL at the same time - and as they are on different servers ...
IMHO problem solved now - I am going to backup the EX with classic "ExSuspend -> Backup -> ExSuspend resume" on EX server.
For SQL side - as I do the online backups with tr.log backups, I am able to do point-in-time restore, so in case of DR I just restore the last EX backup, note the time of it and then restore the SQL to the same moment.
Should work. (Thanx Blackman for the idea)
Harry
M314
36 Posts
0
June 20th, 2008 05:00
I thought the Suspend job would prevent any new work from starting and then let in-flight work complete and then stop the EX services.
Is that what the -timeout parameter is for ?
...Give it N seconds to get all that work completed.
But I am not sure.
Thanks.