Hi Tim, Many thanks for the suggestions and quick reply. I wonder how other developers use SCSI AWS storage gateways to host live MySQL then? I think the way AWS storage gateways mounted as iSCSI devices should work. So customer has a s3 volume setup in a local machine at the premises which is like a cached disk for s3 storage for redundancy .... Am I thinking straight? Or off track completely....what is http://docs.aws.amazon.com/storagegateway/latest/userguide/initiator-connection-common.html mean exactly?
On 13 December 2016 at 22:07, Timothy Penner <[email protected]> wrote: > Hi Balinder, > > I have heard of "issues" with using dropbox as a storage location for the > database files (4DD, 4DB, journal, etc); specifically issues using dropbox > as a way of synchronizing the database files offsite... In that situation > simply moving the database files outside of the dropbox watch folder fixed > the issue, as if dropbox was causing the issue by locking the file or > something. I can’t recall how the issue manifested itself but I remember > the resolution being to move it outside of the dropbox watch folder. > > Instead of storing the files directly inside of the Dropbox or S3 folder, > a better approach is to work with the files locally in their own folder and > only copy or move them to the dropbox/S3 as needed. > > I definitely wouldn’t move the 4DD/4DB/Jorunal files to dropbox or S3, > maybe copy them when 4D isn’t running, but I would not move them. You > wouldn't want the running files to be locked by an external process, while > having a *copy* of the file locked is not a big deal. > > I also wouldn’t backup directly to dropbox or S3 either, but maybe use On > Backup Shutdown to trigger an operation that will move the finished backup > file to the dropbox or S3 watchfolder. > > You want the 4DD/4DB/Journal/4BK locations to have fast write (and read) > access otherwise you risk slowing down those operations and having other > issues down the line. Running your database off of a network drive (in the > same local network) isn't even suggested and can be problematic on its own, > so running them from an offsite storage (or placing them in a location that > can be locked by an external process while synchronizing them offsite) > would be even worse. > > Hope that helps! > > -Tim PENNER > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
