Peter, In a low transaction environment it's probably not an issue. But if the copy happens to take place during a cache flush you can wind up with a corrupted datafile. It's easily fixed by MSC but a record or two may be lost. I've experienced this myself by making a copy of a live datafile on a system with maybe 10 users logged in at the moment. It works most of the time but fails a non-trivial number of times.
I would try to convey to the vendor that the architecture of 4D is not one that lends itself to this type of backup. If they won't give you an external drive the backup and log file is the final word. Client's risk, client's choice. On Mon, Nov 5, 2018 at 3:17 AM Peter Jakobsson via 4D_Tech < 4d_tech@lists.4d.com> wrote: > What are the implications of backing up the VM while 4D server is still > running ? On the old days this would have been a complete no-no because of > un-flushed caches, locked datafiles and all sorts of issues. Is anybody > running this particular configuration ? > -- Kirk Brooks San Francisco, CA ======================= *We go vote - they go home* ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
