The Green Meadow

1. Necessity of the “Green Meadow”

If the authorizations of a share are to be migrated to a server, then there are two possibilities. Either one migrates within the share or one creates a target share parallel, which one designs and which one finally names the source share. The first variant is possible with migRaven, contains however old and new authorizations and requires rework. The second variant with the structure of a parallel share is only sensible. Then which name should one give to the parallel share? Should the source share be renamed anyway, one simply give the target share the new name. The name should mostly be maintained, i.e. the target share should retain the same name like the source share. Two same release names on a server are however not possible. Thus the new share gets first any name, e.g. “Green Meadow”. After the migration, i.e. after creating the authorizations and after copying the data, the old share must be renamed and the new share can maintain the original name of the old share.

2. Can I subsequently 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 does the group mainly assign authorizations and what type of authorizations. Change in directory name discards this concept.

2. If the authorization groups created by migRaven are used afterwards by 8MAN, then not only the group names are adhered, else 8MAN does not accept these groups. Also a parameter of the authorization group, the “description”, which is accessible in AD, includes server-, release- and directory names. Also these must be correct.

-> Also a clear NO. The release- and directory names should not be subsequently changed.

3. Use the green meadow in migRaven

The problem exists only while migrating per 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 source is outside the windows server and thus the target share can get the same final name.

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 n empty, but fully authorized duplicate of the directory tree.

The “Green Meadow” is available so that the complete process can be carried out 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 number of files in the directory tree, writing the ACLs can take days!


Leave a Reply

Translate »