Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Tim Watts Newsgroups: comp.databases.mysql Subject: Re: Can MySql database store images? Followup-To: comp.databases.mysql Date: Mon, 25 Apr 2011 08:30:59 +0100 Organization: A noiseless patient Spider Lines: 43 Message-ID: References: <55md88-7pb.ln1@squidward.dionic.net> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit Injection-Info: mx02.eternal-september.org; posting-host="6oIlEBqCjOm0MjsSUEk5CA"; logging-data="17555"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19sI2zWVSHpp6z0qNKw6QdDV8YxWW9+ENo=" User-Agent: KNode/4.4.6 Cancel-Lock: sha1:2JdSg1w3NT5Lw2NFqOVqE0aP1qg= Xref: x330-a1.tempe.blueboxinc.net comp.databases.mysql:641 Jerry Stuckle wrote: > On 4/24/2011 3:51 PM, Tim Watts wrote: >> Jerry Stuckle wrote: >> >> >>> Totally practical. Just back it up locally then transfer whenever you >>> want. That's how I do filesystem backups, also. That way the backup >>> isn't being delayed by the network. >> >> Yeah - I was kind of considering the case where the total dataset size >> exceeds the capacity of the link over the backup periodicy - which could >> be a problem for a very large dataset and a very weak link. But see >> below: >> > > No more so than for files. Yes more so for files. Using any rsync wrapper of your choice, you may have 10TB of data total and find you only need to transfer 1-10GB of updates per day (real world figure from a university environment). OK - you can keep shifting your binlogs from MySQL but sooner or later you are going to want to run another full backup and suddenly you have to shift all that data again. With files you always get "last night's full backup image" for the cost of the changed files. > > And what happens when you delete a file - but later need to restore it > from backup? You copy it from one of the previous incrementales - specifically the one that was triggered due to the file deletion on the source end. You manage how many incrementals you keep by deleting the ones you don't want, either consolidating the incremental set to the nearest weekly/monthly - or your use the "every incremental looks like a full but virtue of hardlinks" and just delete the ones you no longer want. Usually in some patter like having the last 7 dailys, 4 weeklys, 12 monthlys or whatever. -- Tim Watts