there some voices that had some criticism about the mix between MSSQL and PGSQL, but I would like to say "thank you" to veeam the way they did it. Because if you have this clear cut where ALL the products and components switch from one database to the other, it surely causes some issues because of some bugs that would occur because the new database deployment justs wasn't that sophisticated as the old one.
So when veeam shipped the version where you could choose between the two systems I sticked to the existing MSSQL to then switch to PGSQL some months later with a migration that was purely planned for the DB migration. So if you had no bugs and issues before and had some after the migration, you clearly knew where it came from.
Doing such a migration step by step might be annoying here and there, but if something goes wrong, it does not mess up your whole stack of veeam products...
So when veeam shipped the version where you could choose between the two systems I sticked to the existing MSSQL to then switch to PGSQL some months later with a migration that was purely planned for the DB migration. So if you had no bugs and issues before and had some after the migration, you clearly knew where it came from.
Doing such a migration step by step might be annoying here and there, but if something goes wrong, it does not mess up your whole stack of veeam products...
Statistics: Posted by mcz — Dec 10, 2024 10:25 am
/english-betterindia/media/post_attachments/uploads/2022/05/Sustainable-home-10-1651667432.jpg)
