The simplest way to do this is to directly copy the catalog files (*.vvv), but there is also another solution.
VVV stores data using a relational database (Firebird) so there is a way to create dedicated backup files.
You cannot use directly those backup files, but you must restore them before using them. Those backups are usually much smaller than catalog files, and a backup-and-restore cycle will usually produce a smaller catalog file.
Anyway, you can safely copy a catalog file if VVV is configured in single-user mode (the default), as long as VVV is not running.
On the other hand, if VVV is configured for network usage many users can connect to the same catalog at the same time, and you cannot be sure that nobody is using it. You should stop the database server before copying a catalog file or you could cause corruption in the catalog.
For this reason, if you are using VVV in multi-user configuration, it is recommended to make a backup instead of directly copying the catalog file. Backup is designed in such a way that other users connected to the catalog will not cause problems.
You must be working at the server computer in order to backup or restore a catalog.
Moreover, the database producers recommend using a backup to move a catalog from a computer platform to another, for example from Windows to Linux.
Use the File/Backup menu command to create a backup of the current catalog.
Use the File/Restore menu command to restore a backup to a new catalog.