Using Filters

Use VirtaMove filters to exclude specific paths and registry files from a migration.

You can do this:

when you create a container
during tether, or
when you dissolve, to make sure that specific paths are not transferred to the underlying operating system; for example, to exclude VirtaMove executables

Define filters by:

editing UserDefinedFilter and adding nodes where appropriate, or
creating filters based on the environments or applications you want to migrate

You create filters by adding a Custom filter entity to the FilterList.xml file and copying the custom filter into the <Installation Directory>\Filters\Custom folder. The syntax should follow existing filters.

Filters

<Installation Directory>\Filters\VirtaMoveDissolveExcludes.xml	Contains path and registry filters that will automatically be copied to every container that is created. Useful for excluding OS-dependent information from a migration.
<Installation Directory>\Filters\VirtaMoveFilter.xml	This filter excludes all VirtaMove-related products. Useful for excluding VirtaMove Source Agent files.
<Installation Directory>\Filters\FilterList.xml	Contains a list of all the filters in a container.
<Installation Directory>\Filters\Custom\DotNet.xml	A custom filter used to exclude .NET files and registry keys, so that they maintain their integrity on the underlying operating system.
<Installation Directory>\Filters\Custom\LogAndTempFilter.xml	A custom filter used to exclude all log and temporary files, which are usually huge and do not need to be migrated to the new server. Excluding these files speeds up the pre-populate and COTF process.
<Installation Directory>\Filters\Custom\UserDefinedFilter.xml	Stores user-defined filters, which will automatically be used by all filters.