cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 12

Moving/copying directories to another server

Jump to solution

Hi there,

is there a best practice document on moving/copying directories which are managed by ARM to another file server?

Regards

Marcus

0 Kudos
1 Solution
Level 9

Hi Marcus,

there is a simple way. Please follow the small article below.

How can I move an ARM managed server, share or directory?

The main problem is that the file .id.8man, which exists in every ARM managed directory (System, Hidden) after copying, has a problem with the properties "Creation Date" or "Last Write Access". The ARM software uses these properties to determine whether the file is authentic (original) or a copy. Copies are not allowed and are deleted with each scan.

What does this mean in concrete terms?

There is a configuration switch that controls the described behavior (fileSystem.config.deleteId8ManFiles).

The ARM configuration switch in position "false" does two things:


- The check of the above mentioned properties is not executed; the files are not deleted.
- The files are accessed once for writing (similar to the UNIX 'touch' command)

After a successful ARM resource scan all .id.8man files are authentic again (original). The temporary configuration switch must be deleted again. The action is successfully completed. The procedure also works for subtrees, e.g. shares or directories.


Instructions in telegram style:

1. Copy all data and directories to the new position
2. Set the configuration switch mentioned below temporarily to "false
3. Scan the new resource with ARM.
4. Remove the configuration switch again.
5. Restart the ARM service.
6. Done.

 

Configuration switch profile:

Key: fileSystem.config.deleteId8ManFiles

Position: pnServer.Config.xml

Type: bool (System.Boolean)

Default: not configured / true

Description: Switch that affects whether the Fileserver-Scanner will automatically delete copies of .id.8man files during the scan. Disabling this option is useful when moving a file server.

Example: <fileSystem.config.deleteId8ManFiles type="System.Boolean">false</fileSystem.config.deleteId8ManFiles>

 

Regards

Norbert

View solution in original post

2 Replies
Level 9

Hi Marcus,

there is a simple way. Please follow the small article below.

How can I move an ARM managed server, share or directory?

The main problem is that the file .id.8man, which exists in every ARM managed directory (System, Hidden) after copying, has a problem with the properties "Creation Date" or "Last Write Access". The ARM software uses these properties to determine whether the file is authentic (original) or a copy. Copies are not allowed and are deleted with each scan.

What does this mean in concrete terms?

There is a configuration switch that controls the described behavior (fileSystem.config.deleteId8ManFiles).

The ARM configuration switch in position "false" does two things:


- The check of the above mentioned properties is not executed; the files are not deleted.
- The files are accessed once for writing (similar to the UNIX 'touch' command)

After a successful ARM resource scan all .id.8man files are authentic again (original). The temporary configuration switch must be deleted again. The action is successfully completed. The procedure also works for subtrees, e.g. shares or directories.


Instructions in telegram style:

1. Copy all data and directories to the new position
2. Set the configuration switch mentioned below temporarily to "false
3. Scan the new resource with ARM.
4. Remove the configuration switch again.
5. Restart the ARM service.
6. Done.

 

Configuration switch profile:

Key: fileSystem.config.deleteId8ManFiles

Position: pnServer.Config.xml

Type: bool (System.Boolean)

Default: not configured / true

Description: Switch that affects whether the Fileserver-Scanner will automatically delete copies of .id.8man files during the scan. Disabling this option is useful when moving a file server.

Example: <fileSystem.config.deleteId8ManFiles type="System.Boolean">false</fileSystem.config.deleteId8ManFiles>

 

Regards

Norbert

View solution in original post

Thanks Norbert!

0 Kudos