MSDP /Storage/databases Symbolic Link Anyone?
I have noticed a very bad piece of programming in the PureDisk/MSDP code, the inability to move the databases filesystem/folder/partition from one mount point to another. I reference this post.
The dedupe guide warns against bad planning (agree muchly with this) but sometimes certain things are just out of your control, for instance, we were under severe pressure to get a system working (temporarily) for a customer, with limited time and limited resources we had to place the /Storage/databases under one LUN with the /Storage partition, eventually this started resulting in bad performance due to .tlogs growing into the hundreds of millions, I had noticed we needed to move the databases to another LUN/Disk/Location for improved performance, UNFORTUNATELY we hit a brick wall with lots of advice and posts on HOW NOT to move a databases directory, so as they say in Sunny South Africa, a boer maak a plan (A farmer, makes a plan). So we did that, we got hold of some super fast disk and created a symbolic link to the new location, moved all the files into the new location. Started the Netbackup services and voila, it works better than expected. This is but a temporary solution and I am sure it is frowned upon and wholly unsupported by Symantec BUT, it works and i just thought i would share my experiences with this.
Symantec, would you care to elaborate on such poor coding/methodology behind this? Your MSDP/PureDisk solution uses a hacked/modified version of PostgreSQL and under a normal PostgreSQL installation I can move Databases and their locations around no problem by editing some config files, why can I not do this with MSDP? Or perform pgdump of my very important MSDP databases and instead use other weird proprietary methods to get it done?
Thank you all for reading