Hi Susan, I have several dev servers that I keep up to date with various prod servers. I use Misi's rrrChive program for doing that. It is free and extremely useful for synchronising the data between two servers. It is comand line and config file driven so it is easy to create various config files for keeping various applications in sync. It has saved me a lot of time over the last 12 months. Typically I don't want to synchronise all tables all the time so this is much better than either database copies or manual methods. It has a lot of options for doing things like disabling merge workflow automatically, dropping and creating indexes etc. Once you have a config file you trust you can use it again and again, just keeping it up to date when new tables are added or removed from the sync as needed.
I don't use Migrator for code migrations. Like you I have had some bad experiences with corrupt workflow using migrator. I'd rather take full control over the process so I use the standard def file import. Quite often there is some manual intervention required to fix the odd discrepency that can't be migrated. eg. changing the field type of an existing field. I don't think it is practical to have migrations done without any Remedy training unless you have a Remedy person on standby to fix problems. With simple and/or well tested migrations it might work but I'd be sceptical of this being the best way to do things at most organisations. Rod On 15/05/2009, Susan Palmer <[email protected]> wrote: > > ** Hi Everyone, > > We are actually (finally) moving to a Sun Solaris 10 environment. Dev > server is built and in use. Prod server almost done and will be in > production the weekend of 5/30 !! We'll have a BIGIP to two prod servers, > one active and one as a failover if needed. Two Oracle 10g databases using > dataguard to keep insync. We even will have dev and prod Crystal Report > Servers (not sure I see the value to a dev but it completes the picture). > > The next step is inserting a Test server(s) into the mix. It's almost > overwhelming to go to such a 'full' environment. It brings with it some > process changes that are challenging. I'd like some feedback on best > methods you've come across. > > 1. How do you keep the Test server database reasonably current reflecting > the Production database? Is there a way to do this without intervention to > clean server names or manually migrate data? > > 2. Do any of you have a situation where the production operations group is > responsible for moving all enhancements from Test to Production and they are > not Remedy trained? We do have migrator but there are some inherent > problems with using it when Forms you migrate have Audit or Archive forms. > Not sure if this was just a windows problems but had several situations of > corrupted data in the past. > > Any advice is welcome. > > Thanks, > Susan > > ARS v7.0.1P2 > Sun Solaris 10 > Oracle 10gr2 > > Susan Palmer > ShopperTrak RCT Corporation > 200 W Monroe St 11th Floor > Chicago, IL 60606 > Office 312-529-5325 > Cell 312-502-7687 > > > > > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
