ArchiverFS - DFS Compatability.

Home | Product Home | Pricing | Download | Documentation | Release Notes | Customers

How to use ArchiverFS with DFS.

ArchiverFS is 100% compatible with all versions of DFS. As ArchiverFS works as the file level and doesn't use any client side software or low level file system drives, it integrates seamlessly with all windows features including DFS.

Targeting the live file system.

When setting up archiving jobs that target a DFS share it is crucial that you consider how ArchiverFS works e.g. everything is based on UNC paths.

- Live locations are added to a job via their UNC path.

- Archive destinations are added to a job via UNC paths.

- When shortcuts are created of any kind, they point to migrated files via their UNC path.

This is why is is really important that you point ArchiverFS at a DFS based file system by using the domain based path and not the local server based path. If you use a local server path in a DFS setup with multiple real servers supporting a domain based DFS root, then when files are migrated they will be recorded as having been moved from the specified single server and not the DFS root path. This can cause multiple undesirable behaviors.

A note about replication.

If you are using a multi-server DFS based file system then you are probably using replication. What's more, if you are doing this then you are probably servicing more than one geographical location with your infrastructure.

When you run your first job you may end up archiving a significant proportion of your file system (depending on the settings you selected)..

If this is the case then don't forget that DFS may have a lot of data to replicate. When running the first archive job on a DFS based file system we recommend you:

- Disable the maintenance job.

- Run the first job.

- Keep an eye on your DFS replication queues.

- Once they have cleared, enable the maintenance job..

A DFS based destination.

If you have multiple geographical locations to service and they all access a single DFS root that is replicated across all locations, then you might consider archiving to a DFS root and replicating it to all of your sites.

While this would require second line storage to be available at all locations, it means that when users access migrated files via stubs\links their request will be served via the local network and not over the WAN. Depending on the speed of the WAN connection and the size of the file this can speed up the retrieval process.

If you decide that DFS based archive storage is right for your organisation then rest assured, ArchiverFS is fully compatible with even multi-replica DFS based archive destinations.

Further information.

If you have any questions please don't hesitate to contact us via Sales@MLtekSoftware.com, we would love to hear from you!

The internet is full of guidse and videos that explain how to set up DFS. In adition to them, we would recomend taking a look at some of Microsoft's official documentation: https://docs.microsoft.com/en-us/windows-server/storage/dfs-namespaces/dfs-overview