DPVM can use CFS to distribute the database to all switches in the fabric to allow devices to move anywhere and keep the same VSAN membership.
You should enable CFS distribution on all switches in the fabric.
Using the CFS infrastructure, each DPVM server learns the DPVM database from each of its neighboring switches during the ISL bring-up process. If you change the database locally, the DPVM server notifies its neighboring switches, and that database is updated by all switches in the fabric.
When you enable CFS distribution for DPVM, the DPVM configuration database is copied into the DPVM pending database. All changes to the DPVM configuration are now stored in the DPVM pending database and the feature is locked (that is, no other switch can make changes to the DPVM database until you commit the changes or discard the changes and free the CFS lock).
The DPVM pending database includes the following changes:
Adding, deleting, or modifying database entries.
Activating, deactivating, or deleting the configuration database.
Enabling or disabling autolearning.
CFS distributes these changes to all switches in a fabric when you commit the changes. You can also discard (abort) the changes at this point.