This is good advice. The real issue is when upgrading my cluster to new HD's we have run
into an issue with a specific query. I have reported this to the support at mysql but have
not found a solution. So I am a bit concerned and do not want to upgrade my primary
cluster drives until I get the other issue resolved. The NFS is actually a connection to a
large storage array are you suggesting a fiber san? Do you have any other suggestions?
Thanks Joshua Gordon
From: Hartmut Holzgraefe [mailto:hartmut.holzgraefe@stripped]
Sent: Friday, October 08, 2010 1:36 AM
Subject: Re: changing the location of online backup.
On 10/08/2010 09:27 AM, Geert Vanderkelen wrote:
> IMHO, you should backup locally, then copy. NFS might fail and it
> might take to much bandwidth, which might cause data node failure.
> Also, I think it's good to keep the last backup locally on disk.
> Just incase you need to restore and need to do it fast.
agree ... personally i'd store backups locally first and use
rsync (with --bwlimit option to make sure that the network is
not saturated by this -> so it does not affect latency in cluster
node communication) to have centralized copies of the backups
for the case that a data nodes local disk fails.
Or use a reliable shared SAN device ... NFS i'd personally not
trust enough for this either ...
Hartmut Holzgraefe | MySQL Regional Support Manager, EMEA
Oracle MySQL Support
ORACLE Deutschland B.V. & Co. KG | Brandenburger Straße 2 | 40880 Ratingen
ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven
MySQL Cluster Mailing List
For list archives: http://lists.mysql.com/cluster
To unsubscribe: http://lists.mysql.com/cluster?unsub=1