| Author |
Message |
Trevor Seward
Guest
|
 Posted:
Tue Aug 23, 2005 12:51 am Post subject:
Insuring that data isn't placed in a PreExisting folder? |
|
|
What is the sure-fire way to prevent existing data being placed in a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based DFS root
with 3 DFS links. I have another server that this data needs to replicate
to which is devoid of any files/folders. I'm finding once I enable
replication, anything on my original server goes into the PreExisting folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor |
|
| Back to top |
|
 |
Jill Zoeller [MSFT]
Guest
|
| Posted:
Wed Aug 24, 2005 4:52 pm Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
Can you confirm that you have chosen the server with the existing content as
the initial master when you set up replication? The behavior you describe
should happen on the non-initial masters if they have pre-existing content.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
| Quote: | What is the sure-fire way to prevent existing data being placed in a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based DFS root
with 3 DFS links. I have another server that this data needs to replicate
to which is devoid of any files/folders. I'm finding once I enable
replication, anything on my original server goes into the PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Trevor
Guest
|
| Posted:
Wed Aug 24, 2005 8:53 pm Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
| Quote: | Can you confirm that you have chosen the server with the existing content
as
the initial master when you set up replication? The behavior you describe
should happen on the non-initial masters if they have pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being placed in a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based DFS
root
with 3 DFS links. I have another server that this data needs to
replicate
to which is devoid of any files/folders. I'm finding once I enable
replication, anything on my original server goes into the PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Jill Zoeller [MSFT]
Guest
|
| Posted:
Thu Aug 25, 2005 12:51 am Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
If you are choosing the correct initial master (i.e., your root server) when
you run the wizard, and data on that server is still moving to preexisting,
this sounds like something you'll need to work with product support to
solve. Data on the initial server should not move to preexisting because
this content is considered authoritative. Something strange is happening,
and unfortunately I don't have an answer as to why.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Trevor" <null@rottdog.com> wrote in message
news:OGFX1APqFHA.3160@TK2MSFTNGP14.phx.gbl...
| Quote: | The current setup is that the root server also has the DFS links (with no
replication partners) and contains all of the data.
Once I add a link and set up replication, that is when all my data on the
root/original server goes into PreExisting. The replication partner has
no
data on it.
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:OHERr6OqFHA.2432@TK2MSFTNGP10.phx.gbl...
From the behavior you describe, it does sound like you chose the "empty"
server to be the initial master. This means that your other server would
move its content to Pre-existing folder so that the server is also
"empty."
But I don't know of a way to definitively confirm which server you chose
in
the wizard.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:O2OYtFNqFHA.2240@tk2msftngp13.phx.gbl...
The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
Can you confirm that you have chosen the server with the existing
content
as
the initial master when you set up replication? The behavior you
describe
should happen on the non-initial masters if they have pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being placed in a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based DFS
root
with 3 DFS links. I have another server that this data needs to
replicate
to which is devoid of any files/folders. I'm finding once I enable
replication, anything on my original server goes into the
PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Jill Zoeller [MSFT]
Guest
|
| Posted:
Thu Aug 25, 2005 12:51 am Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
From the behavior you describe, it does sound like you chose the "empty"
server to be the initial master. This means that your other server would
move its content to Pre-existing folder so that the server is also "empty."
But I don't know of a way to definitively confirm which server you chose in
the wizard.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Trevor" <null@rottdog.com> wrote in message
news:O2OYtFNqFHA.2240@tk2msftngp13.phx.gbl...
| Quote: | The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
Can you confirm that you have chosen the server with the existing content
as
the initial master when you set up replication? The behavior you describe
should happen on the non-initial masters if they have pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being placed in a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based DFS
root
with 3 DFS links. I have another server that this data needs to
replicate
to which is devoid of any files/folders. I'm finding once I enable
replication, anything on my original server goes into the PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Trevor
Guest
|
| Posted:
Thu Aug 25, 2005 12:51 am Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
The current setup is that the root server also has the DFS links (with no
replication partners) and contains all of the data.
Once I add a link and set up replication, that is when all my data on the
root/original server goes into PreExisting. The replication partner has no
data on it.
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:OHERr6OqFHA.2432@TK2MSFTNGP10.phx.gbl...
| Quote: | From the behavior you describe, it does sound like you chose the "empty"
server to be the initial master. This means that your other server would
move its content to Pre-existing folder so that the server is also
"empty."
But I don't know of a way to definitively confirm which server you chose
in
the wizard.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:O2OYtFNqFHA.2240@tk2msftngp13.phx.gbl...
The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
Can you confirm that you have chosen the server with the existing
content
as
the initial master when you set up replication? The behavior you
describe
should happen on the non-initial masters if they have pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being placed in a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based DFS
root
with 3 DFS links. I have another server that this data needs to
replicate
to which is devoid of any files/folders. I'm finding once I enable
replication, anything on my original server goes into the PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Trevor
Guest
|
| Posted:
Thu Aug 25, 2005 8:52 pm Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
Is it possible that you could provide me with the steps to do this correctly
given that the root server is already set up with links? Perhaps I'm just
missing something.
Thanks Jill!
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:#P1NyFQqFHA.3304@TK2MSFTNGP11.phx.gbl...
| Quote: | If you are choosing the correct initial master (i.e., your root server)
when
you run the wizard, and data on that server is still moving to
preexisting,
this sounds like something you'll need to work with product support to
solve. Data on the initial server should not move to preexisting because
this content is considered authoritative. Something strange is happening,
and unfortunately I don't have an answer as to why.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:OGFX1APqFHA.3160@TK2MSFTNGP14.phx.gbl...
The current setup is that the root server also has the DFS links (with
no
replication partners) and contains all of the data.
Once I add a link and set up replication, that is when all my data on
the
root/original server goes into PreExisting. The replication partner has
no
data on it.
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:OHERr6OqFHA.2432@TK2MSFTNGP10.phx.gbl...
From the behavior you describe, it does sound like you chose the
"empty"
server to be the initial master. This means that your other server
would
move its content to Pre-existing folder so that the server is also
"empty."
But I don't know of a way to definitively confirm which server you
chose
in
the wizard.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:O2OYtFNqFHA.2240@tk2msftngp13.phx.gbl...
The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do
this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
Can you confirm that you have chosen the server with the existing
content
as
the initial master when you set up replication? The behavior you
describe
should happen on the non-initial masters if they have pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being placed in
a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based
DFS
root
with 3 DFS links. I have another server that this data needs to
replicate
to which is devoid of any files/folders. I'm finding once I
enable
replication, anything on my original server goes into the
PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Jill Zoeller [MSFT]
Guest
|
| Posted:
Thu Aug 25, 2005 8:52 pm Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
You bet. I assume (based on your past post) that you're using the W2K3
version of the snap-in.
1. In the Distributed File System snap-in, right-click the link that has
multiple targets that you want to replicate, and then click Configure
Replication.
2. In the Configure Replication Wizard opening page, click Next.
3. On this page, you'll choose the initial master. Make sure you are
selecting the server that already contains the content. Here is the
explanation from the wizard, fyi: "You must select one target as the initial
master. The first time you start replication, its contents are replicated to
the other targets."
From here on out, you can just follow the wizard to choose the topology,
etc. The most important page for you is the initial master page. Perhaps
it's defaulting to the empty server? I'm guessing the server list is just
alphabatized--I don't think the wizard attempts to look at the content of
the link target.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Trevor" <null@rottdog.com> wrote in message
news:e2b%23CjZqFHA.3680@TK2MSFTNGP15.phx.gbl...
| Quote: | Is it possible that you could provide me with the steps to do this
correctly
given that the root server is already set up with links? Perhaps I'm just
missing something.
Thanks Jill!
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:#P1NyFQqFHA.3304@TK2MSFTNGP11.phx.gbl...
If you are choosing the correct initial master (i.e., your root server)
when
you run the wizard, and data on that server is still moving to
preexisting,
this sounds like something you'll need to work with product support to
solve. Data on the initial server should not move to preexisting because
this content is considered authoritative. Something strange is happening,
and unfortunately I don't have an answer as to why.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:OGFX1APqFHA.3160@TK2MSFTNGP14.phx.gbl...
The current setup is that the root server also has the DFS links (with
no
replication partners) and contains all of the data.
Once I add a link and set up replication, that is when all my data on
the
root/original server goes into PreExisting. The replication partner
has
no
data on it.
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:OHERr6OqFHA.2432@TK2MSFTNGP10.phx.gbl...
From the behavior you describe, it does sound like you chose the
"empty"
server to be the initial master. This means that your other server
would
move its content to Pre-existing folder so that the server is also
"empty."
But I don't know of a way to definitively confirm which server you
chose
in
the wizard.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:O2OYtFNqFHA.2240@tk2msftngp13.phx.gbl...
The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do
this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
Can you confirm that you have chosen the server with the existing
content
as
the initial master when you set up replication? The behavior you
describe
should happen on the non-initial masters if they have pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being placed
in
a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based
DFS
root
with 3 DFS links. I have another server that this data needs to
replicate
to which is devoid of any files/folders. I'm finding once I
enable
replication, anything on my original server goes into the
PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Trevor
Guest
|
| Posted:
Thu Aug 25, 2005 8:52 pm Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
Great, I will try this out as soon as I can. I'll let you know if I have
any problems. FYI what I've typically been doing is during the addition of
the 2nd (no data present) server, it wants to run the replication wizard at
that point. I'll try cancelling it and simply following your instructions.
Thanks Jill!
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:O73RpuZqFHA.2816@tk2msftngp13.phx.gbl...
| Quote: | You bet. I assume (based on your past post) that you're using the W2K3
version of the snap-in.
1. In the Distributed File System snap-in, right-click the link that has
multiple targets that you want to replicate, and then click Configure
Replication.
2. In the Configure Replication Wizard opening page, click Next.
3. On this page, you'll choose the initial master. Make sure you are
selecting the server that already contains the content. Here is the
explanation from the wizard, fyi: "You must select one target as the
initial
master. The first time you start replication, its contents are replicated
to
the other targets."
From here on out, you can just follow the wizard to choose the topology,
etc. The most important page for you is the initial master page. Perhaps
it's defaulting to the empty server? I'm guessing the server list is just
alphabatized--I don't think the wizard attempts to look at the content of
the link target.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:e2b%23CjZqFHA.3680@TK2MSFTNGP15.phx.gbl...
Is it possible that you could provide me with the steps to do this
correctly
given that the root server is already set up with links? Perhaps I'm
just
missing something.
Thanks Jill!
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:#P1NyFQqFHA.3304@TK2MSFTNGP11.phx.gbl...
If you are choosing the correct initial master (i.e., your root server)
when
you run the wizard, and data on that server is still moving to
preexisting,
this sounds like something you'll need to work with product support to
solve. Data on the initial server should not move to preexisting
because
this content is considered authoritative. Something strange is
happening,
and unfortunately I don't have an answer as to why.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:OGFX1APqFHA.3160@TK2MSFTNGP14.phx.gbl...
The current setup is that the root server also has the DFS links
(with
no
replication partners) and contains all of the data.
Once I add a link and set up replication, that is when all my data on
the
root/original server goes into PreExisting. The replication partner
has
no
data on it.
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:OHERr6OqFHA.2432@TK2MSFTNGP10.phx.gbl...
From the behavior you describe, it does sound like you chose the
"empty"
server to be the initial master. This means that your other server
would
move its content to Pre-existing folder so that the server is also
"empty."
But I don't know of a way to definitively confirm which server you
chose
in
the wizard.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:O2OYtFNqFHA.2240@tk2msftngp13.phx.gbl...
The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do
this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in
message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
Can you confirm that you have chosen the server with the existing
content
as
the initial master when you set up replication? The behavior you
describe
should happen on the non-initial masters if they have
pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers
no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being placed
in
a
PreExisting folder when setting up replication?
I have one server that is currently configured as a
domain-based
DFS
root
with 3 DFS links. I have another server that this data needs
to
replicate
to which is devoid of any files/folders. I'm finding once I
enable
replication, anything on my original server goes into the
PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Jill Zoeller [MSFT]
Guest
|
| Posted:
Thu Aug 25, 2005 8:52 pm Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
Good call. I think the same wizard is launched, but I can't say for sure
whether the steps are different.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Trevor" <null@rottdog.com> wrote in message
news:eYt1oCbqFHA.3064@TK2MSFTNGP15.phx.gbl...
| Quote: | Great, I will try this out as soon as I can. I'll let you know if I have
any problems. FYI what I've typically been doing is during the addition
of
the 2nd (no data present) server, it wants to run the replication wizard
at
that point. I'll try cancelling it and simply following your
instructions.
Thanks Jill!
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:O73RpuZqFHA.2816@tk2msftngp13.phx.gbl...
You bet. I assume (based on your past post) that you're using the W2K3
version of the snap-in.
1. In the Distributed File System snap-in, right-click the link that has
multiple targets that you want to replicate, and then click Configure
Replication.
2. In the Configure Replication Wizard opening page, click Next.
3. On this page, you'll choose the initial master. Make sure you are
selecting the server that already contains the content. Here is the
explanation from the wizard, fyi: "You must select one target as the
initial
master. The first time you start replication, its contents are replicated
to
the other targets."
From here on out, you can just follow the wizard to choose the topology,
etc. The most important page for you is the initial master page. Perhaps
it's defaulting to the empty server? I'm guessing the server list is just
alphabatized--I don't think the wizard attempts to look at the content of
the link target.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:e2b%23CjZqFHA.3680@TK2MSFTNGP15.phx.gbl...
Is it possible that you could provide me with the steps to do this
correctly
given that the root server is already set up with links? Perhaps I'm
just
missing something.
Thanks Jill!
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:#P1NyFQqFHA.3304@TK2MSFTNGP11.phx.gbl...
If you are choosing the correct initial master (i.e., your root
server)
when
you run the wizard, and data on that server is still moving to
preexisting,
this sounds like something you'll need to work with product support to
solve. Data on the initial server should not move to preexisting
because
this content is considered authoritative. Something strange is
happening,
and unfortunately I don't have an answer as to why.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:OGFX1APqFHA.3160@TK2MSFTNGP14.phx.gbl...
The current setup is that the root server also has the DFS links
(with
no
replication partners) and contains all of the data.
Once I add a link and set up replication, that is when all my data
on
the
root/original server goes into PreExisting. The replication partner
has
no
data on it.
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:OHERr6OqFHA.2432@TK2MSFTNGP10.phx.gbl...
From the behavior you describe, it does sound like you chose the
"empty"
server to be the initial master. This means that your other server
would
move its content to Pre-existing folder so that the server is also
"empty."
But I don't know of a way to definitively confirm which server you
chose
in
the wizard.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:O2OYtFNqFHA.2240@tk2msftngp13.phx.gbl...
The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do
this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in
message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
Can you confirm that you have chosen the server with the
existing
content
as
the initial master when you set up replication? The behavior you
describe
should happen on the non-initial masters if they have
pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers
no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being
placed
in
a
PreExisting folder when setting up replication?
I have one server that is currently configured as a
domain-based
DFS
root
with 3 DFS links. I have another server that this data needs
to
replicate
to which is devoid of any files/folders. I'm finding once I
enable
replication, anything on my original server goes into the
PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
Trevor
Guest
|
| Posted:
Mon Sep 19, 2005 4:51 pm Post subject:
Re: Insuring that data isn't placed in a PreExisting folder? |
|
|
Jill, thank you. I didn't read that page of the wizard closely enough, and
yes, the member with the data was first in the list so I'd be configuring
the FRS staging folder in order -- which means of course that I'd be
selecting the member without the data!
Thanks again!
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:O73RpuZqFHA.2816@tk2msftngp13.phx.gbl...
| Quote: | You bet. I assume (based on your past post) that you're using the W2K3
version of the snap-in.
1. In the Distributed File System snap-in, right-click the link that has
multiple targets that you want to replicate, and then click Configure
Replication.
2. In the Configure Replication Wizard opening page, click Next.
3. On this page, you'll choose the initial master. Make sure you are
selecting the server that already contains the content. Here is the
explanation from the wizard, fyi: "You must select one target as the
initial master. The first time you start replication, its contents are
replicated to the other targets."
From here on out, you can just follow the wizard to choose the topology,
etc. The most important page for you is the initial master page. Perhaps
it's defaulting to the empty server? I'm guessing the server list is just
alphabatized--I don't think the wizard attempts to look at the content of
the link target.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:e2b%23CjZqFHA.3680@TK2MSFTNGP15.phx.gbl...
Is it possible that you could provide me with the steps to do this
correctly
given that the root server is already set up with links? Perhaps I'm
just
missing something.
Thanks Jill!
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:#P1NyFQqFHA.3304@TK2MSFTNGP11.phx.gbl...
If you are choosing the correct initial master (i.e., your root server)
when
you run the wizard, and data on that server is still moving to
preexisting,
this sounds like something you'll need to work with product support to
solve. Data on the initial server should not move to preexisting because
this content is considered authoritative. Something strange is
happening,
and unfortunately I don't have an answer as to why.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:OGFX1APqFHA.3160@TK2MSFTNGP14.phx.gbl...
The current setup is that the root server also has the DFS links (with
no
replication partners) and contains all of the data.
Once I add a link and set up replication, that is when all my data on
the
root/original server goes into PreExisting. The replication partner
has
no
data on it.
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:OHERr6OqFHA.2432@TK2MSFTNGP10.phx.gbl...
From the behavior you describe, it does sound like you chose the
"empty"
server to be the initial master. This means that your other server
would
move its content to Pre-existing folder so that the server is also
"empty."
But I don't know of a way to definitively confirm which server you
chose
in
the wizard.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Trevor" <null@rottdog.com> wrote in message
news:O2OYtFNqFHA.2240@tk2msftngp13.phx.gbl...
The answer would be no! ;)
Can you point me to directions or tell me what I need to do to do
this?
Thanks,
Trevor
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:ep6LUeMqFHA.1028@TK2MSFTNGP09.phx.gbl...
Can you confirm that you have chosen the server with the existing
content
as
the initial master when you set up replication? The behavior you
describe
should happen on the non-initial masters if they have pre-existing
content.
--
This posting is provided "AS IS" with no warranties, and confers
no
rights.
"Trevor Seward" <null@rottdog.com> wrote in message
news:euqwRN3pFHA.3732@TK2MSFTNGP09.phx.gbl...
What is the sure-fire way to prevent existing data being placed
in
a
PreExisting folder when setting up replication?
I have one server that is currently configured as a domain-based
DFS
root
with 3 DFS links. I have another server that this data needs to
replicate
to which is devoid of any files/folders. I'm finding once I
enable
replication, anything on my original server goes into the
PreExisting
folder
under the replicated link. I'd rather this not happen!
These are Win2K3 with the last Pre-SP1 NTFRS patch.
Thanks,
Trevor
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in