Restoring a previous version of a site using strictly import/export feature???

Anthony Levine asked on August 22, 2016 22:47

Backstory: I work for a company who does Kentico content creation/management for a much larger company who hosts 50+ individual sites in a single Kentico instance. This company recently just made the move from Azure Cloud Services to Web Apps. This environment uses a dev -> stage -> production model, and we use stage to do everything that doesn't involve actual dev work (i.e. web part coding). Unfortunately, we had close to 60+ hours of content editing (document creation/deletion, page alias work, template work) on the staging server which was wiped completely clean when a version of production was used as the basis for all 3 instances (dev,stage,prod) after the Cloud Services to Web Apps migration.

The problem: We would like to restore the previous version to the new staging environment. We are able to access an old instance that has been left up solely for this reason. Theoretically, are we able to export the site and import it into the new instance to "overwrite" the current content? Are there any other methods used to restore a backup version of a site? Versioning was not turned on. Though in the export package, I'm able to see all of the pages and content within the document xml file. We were toying with the idea of parsing the XML export data and using that to generate SQL update statements to update the content field in the DB tables based on page ID. Does anyone have any experience doing something similar? Thanks.

Recent Answers

Richard Sustek answered on August 23, 2016 09:12

Hi Anthony,

Importing a site to your stage environment would be possible and it would basically overwrite your current instance. However, the primary keys (IDs) could and will be different than the ones you had before. I'm not sure how your site is developed, but it is recommended to avoid storing ID's in database to create relations as this could be problematic (use GUIDs instead).

If this will be an issue I think you will need to manually update the documents/page templates. I would avoid using SQL updates directly and used API instead to update objects.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.