Yeah, I've always found that a periodic scheduled reboot is a good idea; monthly seems to work well. I still would call it 99.999%, as the downtime is scheduled. We can afford a much higher tolerance for scheduled downtime than for unscheduled downtime. If you can't do that, then there's probably going to be an increased amount of the hairier sort of sysadmin. Cleaning out orphaned shared memory segments while not deleting the wrong ones (phantoms look a lot like orphaned processes at first glance), maintaining active user lists, that sort of thing. A wise, old, even ancient U2 Guru once said to me, "when you can absolutely guarantee to me that there are no bugs in the software you write, we can talk about guaranteeing no bugs in the OS. Until then, we're going to have periodic reboots". Well, words to that effect. He has that wonderful flourish with the English language that uber-geekdom often confers.
It is in identifying the files to replicate that we spend a great deal of our time. You should only replicate those files you care about, but how do you decide which ones to care about? Temp files are usually not replicated, but even that's a judgement call. You certainly need to replicate all of the associated files when you decide to replicate a file. For example, if you're replicating a transaction file, you would want to replicate a batch file to maintain logical data integrity. That ones kind of obvious, but you'll want to investigate & think about the less obvious ones. Do you create work files on the fly? Then don't assume that the VOC is static, etc. You wouldn't want to replicate program files; if you _did_ want to do so, you should re-examine your release/version control process <g>. In short, it's a file-by-file decision process, after you make the global determination, "what's my risk tolerance"?. By this I mean, do you need the system to come up exactly as it was? Or can you "live" with recovering only a subset. Chances are, if you're replicating, your risk tolerance is rational and low. 1. Will this file change after the previous backup? 2. Is this a critical enough file that I will need it to come up as it was at the point of failure? 3. Does this file need to be in sync with another file I need replicated? 4. Other questions you may have. For example, is this an ERP product structure that gets rebuilt from a bill of materials file? You may or may not want to replicate it. Pros would include not having to rebuild it as a part of recovery. Cons would include the resource consumption when you rebuild it on a normal schedule: RFS memory allocation, network saturation, etc. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Scholl Sent: Wednesday, January 23, 2008 1:21 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD: Replication Thanks Wally, I am getting closer. After rebooting again, the RM service is running on both machines. Windows just wants a reboot every now and then. So much for 99.999% uptime. I still have firewall and port-forwarding issues since the two machines are in separate locations. But that is not for this group to suffer through. Does the replication service work through the RPC port 31438? One conceptual question: I copy the complete account from the publishing server to the subscriber. Should I only put the database files that I care about into a replication group or all the data files? Martin Scholl 18910 New Hampshire Ave Brinklow, MD 20862 Phone: 301-924-5537 Cell: 301-613-9572 [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wally Terhune Sent: Wednesday, January 23, 2008 9:50 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] UD: Replication You may find the following IBM.com entitled article useful (180 page guide). UniData Data Replication Operations Guide - v1.1 and v2.1 Also, the minimum UniData Windows release I would recommend for Replication is 7.1.9. The current 7.1.12 release is even better. Wally Terhune SWG Client Support - Information Management Software U2 Support Architect b IBM U2 Client Support Team 4700 S. Syracuse St., Denver, CO 80237 Tel: (303) 773-7969 T/L 656-7969 Mobile: (303) 807-6222 [EMAIL PROTECTED] "Martin Scholl" <[EMAIL PROTECTED] holl.com> To Sent by: <u2-users@listserver.u2ug.org> [EMAIL PROTECTED] cc stserver.u2ug.org Subject [U2] UD: Replication 01/23/2008 05:32 AM Please respond to [EMAIL PROTECTED] er.u2ug.org I am trying to get Replication going between 2 UniData 7.1 Windows system. I installed with Replication selected It seems only one system works properly, in the other I get "RM is not running and from the first system when I try to connect, I get "RM was not responding" What is RM? How do I start this service? I don't see it listed in "Services". Martin Scholl 18910 New Hampshire Ave Brinklow, MD 20862 Phone: 301-924-5537 Cell: 301-613-9572 [EMAIL PROTECTED] No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.9/1238 - Release Date: 1/22/2008 8:12 PM ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ [demime 1.01d removed an attachment of type image/jpeg which had a name of 15028205.jpg] [demime 1.01d removed an attachment of type image/gif which had a name of graycol.gif] [demime 1.01d removed an attachment of type image/gif which had a name of pic15788.gif] [demime 1.01d removed an attachment of type image/gif which had a name of ecblank.gif] ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.9/1238 - Release Date: 1/22/2008 8:12 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.9/1238 - Release Date: 1/22/2008 8:12 PM ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
