> So any security improvement you acquire by use of aliases, is lost if

you

> are forced to publish to the users via backup file name and path, the

backup

> file path. I can only see that backing up remotely must be removed

from the

> remote users's options if you are to protect the database file. No?

Use the OS to create an alias for the destination file location. If you
create a soft link to a directory on the server and give write but not
read permission, then the user will have no idea where the file is
really located on the server, nor be able to look at that location's
contents.
This assumes Unix as the file destination.

Rick DeBay