On Nov 5, 2018, at 2:00 PM, Peter Jakobsson wrote:
> Many thanks for the useful replies.
>
> I’ve contacted the IT contractor to try to negotiate a new backup strategy.
>
> Hopefully it will be less of a sweat than the China trade talks :-)
Peter,
If you just enable 4D Backup you should be
Many thanks for the useful replies.
I’ve contacted the IT contractor to try to negotiate a new backup strategy.
Hopefully it will be less of a sweat than the China trade talks :-)
Peter
> On 5 Nov 2018, at 13:36, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Definitely not
Definitely not safe prior to v17. With v17 there's support for Volume Shadow
Copy which puts the datafile in a safe state prior to VMWare taking a snapshot.
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On Nov 5, 2018, at 6:17 AM, Peter Jakobsson via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
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
It will work, but it is *not* safe.
I would use a 4D backup anyway on the same drive the vm works. In this case
they save with the snapshot of the vm the 4D backup files too.
Or you have to dive into the feature of volume shadow copies and the supporting
of them by 4D.
Regards
Lutz
>
5 matches
Mail list logo
