Backup problem for backup MySQL (a table > 2GB)
Patrick Dung
patrick_dkt at yahoo.com.hk
Tue Aug 16 07:16:50 GMT 2005
The main problem is money. Buying a new product needs money.
The old backup product (commercial) is scalable and is working fine
with various OS. However it is outdated and is not supported anymore
(unless we have a service agreement with the vendor of the backup
product.)
It consumes lots of space to do tar+gzip and split.
I am thinking if I could copy all mysql files to another server (by
ftp/ssh) periodically.
Regards
Patrick
--- Vasil Dimov <vd at datamax.bg> wrote:
> On Mon, Aug 15, 2005 at 11:41:09PM -0700, Patrick Dung wrote:
> > Hi
> >
> > We are using an old backup product which can only backup files <
> 2GB.
> > Now we have a mysql file > 2GB. The backup product refuse to backup
> > that file.
> >
> > So, whats the alternatives to perform backup for this situation?
> > This is current idea:
> >
> > Tar all the mysql directory and split into small files < 2GB.
> >
> > Any suggestions?
> >
>
> I guess this is not applicable, but what about using other "backup
> product" that supports larger files?
>
> Otherwise tar(1) + gzip(1) (eventually) + split(1) seems reasonable
> solution...
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
More information about the freebsd-hackers
mailing list