|
Home > Archive > BizTalk Server General > December 2005 > Biztalk Server Distaster Recovery
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Biztalk Server Distaster Recovery
|
|
| Chris Holliday 2005-12-05, 5:55 pm |
| I am interested in any examples or insite into how others handle disaster
recovery for their Biztalk app servers? Assuming a node of BTS boxes are
destroyed in some event, what processes are used to do a full recovery of
the system? Is there some utility to extract all artifacts associated with
interfaces?
Thanks,
Chris
| |
| esgraham 2005-12-05, 5:55 pm |
| Is there some utility to extract all artifacts associated with
> interfaces?
I suggest using VSS to store the BizTalk solution files, including the maps,
schemas, orchestrations, etc. I also use the Deployment Wizard to create an
xml port binding file that I store in VSS for each project. Be sure to back
up your databases with the backup SQL job, so that you can recover your
databases.
"Chris Holliday" wrote:
> I am interested in any examples or insite into how others handle disaster
> recovery for their Biztalk app servers? Assuming a node of BTS boxes are
> destroyed in some event, what processes are used to do a full recovery of
> the system? Is there some utility to extract all artifacts associated with
> interfaces?
>
> Thanks,
>
> Chris
>
>
>
| |
|
| I am writing a series of articles about BizTalk 2004 Backup and Recovery. The
articles are available for free at http://wworkflow.net - click the
{dispatches} blog to access the articles.
Erik
wworkflow.net - BizTalk and more
"Chris Holliday" wrote:
> I am interested in any examples or insite into how others handle disaster
> recovery for their Biztalk app servers? Assuming a node of BTS boxes are
> destroyed in some event, what processes are used to do a full recovery of
> the system? Is there some utility to extract all artifacts associated with
> interfaces?
>
> Thanks,
>
> Chris
>
>
>
|
|
|
|
|