Can pointing a cloned site to the original site's database cause problems?
I'm running a Drupal 7 site with a MySQL database sitting on a separate server.
I pulled a clone of the site's codebase repository onto a seperate development server, then imported a very recent backup of the database into a fresh database. The site ran correctly, from a different domain.
However, I forgot to update the
local.settings.php file, so the cloned DEV site pointed to the PROD database. This file was incorrect for about 16 hours, overnight, and I've since updated it to point to the correct database.
While the DEV sit pointed to PROD, I did not create, edit or delete any content on the DEV site. My only change was to disable 'aggregating CSS/JS files' under performance settings. The CRON would have run many times overnight.
I've since cleared all caches and purged all cached URLs from Varnish, but for political reasons I cannot simply restore an earlier backup of the site.
Could this database crossover cause any problems now or in the future?