Hi Peter, Indeed, it is a brave new world, isn’t it? And like you said, it all happened transparently.
At my last employer everything was virtualized. The SAN ‘guarenteed’ data uptime and redundancy. “Disks” (HDD or SSD) were ‘auto-healing’ and hardware failover was automatic. It is really quite amazing. And it worked very well. Once the VMs were optimized it was as fast or faster than dedicated hardware. Moving 4D Server to the “external cloud" is another question. For optimum (or maybe even just tolerable) performance, your app will need to be designed with a very lightweight front end. Or abandon 4D client and use a web front end. >I don’t really like the idea that the log file has the same redundancy system >as the main datafile because the whole idea is that the corruption doesn’t get >replicated (which is what a RAID system does) and it’s independent at the >logical level. > A SAN is really a lot more that just a RAID. As for a backup strategy, at this point we’re really talking about a disaster recovery plan, since the SAN is ‘guarenteed'. You might consider mirroring to another ‘cloud service'. Since "spinning up" a VM is so easy now, all you need is another 4D server license to set up a 4D mirror server. Have it integrate the log file every minute or two and you have a near real time backup, ready for (manual) failover. Since only the log files sent, and they are tiny, the bandwidth costs would be extremely small. Tom benedict ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
