On my project we are using the GR off mesh. We created a second network which is called the Archestra network. The GR is on the Archestra network and all IEE client stations are on mesh and Archestra networks. The main reason we moved the GR off mesh was to enable the multi-core to improve performance. The off mesh GR configuration is defined in the InFusion Deployment guide. You are correct in that to be on the mesh (that is to load and run IA software) you must disable the multi-core option on the workstation. We use Windows Scheduler to run a script to make a galaxy backup every night. We downloaded the script from the Archestra.biz site. -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of stan Sent: Wednesday, March 24, 2010 8:55 AM To: Foxboro List Subject: [foxboro] Off Mesh Galaxy database Has anyone implemented a design where their Galaxy DB is "off mesh"? What I am referring to here is a design where IEEE is on an AW on the mesh, and has it's database located on a machine connected to this AW via an additional NIC. To kind of explain why I am thinking about this here is the long version. It is my understanding that to be "on mesh" any machine must run only a single core, even if it is for instance a quad core machine. If this is incorrect, I would love to hear that, BTW. So, given the perceived fragility of this DB, I am thinking that, particularly when we are doing active development work, we want to back up this DB _very_ frequently. Now I would like to minimize the amount of time spent doing these backups, and it seems to me being able to run this on a machine that I can take full advantage of the power of the hardware would be advantageous. Thoughts? -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave