Restoring Page Versions that were Deleted by the Removal Job
Permalink 1 user found helpful
Hello, I wanted to see if anybody had any information on how to restore old page versions from the SQL database that have been removed from Concrete5 using the automated job. The job trims the versions down to the last 10, although the industry I work in requires that we hold on to all versions.
I can see the old versions in the SQL database, so I know they are still living, I just need to load them back up into Concrete5.
Any help is appreciated.
Thank you.
I can see the old versions in the SQL database, so I know they are still living, I just need to load them back up into Concrete5.
Any help is appreciated.
Thank you.
jvansanten is correct in saying that the "Remove Old Page Versions" job does delete page versions from the database. Until someone comes up with a larger solution to store static 'snapshots' of past page versions, I'm guessing something like "Backup VooDoo" might be helpful to keep monthly whole-site backups offsite.
http://www.concrete5.org/marketplace/addons/backup-voodoo/...
http://www.concrete5.org/marketplace/addons/backup-voodoo/...
I appreciate the feedback! This is my first round with Concrete5 and I love it so far. Adding Backup Voodoo seems to have done the trick for what I need currently.
In a previous life, we built a hulking backup/restore process. This is much more elegant and does what I need.
I'll look into the hosting option if things start to get bigger. Thank you for all the help!
In a previous life, we built a hulking backup/restore process. This is much more elegant and does what I need.
I'll look into the hosting option if things start to get bigger. Thank you for all the help!
If you do need the history, perhaps it's better to avoid the utility and look at enhanced hosting options with your host, or a platform that provides higher performance.
I haven't used the utility. The documentation suggests that it does delete records. So, if it's an issue of reintegrating older records, that could be done by accessing a database backup prior to the deletion as well as a current backup.
You then could use a tool like dif on each table to identify the missing data and restore it.
I don't know the database structure of C5 sufficiently well to identify problems with this approach. If autoincrement fields are used as key values in any table, for example, this would fail.