Production System and Test System Sync

The set up for our test server is also different from our production server.  The hardware is a little newer and we have a couple of additional solutions.  But we've found that as long as most of our tables match (content specificially) we are able to predict likely behavior between both servers.  So, it could depend on what you want to commonly test. 

We frequently test future changes to the production server by making the modifications to our test server.  For that, we need the values of our tables to be similar.  For example, Queues, Quick Incidents, Rules, Notifications....etc.  We do have mirrored drives and once we tried to overwrite our production database to our test db...but it was a mess.  After having our DBA spend hours trying to rename things...we had the closest environment we'd ever had and it didn't really provide a lot of benefits. 

The simpliest thing is to keep the to systems aligned with your configurations so that what can be predicted on the production server can be verified on the test.  :)

I'd also recommend matching your test server to your production server.  Of utmost importance is making sure you have the same versions, not just the same solutions.  Database changes can often be pretty big depending on version differences. 

I'd also be curious about which databases you're mirroring.  The helpdesk solution does have it's own database (Altiris_Incidents) that I've been able to float from Production over to my test server even though the test server had other solutions that the Production helpdesk box didn't have. 

All in all if it's just a test I'd say backup the test database, drop the production one on top of it as a test.  If it doesn't work just drop the backup back on your test box and plan on reloading it to match production.  If it does work you've saved some time by not reloading the server.

What I do, use BESR (Backup Exec System Recovery).
When I want to be sure my test = production, I make a Recovery Point of my production for use in VmWare
As long as both machine do not "see" each other there is no harm.
I test what ever I want. I can use VmWare snapshots to return to a certain point, etc, etc.
Works like a charm. Can also be done with free tools of VmWare, but... ->
One very nice addition using BESR, doing this I also have a nice Disaster recovery as I can also go from VmWare towards a physical machine with BESR. So I have setup a proces making Recovery Points every day.

One other official thing, licenses. Using this as your procedure will bring little hassle on licenses as when you have two similar systems running al the time...  At least that is my point of view.

Regards