TMG-L Archives

Archiver > TMG > 2010-04 > 1272130153


From: Rick Van Dusen <>
Subject: Re: [TMG] Complete Export/import of TMG data sets
Date: Sat, 24 Apr 2010 10:52:47 -0700
References: <351417.72171.qm@web88304.mail.re4.yahoo.com>
In-Reply-To: <351417.72171.qm@web88304.mail.re4.yahoo.com>


There are a number of fundamental computer limitations that preclude TMG
from backing up "absolutely everything". I'll name only two that have
been mentioned here:

1. Data paths vary from user to user, and even from computer to computer
of single users. This makes backing up and restoring Exhibits a bit
tricky to program into TMG (at least to do so in a way that all users
can learn to use).

2. As Jim said earlier today, every computer is a little different, so
backing up the app.ini file that saves all the TMG settings is a bad
idea. And without backing up and restoring this file, a number of
settings need to be recreated, e.g. data paths and custom languages.

Actually, this "not quite complete transfer" situation exists with most
computer upgrades with most software. With MS Office, for example, many
settings need to be in the Registry, and you dare not copy the Registry
from one computer to another; there are just too many settings that
vary. And if you attempt to copy branches or even keys, you're liable to
run into the CSIDs being different from one computer to the other. So
you end up recreating the e.g. customized toolbars.

Terry and Virginia have already told you that the backups already
contain all the options you list; I would amend to "all the options that
are reasonable": There are some things you really don't want TMG to try
to do for you, or that TMG flat-out can't do.



Pierce Reid wrote:
> With all the problems people have pointed out with backing up not just the TMG data base, but also exhibits, and various preferences that are not limited to one data base, it seems TMG needs a complete Export and Import process.
>
> Export would create a file (probably a .sqz file) that contains everything TMG knows about your data base. That would include backing up all exhibits, source templates, report definitions, etc. which the current basic backup does not save. (I'm still confused what is missing from a normal backup, but I'm sure when I need the information, I can find it by trolling this list and the many helpful documents available on-line.)
>
> There would need to be a complementary Import function that would restore everything. There could be some options, such as, Do you want the original exhibits folder locations re-used or re-recreated, or Do you want exhibits stored in one folder or folder structure?
>
> The Exported file may be quite large, and may even have to be split over several DVDs (like our old backups were split over several floppies), and the Export and Import processes should handle that.
>
> This sort of export would not have to be used as often as you should do a regular backup of your data. A regular backup could be applied to an Imported data base if none of the normally missing information has been changed between the full Export and the regular backup. And even if you added a few exhibits since the Export, it is easier to deal with a few problems rather than many that you don't really understand.
>
> This facility would be of use when someone is moving to a new computer, or new operating system, or replacing a hard drive that died. Many users do not know enough about operating systems or TMG data locations to be able to reliably rebuild their TMG data base(s) without a lot of work.
>
> Pierce
>
> PS
>
> And as a side note: one reason for having a TMG exhibit copy of your images in addition to the original copy is file size. You can often greatly reduce the file size by using JPEG or some other image file compression facility. Ancestry census and other images can often be reduced in size by a factor of 5 or more without hurting the readability of the hand writing. Images from modern digital cameras and scanners can often let your pick out a face from a group picture, but if the group picture is your exhibit, you don't need that detail. Reducing the file sizes of images can greatly reduce the file size of a web site or a report you send to a relative.

This thread: