> However, let's point out that backing up files that are in use (frequent > case when you have them on the web) will make the backup corrupted without > even knowing.
The way we do this is to backup the file BEFORE it is installed. For example, we have a number of applications which run over the internet, and users submit pictures to be associated with database records. The file they submit is copied to a backup location and a second copy is placed in the web location (transparent to the user), and the web copy path and file name are stored in the database record. This image file is then available for both web access and through Windows apps. The backup copy is backed up offsite to DVD incrementally. Only the new and changed files are written to a DVD and stored offsite. > Size of the dump file? - use a DVD disk (or two.) it cost about a dollar! This is a good idea that a lot of people miss. We are gradually replacing our tape backup installations with a combination of disk-to-disk backups with DVD for offsite and archive. > But let's point out something was forgotten in this exchange of messages: > the need of the user to access same image files with other tools. That > should conclude our debate giving priority to images in separate files. > (unless. but no! it was enough!) I agree with that. I probably wasn't clear enough on this point, but it was one of the main reasons we prefer to keep the files in the file system (and not in the database). Thanks for your input. Glenn Lawler ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
