We have ~30G externalized attachements and a ~4G db left.
Now we want to move from
postgresql. So the proposed process for this (see here for example) is basically:
- Serialize the data (
- Initialize a ne pg-database (
- Import the data (
I initially worked on a dev-machine where externalized data was not present. I then created the mysql-db from a backup och the live-system. This works nice and well except that the externalized data is not shown when viewing tickets.
But when I try to serialize the database it will complain about all the missing attachments with messages like:
Failed to load 7d526b07fdddbe548704a7d60466f5fb93feebc13c1bec6244ef3c7edacbcb3c from external storage: File does not exist
The result is that the references in the serialized data is set to null. This can be solved by first copying all the externalized data to the dev-machine. Now the serialization works without errors, byt the already externalized data is also included in the serialized output (~34G v.s. ~4G).
This is very inconvenient. The externalized data is in all practical terms already serialized (stored in separate files on disk) so I can not see any reason why it should be serialized again.
To proceed I would now need to import all data (including the previously externalized data) back into the new database just to externalize it ones again.
So my question is:
Is there a way for me to avoid having to serialize the externalized data and just serialize the database-content?