Migration from Original Plugin

Migration from the original plugin

The new identity is dvm; the original is dwdvm. Removing the original without a verified backup can delete settings and traffic history.

1. Stop the original service. Back up /boot/config/plugins/dwdvm outside its plugin directory.
2. Copy the newest stopped vnstat.db from its effective DatabaseDir, normally /var/lib/vnstat. Preserve custom /etc/vnstat files. Verify the copies.
3. Remove the original plugin. Its uninstall routine deletes its settings, /etc/vnstat, and the default runtime database directory.
4. Install the chosen available channel's manifest above. Leave its service disabled.
5. Restore dwdvm.cfg as /boot/config/plugins/dvm/dvm.cfg, with SERVICE="disable" until restoration is complete.
6. Restore supported .conf/.sh files to /etc/vnstat and /boot/config/plugins/dvm/vnstat. Do not restore dwdvm.cfg into these directories. Update old plugin paths in custom scripts.
7. Restore the newest database into the restored configuration's DatabaseDir and retain an independent backup. It may also be copied to /boot/config/plugins/dvm/vnstat.db; a custom path needs a successful new backup before its path/checksum metadata is established.
8. Set restored files to root ownership, database/configuration files to 644, directories to 755, and the two action scripts to 755.
9. Enable the service. Verify interfaces, history, thresholds, actions, and persistence through a normal reboot.

Keep the independent backup until migration is verified. Do not install both identities together.

This identity migration is different from changing Stable/Development channels of an existing dvm installation. For channel changes, use the in-place channel procedure instead.