Discussion:
Replication of this type of reparse point is not supported by the
(too old to reply)
Alex Kukin
2006-07-26 21:47:02 UTC
Permalink
My DFS Replciation seems to be working, but I get this error message:
"Replication of this type of reparse point is not supported by the DFS
Replication service" on the primary server. Out of 37GB of data 3.7GB did not
copy over (that's about 100 folders). I could not find any information on why
this occurs and how to fix it. Any ideas?
Thanks!
Ned Pyle [MSFT]
2006-07-26 22:37:39 UTC
Permalink
Do you have a reparse or junction or mount point within your folder
structure that's being replicated? Does the event have any further info?

If it doesn't tell us, what is the top level folder which refuses to
replicate the 100 subfolders? Knowing that path we can use FSUTIL (built-in
tool) to query that top-level folder and find out interesting things about
it.

For example when you do it against a SYSVOL you will see:

=====================================================
C:\>FSUTIL REPARSEPOINT query c:\windows\sysvol\sysvol\fabrikam.com
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 56
Print Name offset: 58
Print Name Length: 48
Substitute Name: \??\C:\WINDOWS\SYSVOL\domain
Print Name: C:\WINDOWS\SYSVOL\domain

Reparse Data Length: 0x00000074
Reparse Data:
0000: 00 00 38 00 3a 00 30 00 5c 00 3f 00 3f 00 5c 00 ..8.:.0.\.?.?.\.
0010: 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 4f 00 C.:.\.W.I.N.D.O.
0020: 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 4f 00 W.S.\.S.Y.S.V.O.
0030: 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 6e 00 L.\.d.o.m.a.i.n.
0040: 00 00 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 ..C.:.\.W.I.N.D.
0050: 4f 00 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 O.W.S.\.S.Y.S.V.
0060: 4f 00 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 O.L.\.d.o.m.a.i.
0070: 6e 00 00 00 n...
=====================================================

DFSR (and FRS as well) cannot ordinarily replicate mount points or reparse
points that exist beneath the types of points that DFS puts in. So any type
of reparse point that exists in a replicated structure is going to go
kaboom. More info:

http://technet2.microsoft.com/WindowsServer/en/library/1aa249c0-40f3-4974-b67f-e650b602415e1033.mspx?mfr=true

Files not replicated. DFS Replication does not replicate the following types
of files:

• NTFS mounted drives within the local path of the replicated folder.
(However, the local path of a replicated folder can be at or under a mounted
drive.)
• Files encrypted by using encrypting file system (EFS).
• Any reparse points except those associated with DFS Namespaces. If a file
has a reparse point used for Hierarchical Storage Management (HSM) or Single
Instance Store (SIS), DFS Replication replicates the underlying file but not
the reparse point.
• Files on which the temporary attribute has been set.
• Files with case-sensitive names created by using a UNIX-compatible
application and saved to a Network File System (NFS) shared folder. (NTFS
supports the Portable Operating System Interface [POSIX] standard, which
provides the ability to create two files that have the same name but
different capitalization.) For example, if a user creates two files,
FILE.doc and File.doc, on an NFS shared folder, DFS Replication will
replicate the first but not the second.
--
Ned Pyle
Microsoft Enterprise Platforms Support

All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
"Replication of this type of reparse point is not supported by the DFS
Replication service" on the primary server. Out of 37GB of data 3.7GB did not
copy over (that's about 100 folders). I could not find any information on why
this occurs and how to fix it. Any ideas?
Thanks!
Alex Kukin
2006-07-27 19:16:01 UTC
Permalink
Here are the exact error messages. Also, an idea I had was: I am hosting my
namespace in the same server/same folder - could this cause this to happen?

Thanks,

Errors:

Replication of this type of reparse point is not supported by the DFS
Replication service.
Affected replicated folders: Public
Description: The DFS Replication service encountered an unsupported
reparse point in replicated folder Public with local path D:\Public. This
reparse point (Public) will not be replicated because the replication of this
type of reparse point is not supported by the DFS Replication service. Event
ID: 4406
Last occurred: Wednesday, July 26, 2006 at 5:59:38 PM (GMT-5:00)
Suggested action: Replication of this type of reparse point is not
supported by the DFS Replication service.

One or more replicated folders have sharing violations.
Affected replicated folders: Public
Description: Due to ongoing sharing violations, DFS Replication cannot
replicate files in the replicated folders listed above. This problem is
affecting 22 files in 1 replicated folders. Event ID: 4302
Last occurred: Thursday, July 27, 2006 at 3:12:42 PM (GMT-5:00)
Suggested action: Verify that the files you want to replicate are closed
and have no open handles to them. For information about troubleshooting
sharing violations, see The Microsoft Web Site.
Post by Ned Pyle [MSFT]
Do you have a reparse or junction or mount point within your folder
structure that's being replicated? Does the event have any further info?
If it doesn't tell us, what is the top level folder which refuses to
replicate the 100 subfolders? Knowing that path we can use FSUTIL (built-in
tool) to query that top-level folder and find out interesting things about
it.
=====================================================
C:\>FSUTIL REPARSEPOINT query c:\windows\sysvol\sysvol\fabrikam.com
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 56
Print Name offset: 58
Print Name Length: 48
Substitute Name: \??\C:\WINDOWS\SYSVOL\domain
Print Name: C:\WINDOWS\SYSVOL\domain
Reparse Data Length: 0x00000074
0000: 00 00 38 00 3a 00 30 00 5c 00 3f 00 3f 00 5c 00 ..8.:.0.\.?.?.\.
0010: 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 4f 00 C.:.\.W.I.N.D.O.
0020: 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 4f 00 W.S.\.S.Y.S.V.O.
0030: 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 6e 00 L.\.d.o.m.a.i.n.
0040: 00 00 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 ..C.:.\.W.I.N.D.
0050: 4f 00 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 O.W.S.\.S.Y.S.V.
0060: 4f 00 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 O.L.\.d.o.m.a.i.
0070: 6e 00 00 00 n...
=====================================================
DFSR (and FRS as well) cannot ordinarily replicate mount points or reparse
points that exist beneath the types of points that DFS puts in. So any type
of reparse point that exists in a replicated structure is going to go
http://technet2.microsoft.com/WindowsServer/en/library/1aa249c0-40f3-4974-b67f-e650b602415e1033.mspx?mfr=true
Files not replicated. DFS Replication does not replicate the following types
• NTFS mounted drives within the local path of the replicated folder.
(However, the local path of a replicated folder can be at or under a mounted
drive.)
• Files encrypted by using encrypting file system (EFS).
• Any reparse points except those associated with DFS Namespaces. If a file
has a reparse point used for Hierarchical Storage Management (HSM) or Single
Instance Store (SIS), DFS Replication replicates the underlying file but not
the reparse point.
• Files on which the temporary attribute has been set.
• Files with case-sensitive names created by using a UNIX-compatible
application and saved to a Network File System (NFS) shared folder. (NTFS
supports the Portable Operating System Interface [POSIX] standard, which
provides the ability to create two files that have the same name but
different capitalization.) For example, if a user creates two files,
FILE.doc and File.doc, on an NFS shared folder, DFS Replication will
replicate the first but not the second.
--
Ned Pyle
Microsoft Enterprise Platforms Support
All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
"Replication of this type of reparse point is not supported by the DFS
Replication service" on the primary server. Out of 37GB of data 3.7GB did not
copy over (that's about 100 folders). I could not find any information on why
this occurs and how to fix it. Any ideas?
Thanks!
Ned Pyle [MSFT]
2006-07-27 21:44:28 UTC
Permalink
Is your namespace being hosted *under* the folder that's being replicated?
So like:

c:\foo <<< the replicated folder
c:\foo\bar <<< the DFS namespace root folder
c:\foo\bar\stuff <<< files in here are the ones not replicated

?

I'm doing a repro here as well to see what I can see.
--
Ned Pyle
Microsoft Enterprise Platforms Support

All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
Here are the exact error messages. Also, an idea I had was: I am hosting my
namespace in the same server/same folder - could this cause this to happen?
Thanks,
Replication of this type of reparse point is not supported by the DFS
Replication service.
Affected replicated folders: Public
Description: The DFS Replication service encountered an unsupported
reparse point in replicated folder Public with local path D:\Public. This
reparse point (Public) will not be replicated because the replication of this
type of reparse point is not supported by the DFS Replication service. Event
ID: 4406
Last occurred: Wednesday, July 26, 2006 at 5:59:38 PM (GMT-5:00)
Suggested action: Replication of this type of reparse point is not
supported by the DFS Replication service.
One or more replicated folders have sharing violations.
Affected replicated folders: Public
Description: Due to ongoing sharing violations, DFS Replication cannot
replicate files in the replicated folders listed above. This problem is
affecting 22 files in 1 replicated folders. Event ID: 4302
Last occurred: Thursday, July 27, 2006 at 3:12:42 PM (GMT-5:00)
Suggested action: Verify that the files you want to replicate are closed
and have no open handles to them. For information about troubleshooting
sharing violations, see The Microsoft Web Site.
Post by Ned Pyle [MSFT]
Do you have a reparse or junction or mount point within your folder
structure that's being replicated? Does the event have any further info?
If it doesn't tell us, what is the top level folder which refuses to
replicate the 100 subfolders? Knowing that path we can use FSUTIL (built-in
tool) to query that top-level folder and find out interesting things about
it.
=====================================================
C:\>FSUTIL REPARSEPOINT query c:\windows\sysvol\sysvol\fabrikam.com
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 56
Print Name offset: 58
Print Name Length: 48
Substitute Name: \??\C:\WINDOWS\SYSVOL\domain
Print Name: C:\WINDOWS\SYSVOL\domain
Reparse Data Length: 0x00000074
0000: 00 00 38 00 3a 00 30 00 5c 00 3f 00 3f 00 5c 00 ..8.:.0.\.?.?.\.
0010: 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 4f 00 C.:.\.W.I.N.D.O.
0020: 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 4f 00 W.S.\.S.Y.S.V.O.
0030: 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 6e 00 L.\.d.o.m.a.i.n.
0040: 00 00 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 ..C.:.\.W.I.N.D.
0050: 4f 00 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 O.W.S.\.S.Y.S.V.
0060: 4f 00 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 O.L.\.d.o.m.a.i.
0070: 6e 00 00 00 n...
=====================================================
DFSR (and FRS as well) cannot ordinarily replicate mount points or reparse
points that exist beneath the types of points that DFS puts in. So any type
of reparse point that exists in a replicated structure is going to go
http://technet2.microsoft.com/WindowsServer/en/library/1aa249c0-40f3-4974-b67f-e650b602415e1033.mspx?mfr=true
Files not replicated. DFS Replication does not replicate the following types
• NTFS mounted drives within the local path of the replicated folder.
(However, the local path of a replicated folder can be at or under a mounted
drive.)
• Files encrypted by using encrypting file system (EFS).
• Any reparse points except those associated with DFS Namespaces. If a file
has a reparse point used for Hierarchical Storage Management (HSM) or Single
Instance Store (SIS), DFS Replication replicates the underlying file but not
the reparse point.
• Files on which the temporary attribute has been set.
• Files with case-sensitive names created by using a UNIX-compatible
application and saved to a Network File System (NFS) shared folder. (NTFS
supports the Portable Operating System Interface [POSIX] standard, which
provides the ability to create two files that have the same name but
different capitalization.) For example, if a user creates two files,
FILE.doc and File.doc, on an NFS shared folder, DFS Replication will
replicate the first but not the second.
--
Ned Pyle
Microsoft Enterprise Platforms Support
All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
"Replication of this type of reparse point is not supported by the DFS
Replication service" on the primary server. Out of 37GB of data 3.7GB
did
not
copy over (that's about 100 folders). I could not find any information
on
why
this occurs and how to fix it. Any ideas?
Thanks!
Alex Kukin
2006-07-28 13:34:02 UTC
Permalink
Correct.

Also, as I modified the namespace to be hosted under a different folder, I
get the error: DFS Replication service stopped replication. (see below). This
is for a larger "Public" folder on the file server (aprx 30GB). What is
interesting is that smaller "Users" folder (3 GB) replicates withOUT any
errors from the same server.

Any ideas are appreciated.

Thanks,

Error:
DFS Replication service stopped replication on replicated folder Public.
Affected replicated folders: Public
Description: The DFS Replication service stopped replication on replicated
folder Public at local path C:\DFSRoots\RockvilleFiles\Public due to Erorr
ID: 87 (The parameter is incorrect.). Event ID: 4004
Last occurred: Friday, July 28, 2006 at 7:10:58 AM (GMT-5:00)
Suggested action: For information about troubleshooting this problem, see
The Microsoft Web Site.
Post by Ned Pyle [MSFT]
Is your namespace being hosted *under* the folder that's being replicated?
c:\foo <<< the replicated folder
c:\foo\bar <<< the DFS namespace root folder
c:\foo\bar\stuff <<< files in here are the ones not replicated
?
I'm doing a repro here as well to see what I can see.
--
Ned Pyle
Microsoft Enterprise Platforms Support
All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
Here are the exact error messages. Also, an idea I had was: I am hosting my
namespace in the same server/same folder - could this cause this to happen?
Thanks,
Replication of this type of reparse point is not supported by the DFS
Replication service.
Affected replicated folders: Public
Description: The DFS Replication service encountered an unsupported
reparse point in replicated folder Public with local path D:\Public. This
reparse point (Public) will not be replicated because the replication of this
type of reparse point is not supported by the DFS Replication service. Event
ID: 4406
Last occurred: Wednesday, July 26, 2006 at 5:59:38 PM (GMT-5:00)
Suggested action: Replication of this type of reparse point is not
supported by the DFS Replication service.
One or more replicated folders have sharing violations.
Affected replicated folders: Public
Description: Due to ongoing sharing violations, DFS Replication cannot
replicate files in the replicated folders listed above. This problem is
affecting 22 files in 1 replicated folders. Event ID: 4302
Last occurred: Thursday, July 27, 2006 at 3:12:42 PM (GMT-5:00)
Suggested action: Verify that the files you want to replicate are closed
and have no open handles to them. For information about troubleshooting
sharing violations, see The Microsoft Web Site.
Post by Ned Pyle [MSFT]
Do you have a reparse or junction or mount point within your folder
structure that's being replicated? Does the event have any further info?
If it doesn't tell us, what is the top level folder which refuses to
replicate the 100 subfolders? Knowing that path we can use FSUTIL (built-in
tool) to query that top-level folder and find out interesting things about
it.
=====================================================
C:\>FSUTIL REPARSEPOINT query c:\windows\sysvol\sysvol\fabrikam.com
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 56
Print Name offset: 58
Print Name Length: 48
Substitute Name: \??\C:\WINDOWS\SYSVOL\domain
Print Name: C:\WINDOWS\SYSVOL\domain
Reparse Data Length: 0x00000074
0000: 00 00 38 00 3a 00 30 00 5c 00 3f 00 3f 00 5c 00 ..8.:.0.\.?.?.\.
0010: 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 4f 00 C.:.\.W.I.N.D.O.
0020: 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 4f 00 W.S.\.S.Y.S.V.O.
0030: 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 6e 00 L.\.d.o.m.a.i.n.
0040: 00 00 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 ..C.:.\.W.I.N.D.
0050: 4f 00 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 O.W.S.\.S.Y.S.V.
0060: 4f 00 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 O.L.\.d.o.m.a.i.
0070: 6e 00 00 00 n...
=====================================================
DFSR (and FRS as well) cannot ordinarily replicate mount points or reparse
points that exist beneath the types of points that DFS puts in. So any type
of reparse point that exists in a replicated structure is going to go
http://technet2.microsoft.com/WindowsServer/en/library/1aa249c0-40f3-4974-b67f-e650b602415e1033.mspx?mfr=true
Files not replicated. DFS Replication does not replicate the following types
• NTFS mounted drives within the local path of the replicated folder.
(However, the local path of a replicated folder can be at or under a mounted
drive.)
• Files encrypted by using encrypting file system (EFS).
• Any reparse points except those associated with DFS Namespaces. If a file
has a reparse point used for Hierarchical Storage Management (HSM) or Single
Instance Store (SIS), DFS Replication replicates the underlying file but not
the reparse point.
• Files on which the temporary attribute has been set.
• Files with case-sensitive names created by using a UNIX-compatible
application and saved to a Network File System (NFS) shared folder. (NTFS
supports the Portable Operating System Interface [POSIX] standard, which
provides the ability to create two files that have the same name but
different capitalization.) For example, if a user creates two files,
FILE.doc and File.doc, on an NFS shared folder, DFS Replication will
replicate the first but not the second.
--
Ned Pyle
Microsoft Enterprise Platforms Support
All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
"Replication of this type of reparse point is not supported by the DFS
Replication service" on the primary server. Out of 37GB of data 3.7GB
did
not
copy over (that's about 100 folders). I could not find any information
on
why
this occurs and how to fix it. Any ideas?
Thanks!
Ned Pyle [MSFT]
2006-07-28 15:17:15 UTC
Permalink
Interesting. I cannot repro any of what you're seeing, but I'm not 100% sure
that I'm reproducing what you have. Mine doesn't break...

I recommend you open a new case with PSS. When you have done so, make sure
your case owner sends an email to "nedpyle" so I can track how things are
going and offer assistance as needed.
--
Ned Pyle
Microsoft Enterprise Platforms Support

All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
Correct.
Also, as I modified the namespace to be hosted under a different folder, I
get the error: DFS Replication service stopped replication. (see below). This
is for a larger "Public" folder on the file server (aprx 30GB). What is
interesting is that smaller "Users" folder (3 GB) replicates withOUT any
errors from the same server.
Any ideas are appreciated.
Thanks,
DFS Replication service stopped replication on replicated folder Public.
Affected replicated folders: Public
Description: The DFS Replication service stopped replication on replicated
folder Public at local path C:\DFSRoots\RockvilleFiles\Public due to Erorr
ID: 87 (The parameter is incorrect.). Event ID: 4004
Last occurred: Friday, July 28, 2006 at 7:10:58 AM (GMT-5:00)
Suggested action: For information about troubleshooting this problem, see
The Microsoft Web Site.
Post by Ned Pyle [MSFT]
Is your namespace being hosted *under* the folder that's being replicated?
c:\foo <<< the replicated folder
c:\foo\bar <<< the DFS namespace root folder
c:\foo\bar\stuff <<< files in here are the ones not replicated
?
I'm doing a repro here as well to see what I can see.
--
Ned Pyle
Microsoft Enterprise Platforms Support
All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
Here are the exact error messages. Also, an idea I had was: I am
hosting
my
namespace in the same server/same folder - could this cause this to happen?
Thanks,
Replication of this type of reparse point is not supported by the DFS
Replication service.
Affected replicated folders: Public
Description: The DFS Replication service encountered an unsupported
reparse point in replicated folder Public with local path D:\Public. This
reparse point (Public) will not be replicated because the replication
of
this
type of reparse point is not supported by the DFS Replication service. Event
ID: 4406
Last occurred: Wednesday, July 26, 2006 at 5:59:38 PM (GMT-5:00)
Suggested action: Replication of this type of reparse point is not
supported by the DFS Replication service.
One or more replicated folders have sharing violations.
Affected replicated folders: Public
Description: Due to ongoing sharing violations, DFS Replication cannot
replicate files in the replicated folders listed above. This problem is
affecting 22 files in 1 replicated folders. Event ID: 4302
Last occurred: Thursday, July 27, 2006 at 3:12:42 PM (GMT-5:00)
Suggested action: Verify that the files you want to replicate are closed
and have no open handles to them. For information about troubleshooting
sharing violations, see The Microsoft Web Site.
Post by Ned Pyle [MSFT]
Do you have a reparse or junction or mount point within your folder
structure that's being replicated? Does the event have any further info?
If it doesn't tell us, what is the top level folder which refuses to
replicate the 100 subfolders? Knowing that path we can use FSUTIL (built-in
tool) to query that top-level folder and find out interesting things about
it.
=====================================================
C:\>FSUTIL REPARSEPOINT query c:\windows\sysvol\sysvol\fabrikam.com
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 56
Print Name offset: 58
Print Name Length: 48
Substitute Name: \??\C:\WINDOWS\SYSVOL\domain
Print Name: C:\WINDOWS\SYSVOL\domain
Reparse Data Length: 0x00000074
0000: 00 00 38 00 3a 00 30 00 5c 00 3f 00 3f 00 5c 00
..8.:.0.\.?.?.\.
0010: 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 4f 00
C.:.\.W.I.N.D.O.
0020: 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 4f 00
W.S.\.S.Y.S.V.O.
0030: 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00 6e 00
L.\.d.o.m.a.i.n.
0040: 00 00 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00
..C.:.\.W.I.N.D.
0050: 4f 00 57 00 53 00 5c 00 53 00 59 00 53 00 56 00
O.W.S.\.S.Y.S.V.
0060: 4f 00 4c 00 5c 00 64 00 6f 00 6d 00 61 00 69 00
O.L.\.d.o.m.a.i.
0070: 6e 00 00 00 n...
=====================================================
DFSR (and FRS as well) cannot ordinarily replicate mount points or reparse
points that exist beneath the types of points that DFS puts in. So any type
of reparse point that exists in a replicated structure is going to go
http://technet2.microsoft.com/WindowsServer/en/library/1aa249c0-40f3-4974-b67f-e650b602415e1033.mspx?mfr=true
Files not replicated. DFS Replication does not replicate the following types
• NTFS mounted drives within the local path of the replicated folder.
(However, the local path of a replicated folder can be at or under a mounted
drive.)
• Files encrypted by using encrypting file system (EFS).
• Any reparse points except those associated with DFS Namespaces. If a file
has a reparse point used for Hierarchical Storage Management (HSM) or Single
Instance Store (SIS), DFS Replication replicates the underlying file
but
not
the reparse point.
• Files on which the temporary attribute has been set.
• Files with case-sensitive names created by using a UNIX-compatible
application and saved to a Network File System (NFS) shared folder. (NTFS
supports the Portable Operating System Interface [POSIX] standard, which
provides the ability to create two files that have the same name but
different capitalization.) For example, if a user creates two files,
FILE.doc and File.doc, on an NFS shared folder, DFS Replication will
replicate the first but not the second.
--
Ned Pyle
Microsoft Enterprise Platforms Support
All postings on this newsgroup are provided "AS IS" with no
warranties,
and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.
Post by Alex Kukin
"Replication of this type of reparse point is not supported by the DFS
Replication service" on the primary server. Out of 37GB of data 3.7GB
did
not
copy over (that's about 100 folders). I could not find any information
on
why
this occurs and how to fix it. Any ideas?
Thanks!
Continue reading on narkive:
Loading...