I agree with John, have FileMaker do database copies. Then when you back up
you'll get two copies of each database.
I go one step further. I have FileMaker make a copy mid day, (to duplicate
that mornings work) then at 6:30pm (after everyone is done working but
before backups happen) Then Retrospect backs up the machine with all 3
copies of each database.
We've got too much riding in our FMPro databases to lose a whole days work.
I figure better safe than sorry.
Tim
____________
John Gee wrote:
> At 12:14 PM -0700 3/10/00, Todd Reed wrote:
> >I figure that if I have 'verify' turned on, and the log doesn't
> >indicate a problem that the database files are getting backed up
> >okay. Is this the experience of the list, or should I be practicing
> >preventive paranoia?
>
> FileMaker Server keeps a lot of data in a RAM cache. Even if the
> database is backed up by Retrospect without errors, I am not sure
> that guarantees that the file will be in a known good state.
>
> I recommend preventive paranoia, have FileMaker perform database
> copies using its internal scheduling, and use Retrospect to backup
> the copies.
> --
> John Gee [EMAIL PROTECTED]
> Dunedin, New Zealand Programmers live in interesting times...
>
> --
> ----------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives: <http://list.working-dogs.com/lists/retro-talk/>
>
> For urgent issues, please contact Dantz technical support directly at
> [EMAIL PROTECTED] or 925.253.3050.
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://list.working-dogs.com/lists/retro-talk/>
For urgent issues, please contact Dantz technical support directly at
[EMAIL PROTECTED] or 925.253.3050.
