Remote backup server for disaster recovery

[Guest GerryA]

I need some advice regarding a project to create a remote server that users

can access in the event of a disaster that causes access to the main server

to be unavailable. The scenario is that in the event of a pending disaster

some employees will relocate and access the main server/office remotely. If

this remote access becomes affected by the disaster then the users will

switch to the alternate server in a remote location. I am looking for advice

as to how best to configure the remote server, do i add it to the existing

Domain and then restore the data to it?

My current train of though is that the servers will not be linked after the

original configuration and relocation of the backup server, what will happen

is that the remote server will only be turned on when needed and the data

restored to it. The data is currently being backed up by a service that will

also house the remote server therefore restoration of the data should not be

too much of an issue.

Any advice is greatfully accepted.

[Guest Lanwench [MVP - Exchange]]

Re: Remote backup server for disaster recovery

 

GerryA <GerryA@discussions.microsoft.com> wrote:

> I need some advice regarding a project to create a remote server that

> users can access in the event of a disaster that causes access to the

> main server to be unavailable. The scenario is that in the event of a

> pending disaster some employees will relocate and access the main

> server/office remotely. If this remote access becomes affected by the

> disaster then the users will switch to the alternate server in a

> remote location. I am looking for advice as to how best to configure

> the remote server, do i add it to the existing Domain and then

> restore the data to it?

> My current train of though is that the servers will not be linked

> after the original configuration and relocation of the backup server,

> what will happen is that the remote server will only be turned on

> when needed and the data restored to it. The data is currently being

> backed up by a service that will also house the remote server

> therefore restoration of the data should not be too much of an issue.

> Any advice is greatfully accepted.

 

Since you already have an online backup service....what do *they* say about

this? Will they back up system state, etc? What else do you run on the main

server?

 

If you can configure a hardware-based VPN link, or leased line connection,

between the two locations, you can add the other machine as a DC/DNS/GC, and

use DFS or other means (even the lowly robocopy) to get your data onto the

secondary box.

[Guest Anthony]

Re: Remote backup server for disaster recovery

 

GerryA,

You can just set the server up as a live site. AD will replicate and give

you a fallback server. DFSR can be used to replicate data.

Anthony

http://www.airdesk.co.uk

 

"GerryA" <GerryA@discussions.microsoft.com> wrote in message

news:C5D36E1C-B51A-4562-A4BF-78574B42861E@microsoft.com...

>I need some advice regarding a project to create a remote server that users

> can access in the event of a disaster that causes access to the main

> server

> to be unavailable. The scenario is that in the event of a pending disaster

> some employees will relocate and access the main server/office remotely.

> If

> this remote access becomes affected by the disaster then the users will

> switch to the alternate server in a remote location. I am looking for

> advice

> as to how best to configure the remote server, do i add it to the existing

> Domain and then restore the data to it?

> My current train of though is that the servers will not be linked after

> the

> original configuration and relocation of the backup server, what will

> happen

> is that the remote server will only be turned on when needed and the data

> restored to it. The data is currently being backed up by a service that

> will

> also house the remote server therefore restoration of the data should not

> be

> too much of an issue.

> Any advice is greatfully accepted.

[Guest GerryA]

Re: Remote backup server for disaster recovery

 

Ok, thanks for the reply. I understand that AD will replicate to the new

server but what is DFSR and will it work over a 1MB WAN link? Forgive my

ignorance.

 

"Anthony" wrote:

> GerryA,

> You can just set the server up as a live site. AD will replicate and give

> you a fallback server. DFSR can be used to replicate data.

> Anthony

> http://www.airdesk.co.uk

>

> "GerryA" <GerryA@discussions.microsoft.com> wrote in message

> news:C5D36E1C-B51A-4562-A4BF-78574B42861E@microsoft.com...

> >I need some advice regarding a project to create a remote server that users

> > can access in the event of a disaster that causes access to the main

> > server

> > to be unavailable. The scenario is that in the event of a pending disaster

> > some employees will relocate and access the main server/office remotely.

> > If

> > this remote access becomes affected by the disaster then the users will

> > switch to the alternate server in a remote location. I am looking for

> > advice

