to some extent i concur with the above sentiments. i actually use the old service method, i don't use systemd. e.g perfect use case in cloud environment where you need the instance to automatically start everything if you have an instance stop/start schedule to contain costs. As for Production, i have never implemented a script and prefer a controlled operation. This is mostly because Cache is too finicky when it comes to start-ups, and preferably you need to be present.

Hi Steve;

I have encountered the same problem where these online backups are problematic on a production system - from the time it writes to disk to the time and it's copied out.

To start with - these are cold offsite backups taken only at a point in time - (NOT A DR SOLUTION). So backing up on the DR Async made more sense to us and we relieved the production a lot. I  have actually restored these backups on other aut/training/tests environments and they are just as good.

So if for off-site backup purposes - no harm I have encountered doing that.

Regards;
Anzelem.

Just been in same situation yesterday and the migrate from ODBC worked for us. We needed the data in Cache for Reports, Dashboards, etc.

The new challenge is: the application that uses MySQL is not yet re-coded to use Cache, so the data is still written in MySQL. Using ODBC to do what we want was giving all sorts of errors... (due to restrictions and limitations for external sources as mentioned in these docs.).  After migrating the data, no issues at all.

Is there a way OR does anyone know how to keep the migrated data always in Sync? If data is written in MySQL it's automatically synced into Cache (... well in Cache speak this will be shadow, mirror, etc). Or custom polling needs to be written?

Regards;

Anzelem.

Thanks Murray for these 'new technology catch-up' articles, especially this part, 9 and 10. Bob alerted me to these. I do have HCI deployment in the horizon based on ESXi and EMC scaleio all-flash (both cache and capacity tiers) architecture. I will keep this in mind when we finally meet the vendors of the HCI kit.

In the article you mentioned "you define the capabilities of storage as policies in vSAN using SPBM; for example "Database" would be different to "Journal". I was hoping to see specific policies for these further down the article??  (well if you consider i'm from traditional arrays where we normally pay attention to these).

Regards;

Anzelem.

Hi Shawn;

Your method you mentioned works perfectly well. I have used it a lot, am predominantly Linux and my most preferred share is over 'nfs'.  Ensure you have write permissions to that drive and that there is no network performance impact when it is running between the two servers, but with the speed you mentioned the impact is insignificant. The other advantage is that the write I/O will be on the other server. 

Regards;

Anzelem.