Oh, I agree. I like the db copy method best because it makes you absolutly sure that your test and production systems are exactly the same. That makes your test plans for future changes much stronger. You have to be thorough with it, though.

On Jun 7, 2010, at 3:38 PM, pritch <pri...@ptd.net> wrote:

I would think if the env is controlled, integrations would be set up test to test and prod to prod. At least for me, the db copy has worked well, but admittedly, you do need to know your system. Just my opinion, but with
the large number of tables in the system these days, knowing what to
include and exclude becomes just as big of a burden.  Just an option.

On Mon, 7 Jun 2010 15:30:08 -0500, Donald Morton <d1mo...@gmail.com> wrote:
Yeah, we leave the e-mail engine running so we can test its
functionality. Its not just e-mails, though. Integrations that go off
escalations could end up sending duplicate tickets to whatever system
you integrate with.


On Jun 7, 2010, at 3:24 PM, pritch <pri...@ptd.net> wrote:

Good point - I normally don't have the email engine running in a test
environment.  I usually test the emails by reviewing them in the
email msg
form.

On Mon, 7 Jun 2010 15:22:17 -0500, Donald Morton <d1mo...@gmail.com>
wrote:
After you copy the database, don't forget to turn off any
notifications or escalations that you wouldn't want running in test. Otherwise, people may start getting a bunch of emails from your test
system. That really confuses people. Not that I would know! I mean,
so
I hear....


On Jun 7, 2010, at 2:48 PM, pritch <pri...@ptd.net> wrote:

Hi Mary,

When I've done this in the past, we've copied the database from
production
back to test, removed any 'sensitive' data and then migrated any
coding
updates that needed to be changed. A couple of items to watch for:

- You need to make sure your ARAdmin ID to the DB is the same (or
have it
reset)
- All your workflow needs to be server independent (you can export
to a def
file and evaluate)
- All test user accts will need to be reset (I've usually exported
those
and imported after the database is restored.
- probably need to check external interfaces and application
settings to
make sure they are pointed properly.

With all the ancillary forms that are used in remedy, I've found
this to be
the easiest way to get all the data moved intact.

pritch

On Mon, 7 Jun 2010 12:05:40 -0700, Mary Estrada
<mestr...@blizzard.com>
wrote:
Hi,

We are looking for suggestions to sync up all data, i.e.
foundation,
configuration & transaction data from our production server onto
our test
server where we need all the prod-like data and keeping all record
IDs in
their forms.  Your feedback is gratefully appreciated.

Thanks,

~Mary





_______________________________________________________________________________






UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"



_______________________________________________________________________________






UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"



_______________________________________________________________________________




UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"


_______________________________________________________________________________




UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"


_______________________________________________________________________________


UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

_______________________________________________________________________________


UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to