VBM365: Disk cache on the server without additional PostgreSQL – Your feedback?

Hello ​@morgan.munck If I understood well your needs, I think you can mount a folder point  to a diferent drive, and that drive could be  your cache drive for exemplo, what do you think?

Hello @AndrePulia, 
That's right, that's exactly what I'm trying to do (if it's still good practice) so as not to overload the system disk.

​@morgan.munck OK, I see your point now. I’m now Windows engineer, but I think won’t be a problem for Windows or PostgresQL

You can check the vb365 best practice, there is a section dedicated to PostgresSQL database server.

https://bp.veeam.com/vb365/guide/buildconfig/postgresql.html

​@AndrePulia, thank you. It was precisely while trying to define the architecture I wanted that I came across this part of the documentation and questioned my ideas.

​@Chris.Childerhose, I think I'll do that. I hadn't thought of it, but it will indeed force the installer to do what I want.

Thank you both for your valuable advice.

Not a problem.  To me if it is just related to PG and the drive it sits on then installing it first on a second drive you then point to that during the install.  Let us know how it goes.

​@morgan.munck It’s good to know you found a solution through Community! :-)

Hi everyone,
I'm coming back to share what I did to successfully move the PostgreSQL database files. Hope this helps someone!
 

1. Stop the services

• Stop PostgreSQL
• Stop Veeam Proxy
• Stop Veeam Service

2. File Explorer

• Create a new directory (e.g. E:\PostgreSQL\15\data)
• Copy all files from the old data folder to the new one
• Rename the old data folder to data_old (as a backup)
• Grant Full Control to Network Service on the new PostgreSQL folder
• Delete the postmaster.pid file

3. Registry (regedit)

• In HKLM\SOFTWARE\PostgreSQL\Installations\postgresql-x64-15 → update Data Directory
• In HKLM\SOFTWARE\PostgreSQL\Services\postgresql-x64-15 → update Data Directory
• In HKLM\SYSTEM\ControlSet001\services\postgresql-x64-15 → update ImagePath
• In HKLM\SYSTEM\ControlSet002\services\postgresql-x64-15 → update ImagePath

4. Edit the script

• Edit C:\Program Files\PostgreSQL\15\pg_env.bat and update the PGDATA value to reflect the new path

5. Restart the services

• Start PostgreSQL
• Start Veeam Proxy
• Start Veeam Service

Feel free to ask if you have any questions! 😊

Thanks for coming back and sharing the steps you took as this great for others to follow.  Very easy and concise.

Thank you for sharing the steps to move your PSSQL DB ​@morgan.munck so the Community can benefit. Well done! 👍🏻