> > as to how best to configure the remote server, do i add it to the existing

> > Domain and then restore the data to it?

> > My current train of though is that the servers will not be linked after

> > the

> > original configuration and relocation of the backup server, what will

> > happen

> > is that the remote server will only be turned on when needed and the data

> > restored to it. The data is currently being backed up by a service that

> > will

> > also house the remote server therefore restoration of the data should not

> > be

> > too much of an issue.

> > Any advice is greatfully accepted.

>

>

>

[Guest GerryA]

Re: Remote backup server for disaster recovery

 

ok, thanks for the response. You guys really like these acronyms and have me

a bit at a loss sometimes with them. Please bear with me here, what do you

mean by "GC" and "DFS". The main server does run a client sever based

application (Accpac) so that will have to be installed and configured. What

are the licensing issuses related to this type of arrangement?

My original plan is to install Windows 2003 and configure it with the

necessary software etc then restore current data from the exisiting server

and run some tests before moving the server to the remote location. Is that a

viable plan? The restoring of data is something that we have to initiate

ourselves as far as I know but I will have to check into that further.

 

"Lanwench [MVP - Exchange]" wrote:

> GerryA <GerryA@discussions.microsoft.com> wrote:

> > I need some advice regarding a project to create a remote server that

> > users can access in the event of a disaster that causes access to the

> > main server to be unavailable. The scenario is that in the event of a

> > pending disaster some employees will relocate and access the main

> > server/office remotely. If this remote access becomes affected by the

> > disaster then the users will switch to the alternate server in a

> > remote location. I am looking for advice as to how best to configure

> > the remote server, do i add it to the existing Domain and then

> > restore the data to it?

> > My current train of though is that the servers will not be linked

> > after the original configuration and relocation of the backup server,

> > what will happen is that the remote server will only be turned on

> > when needed and the data restored to it. The data is currently being

> > backed up by a service that will also house the remote server

> > therefore restoration of the data should not be too much of an issue.

> > Any advice is greatfully accepted.

>

> Since you already have an online backup service....what do *they* say about

> this? Will they back up system state, etc? What else do you run on the main

> server?

>

> If you can configure a hardware-based VPN link, or leased line connection,

> between the two locations, you can add the other machine as a DC/DNS/GC, and

> use DFS or other means (even the lowly robocopy) to get your data onto the

> secondary box.

>

>

>

[Guest Lanwench [MVP - Exchange]]

Re: Remote backup server for disaster recovery

 

GerryA <GerryA@discussions.microsoft.com> wrote:

> ok, thanks for the response. You guys really like these acronyms and

> have me a bit at a loss sometimes with them. Please bear with me

> here, what do you mean by "GC"

 

Global Catalog server

> and "DFS".

 

Distributed File System:

http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/default.mspx

 

> The main server does run a

> client sever based application (Accpac) so that will have to be

> installed and configured. What are the licensing issuses related to

> this type of arrangement?

 

If you have R2 I *believe* you're allowed to have a cold standby server, but

for any and all licensing questions, it's best to ask MS or a reseller

directly.

 

> My original plan is to install Windows 2003 and configure it with the

> necessary software etc then restore current data from the exisiting

> server and run some tests before moving the server to the remote

> location. Is that a viable plan? The restoring of data is something

> that we have to initiate ourselves as far as I know but I will have

> to check into that further.

 

You might look into http://www.intronis.com as an alternative. It can do system

state backups, etc.

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> GerryA <GerryA@discussions.microsoft.com> wrote:

>>> I need some advice regarding a project to create a remote server

>>> that users can access in the event of a disaster that causes access

>>> to the main server to be unavailable. The scenario is that in the

>>> event of a pending disaster some employees will relocate and access

>>> the main server/office remotely. If this remote access becomes

>>> affected by the disaster then the users will switch to the

>>> alternate server in a remote location. I am looking for advice as

>>> to how best to configure the remote server, do i add it to the

>>> existing Domain and then restore the data to it?

>>> My current train of though is that the servers will not be linked

>>> after the original configuration and relocation of the backup

>>> server, what will happen is that the remote server will only be

>>> turned on when needed and the data restored to it. The data is

