1. Necessity of the "Green Meadow"
If the authorizations of a share are being migrated to a server, then there are two possibilities. Either one migrates within the share or one creates a target share in parallel, which one designs and one finally names the source share. The first variant is possible with migRaven, however, requires old and new authorizations and requires rework. The second variant with the structure of a parallel share is only sensitive. Then which name should give one to the parallel share? Should the source share be renamed anyway, one simply give the target share the new name. The name should be maintained, ie the target share should retain the same name as the source share. Two same release names on a server are not possible. Thus the new share gets first name, eg "Green Meadow". After the migration, ie after creating the authorizations and copying the data, the old share must be maintained.
2. Can I change the release and directory names?
1. As it is evident in the group configuration, the optional release name and the directory name are the mandatory components of the name for the authorization group. These meaningful group names indicate where the group mainly assign authorizations and what types of authorizations. Change in directory name discards this concept.
2. If the authorization group created by migRaven 8MAN, then not only the group names are adhered, else 8MAN does not accept these groups. So a parameter of the authorization group, the "description", which is accessible in AD, includes server, release and directory names. So this must be correct.
-> So a clear NO. The release and directory names should not be changed.
3. Use the green meadow in migRaven
The problem exists only while migrating via scan, as here source and target are on the same server. In case of bulk and novell migration, the problem does not exist, because the same name is used.
The release names for source and target path are already specified while creating the project. For the target path, we specify "Green Meadow".
Through the menu option "Deploy ACL", a "Green Meadow" is created with directory tree and the new authorizations. The "Green Meadow" is empty, but fully authorized duplicate of the directory tree.
The "Green Meadow" is available as relaxed as possible. This means: There are no timely dependencies between the work steps and restrictions for the users.
Please note that because it depends on the file number in the directory tree, writing the ACLs can take days!