In some situations/scenarios it is absolutely necessary to move the Veeam Configuration Database (PostgreSQL) to another hard disk of the Backup & Replication Server (e.g. if the C: partition is too small). After installation, the Postgres databases are located under: C:\Program Files\PostgreSQL\xx\data (Unfortunately, the path cannot be changed during the Veeam installation).
Moving the PostgreSQL database is actually quite simple and can be done with pgAdmin. Before you start the migration, you should create a VMware snapshot and/or a Veeam Configuration Backup.
Download pgAdmin from their website (pgAdmin – PostgreSQL Tools) and install it on the Veeam Backup & Replication Server.
Add a second hard disk to the VBR server and create a folder for the database in it.
Because the PostgreSQL service runs under the “Network service” account, the folder must be correctly authorized. To do this, add the “Network service” user with “Full control” to the folder under “Security”.
Stop the Veeam services on the VBR server.
Open pgAdmin. If a postgres password was set during the installation, this must be entered. Otherwise the default password is “postgres”.
Inside pgAdmin you have to browse the databases and select “VeeamBackup”. Under “Properties” you can see the defined locations under tablespace “pg_default” (this is the default location).
A new storage location must now be created. To do this, browse the “Tablespaces” and create a new storage location via “right-click”, ‘create’, “Tablespace…”.
Specify a name for the tablespace.
Specify the created path for the Veeam configuration database under “Location” and klick “Save”.
Now you see the new Tablespace.
To assign the new tablespace to the Veeam database, go to the database settings. Right-click on the “VeeamBackup” database and select “Properties”.
Under the “Definition” tab, select the new tablespace “VeeamConfigurationDatabase” via the drop-down menu and confirm with “Save”.
Now the saving process takes some time and the tablespace should be adjusted afterwards.
If you now look into the folder created on the 2nd hard disk, the database files are now located here. You do not have to delete old files (if you search for them in the old folder, you will find them, but they are a link to the new path. So do not delete them!)
Now the Veeam services can be started again (or reboot server) and pgAdmin can be closed.
The change of the database path is now complete and Veeam can be used normally again. Open the Veeam Console and test if you can log in.
If a VMware snapshot has been created, remember that it must be deleted.