>>> currently being backed up by a service that will also house the

>>> remote server therefore restoration of the data should not be too

>>> much of an issue. Any advice is greatfully accepted.

>>

>> Since you already have an online backup service....what do *they*

>> say about this? Will they back up system state, etc? What else do

>> you run on the main server?

>>

>> If you can configure a hardware-based VPN link, or leased line

>> connection, between the two locations, you can add the other machine

>> as a DC/DNS/GC, and use DFS or other means (even the lowly robocopy)

>> to get your data onto the secondary box.

[Guest GerryA]

Re: Remote backup server for disaster recovery

 

Wow, thanks, lots more reading for me now! Here we go again. Thanks for your

help, I am sure I will have more questions after this after I wade through

this information.

 

"Lanwench [MVP - Exchange]" wrote:

> GerryA <GerryA@discussions.microsoft.com> wrote:

> > ok, thanks for the response. You guys really like these acronyms and

> > have me a bit at a loss sometimes with them. Please bear with me

> > here, what do you mean by "GC"

>

> Global Catalog server

>

> > and "DFS".

>

> Distributed File System:

> http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/default.mspx

>

>

> > The main server does run a

> > client sever based application (Accpac) so that will have to be

> > installed and configured. What are the licensing issuses related to

> > this type of arrangement?

>

> If you have R2 I *believe* you're allowed to have a cold standby server, but

> for any and all licensing questions, it's best to ask MS or a reseller

> directly.

>

>

> > My original plan is to install Windows 2003 and configure it with the

> > necessary software etc then restore current data from the exisiting

> > server and run some tests before moving the server to the remote

> > location. Is that a viable plan? The restoring of data is something

> > that we have to initiate ourselves as far as I know but I will have

> > to check into that further.

>

> You might look into http://www.intronis.com as an alternative. It can do system

> state backups, etc.

> >

> > "Lanwench [MVP - Exchange]" wrote:

> >

> >> GerryA <GerryA@discussions.microsoft.com> wrote:

> >>> I need some advice regarding a project to create a remote server

> >>> that users can access in the event of a disaster that causes access

> >>> to the main server to be unavailable. The scenario is that in the

> >>> event of a pending disaster some employees will relocate and access

> >>> the main server/office remotely. If this remote access becomes

> >>> affected by the disaster then the users will switch to the

> >>> alternate server in a remote location. I am looking for advice as

> >>> to how best to configure the remote server, do i add it to the

> >>> existing Domain and then restore the data to it?

> >>> My current train of though is that the servers will not be linked

> >>> after the original configuration and relocation of the backup

> >>> server, what will happen is that the remote server will only be

> >>> turned on when needed and the data restored to it. The data is

> >>> currently being backed up by a service that will also house the

> >>> remote server therefore restoration of the data should not be too

> >>> much of an issue. Any advice is greatfully accepted.

> >>

> >> Since you already have an online backup service....what do *they*

> >> say about this? Will they back up system state, etc? What else do

> >> you run on the main server?

> >>

> >> If you can configure a hardware-based VPN link, or leased line

> >> connection, between the two locations, you can add the other machine

> >> as a DC/DNS/GC, and use DFS or other means (even the lowly robocopy)

> >> to get your data onto the secondary box.

>

>

>

>

[Guest Lanwench [MVP - Exchange]]

Re: Remote backup server for disaster recovery

 

GerryA <GerryA@discussions.microsoft.com> wrote:

> Wow, thanks, lots more reading for me now! Here we go again. Thanks

> for your help, I am sure I will have more questions after this after

> I wade through this information.

 

You're most welcome. Have fun storming the castle!

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> GerryA <GerryA@discussions.microsoft.com> wrote:

>>> ok, thanks for the response. You guys really like these acronyms and

>>> have me a bit at a loss sometimes with them. Please bear with me

>>> here, what do you mean by "GC"

>>

>> Global Catalog server

>>

>>> and "DFS".

>>

>> Distributed File System:

>> http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/default.mspx

>>

>>

>>> The main server does run a

>>> client sever based application (Accpac) so that will have to be

>>> installed and configured. What are the licensing issuses related to

