> # About DPVM Database Distribution

> 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.

> If fabric distribution is enabled, all changes to the configuration database are stored in the DPVM pending database. These changes include the following tasks:

> - Adding, deleting, or modifying database entries.
> - Activating, deactivating, or deleting the configuration database.
> - Enabling or disabling autolearning.

> These changes are distributed to all switches in a fabric when you commit the changes. You can also discard (abort) the changes at this point.

> Tip See the "Viewing the Pending Database" topic to view the contents of the of the pending database.

> If the DPVM database is available on all switches in the fabric, devices can be moved anywhere and offer the greatest flexibility. To enable database distribution to the neighboring switches, the database should be consistently administered and distributed across all switches in the fabric. The Cisco NX-OS software uses the Cisco Fabric Services (CFS) infrastructure to achieve this requirement (refer to the Cisco MDS 9000 Family NX-OS System Management Configuration Guide).

> Copyright 2010-2015, Cisco Systems, Inc. All rights reserved.