We run umbraco (a multiple domain installation) in a virtual server environment. Our plan to provide 'staging' was to use the ability to copy and redeploy entire virtual servers very effeciently. We thought we'd copy a server instance, copy the umbraco db and presto! we'd have an exact copy of the original.
We hit a snag. The copied server works perfect when pointed to the original umbraco db. But when it is pointed to the copied instance of the umbraco db, domains and updates don't work properly.
To be specific, the version of the page at
http://intranet.webdev1/index.aspx and http://webdev1/index.aspx are not always the same. (IIS default website is set to the first domain in our installation) And changes to the page content when published only are visible at the non-domain url until the web config is touch after which the change is visible at the domain url. It is like the domain version doesn't know there was a new version published. And while touching web config fixes the problem, republishing the page or site from the umbraco console does not. I thought both of those actions caused umbraco.xml to be written.
We're running version 2.1.3 and I've seen posts regarding domain/publishing issues that were not fixed until 2.1.5. We were hoping to wait to upgrade until v3.0 was ready. But the the odd thing is that this instance (original and copied) works perfectly....until that copied db is used as the source.
Any ideas what could be wrong? Anyone else playing with virtual servers....any thoughs on this as way to effect staging?
Thanks
Jason