Guys,
The suite for FileMaker Pro Server 3.0 is;
force quit: Quit application, disconnecting guests if necessary
force quit
[minutes small integer] -- Minutes to wait before
disconnecting guests
[message string] -- Message to send to connected
guests
close: Close a list of files
close list -- Files to close
force close: Close a list of files, disconnecting guests if necessary
force close list -- Files to close
[minutes small integer] -- Minutes to wait before
disconnecting guests
[message string] -- Message to send to connected
guests
database pause: Pause the processing of a list of files
database pause list -- Files to pause
database resume: Resume the processing of a list of files
database resume list -- Files to resume
list databases: Return a list of open database files
list databases
Result: list -- The list of open database files
There is a "force quit" step ... it forces clients to be disconnected if
necessary. Actually I thought it was only necessary to use a "database
pause" before a Retrospect backup, then a "database resume" step after.
My personal preference is to use the FileMaker Pro Server built-in backup
capability where you can schedule FileMaker Pro Server to make a copy of all
of the databases in another location, then use Retrospect to backup the
"other" location.
Cheers, Malcolm
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Information Alchemy Pty Ltd
ACN 089 239 305
Canberra, Australia
Malcolm McLeary Mobile: 0412 636 086
Managing Director Email: [EMAIL PROTECTED]
This message was sent using Outlook Express 5.0 for Macintosh.
--
----------------------------------------------------------
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.