INFO: Site Server Content Deployment (SSCD) Recommendations (294848)


The information in this article applies to:

  • Microsoft Site Server 3.0
This article was previously published under Q294848

SUMMARY

This article provides recommendations for using Site Server Content Deployment (SSCD), which is also known as Content Replication Services (CRS).

Although the Replicate ACLs with the files option (/ACLs from a command prompt) is allowed, it is not recommended because the large amount of overhead and system resources that are involved when you replicate files that contain access control lists (ACLs) may prevent some ACLs from being replicated. You should only consider this option when you replicate a small number of files in which the ACLs are for local accounts or groups or are within the member domain.

MORE INFORMATION

Below are recommendations that can be used to help minimize overhead and system resources when you replicate content.

Recommendation 1 is the best method for replicating content when the source and destination contain the same structure and individual files do not require ACLs to be different than their parent folder. Recommendations 2 and 3 have more overhead and require more resources.

NOTE: When you use automatic mode replications, be aware that ACL changes alone do not cause a replication event. This is because automatic mode uses NT Directory Change Notifications (DCN) to determine the need for a resynchronization of content. DCNs occur when the Modified Date/Time attribute of the file is changed, and ACL changes have no effect on this field. If you want changes in ACLs to be immediately applied, you can use utilities such as the Touch.exe utility in the NT Resource Kit to change the modified date field and cause the file or files to be replicated.

Recommendation 1
=================
Create one publishing project (project A) to replicate files only. By default, Microsoft Windows NT and Microsoft Windows 2000 use folder inheritance for ACLs. When a source folder's ACL has changed, a source folder is added or removed, the source folder structure has changed, or this is the first time the content is replicated to the destination, use Recommendation 2.

Before you start the replication, follow these steps:
  1. In the project's Properties dialog box, on the Security tab, select None. You can also type /noacls at a command prompt.
  2. Make sure the destination already contains the same folder structure and that ACLs on the destination folders are already set.
When you start project A, files are replicated to the destination folders. The replicated files inherit the ACLs of the folder they are replicated to.

Recommendation 2
=================
Create two publishing projects (projects A and B). Project A replicates the files only and project B replicates the folder ACLs. Project B should only be executed when a source folder's ACL has changed, a source folder is added or removed, the source folder structure has changed, or this is the first time the content is replicated to the destination.

If the destination already exists and contains the same folder structure as the source, use Recommendation 1. If any of the files in the source have different ACLs than their parent folder, use Recommendation 3.

Before you start the replication, follow these steps:
  1. In project A, open the Properties dialog box, click the Security tab, and select None. You can also type /noacls at a command prompt.
  2. In project B, open the Properties dialog box, click the Security tab, and select Replicate directory ACLs only and apply to files. You can also type /dirsonly and /permit at a command prompt.
Start project A first. When project A completes successfully, start project B. When project B completes successfully, all files contain the ACLs of their parent folders.

Recommendation 3
=================
Create two publishing projects (project A and B). Project A replicates the files only and project B replicates the ACLs for all files. This recommendation should only be used in cases in which different files have different ACLs. If the source and destination have the same the directory structure and no files require unique ACLs, you should use Recommendation 1.

Before you start the replication, follow these steps:

  1. In project A, open the Properties dialog box, click the Security tab, and select None. You can also type /noacls at a command prompt.
  2. In project B, open the Properties dialog box, click the Security tab, and select Replicate ACLs only. You can also type /aclsonly at a command prompt.
Start project A first. When project A completes successfully, start project B. When project B completes successfully, all files contain the ACLs of their source file.
Modification Type:MajorLast Reviewed:10/17/2001
Keywords:kbinfo KB294848
©2002 Microsoft Corporation. All rights reserved.