>>> this type of arrangement?

>>

>> If you have R2 I *believe* you're allowed to have a cold standby

>> server, but for any and all licensing questions, it's best to ask MS

>> or a reseller directly.

>>

>>

>>> My original plan is to install Windows 2003 and configure it with

>>> the necessary software etc then restore current data from the

>>> exisiting server and run some tests before moving the server to the

>>> remote location. Is that a viable plan? The restoring of data is

>>> something that we have to initiate ourselves as far as I know but I

>>> will have to check into that further.

>>

>> You might look into http://www.intronis.com as an alternative. It can do

>> system state backups, etc.

>>>

>>> "Lanwench [MVP - Exchange]" wrote:

>>>

>>>> GerryA <GerryA@discussions.microsoft.com> wrote:

>>>>> I need some advice regarding a project to create a remote server

>>>>> that users can access in the event of a disaster that causes

>>>>> access to the main server to be unavailable. The scenario is that

>>>>> in the event of a pending disaster some employees will relocate

>>>>> and access the main server/office remotely. If this remote access

>>>>> becomes affected by the disaster then the users will switch to the

>>>>> alternate server in a remote location. I am looking for advice as

>>>>> to how best to configure the remote server, do i add it to the

>>>>> existing Domain and then restore the data to it?

>>>>> My current train of though is that the servers will not be linked

>>>>> after the original configuration and relocation of the backup

>>>>> server, what will happen is that the remote server will only be

>>>>> turned on when needed and the data restored to it. The data is

>>>>> currently being backed up by a service that will also house the

>>>>> remote server therefore restoration of the data should not be too

>>>>> much of an issue. Any advice is greatfully accepted.

>>>>

>>>> Since you already have an online backup service....what do *they*

>>>> say about this? Will they back up system state, etc? What else do

>>>> you run on the main server?

>>>>

>>>> If you can configure a hardware-based VPN link, or leased line

>>>> connection, between the two locations, you can add the other

>>>> machine as a DC/DNS/GC, and use DFS or other means (even the lowly

>>>> robocopy) to get your data onto the secondary box.

[Guest Anthony]

Re: Remote backup server for disaster recovery

 

DFS-Replication will work fine over 1MB, after the initial synch. It depends

on the volume of course, but you have to get the backup copy of data there

somehow. There is no getting round that (except if you had a lot of changing

data you may have to ship the tapes off site and do a restore from tape).

Anthony

http://www.airdesk.co.uk

 

 

 

"GerryA" <GerryA@discussions.microsoft.com> wrote in message

news:5823C8BC-0D4A-44E9-B735-191B50647DDD@microsoft.com...

> Ok, thanks for the reply. I understand that AD will replicate to the new

> server but what is DFSR and will it work over a 1MB WAN link? Forgive my

> ignorance.

>

> "Anthony" wrote:

>

>> GerryA,

>> You can just set the server up as a live site. AD will replicate and give

>> you a fallback server. DFSR can be used to replicate data.

>> Anthony

>> http://www.airdesk.co.uk

>>

>> "GerryA" <GerryA@discussions.microsoft.com> wrote in message

>> news:C5D36E1C-B51A-4562-A4BF-78574B42861E@microsoft.com...

>> >I need some advice regarding a project to create a remote server that

>> >users

>> > can access in the event of a disaster that causes access to the main

>> > server

>> > to be unavailable. The scenario is that in the event of a pending

>> > disaster

>> > some employees will relocate and access the main server/office

>> > remotely.

>> > If

>> > this remote access becomes affected by the disaster then the users will

>> > switch to the alternate server in a remote location. I am looking for

>> > advice

>> > as to how best to configure the remote server, do i add it to the

>> > existing

>> > Domain and then restore the data to it?

>> > My current train of though is that the servers will not be linked after

>> > the

>> > original configuration and relocation of the backup server, what will

>> > happen

>> > is that the remote server will only be turned on when needed and the

>> > data

>> > restored to it. The data is currently being backed up by a service that

>> > will

>> > also house the remote server therefore restoration of the data should

>> > not

>> > be

>> > too much of an issue.

>> > Any advice is greatfully accepted.

>>

>>

>>