Marc -- As far as GT.M is concerned, you don't need to stop VistA or any other processes accessing a database. A single shell command (mupip backup) can take an instantaneous snapshot of the state of a database (even though the backup operation may take time to complete, the state of the database in the backup will be an instaneous snapshot of the database as of the moment you issue the backup command) in either of two different formats.
Of course, such a backup will contain some information that is "useless" when restored. For example, if VistA stores the pids of Taskman processes, that information is contemporaneous, and of no value in a backup that may be brought up on a different computer system, or even on the same system as a different VistA instance or at another time. VistA presumably has ways to clean this information out of the systenm, because the same issue would exist if a system crashes and is then recovered. The bottom line is that taking the backup with GT.M is (close to being) a no-brainer. Using the backup takes a little thought. Regards -- Bhaskar On Mon, 2006-01-09 at 13:21 -0600, Marc Krawitz wrote: > What is the proper / safe procedure for backing up a VistA > installation? I ask this question separately for gtm and Cache. My > guess is: > > 1) Stop taskman. > 2) Stop background filers. > 3) Stop the RPC listener. > 4) Backup mumps.dat or cache.dat > 5) Re-start everything. > > Am I close? > > Thanks, > > Marc ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
