At this point I have realized two things. 1) tar accepts a stream of
filenames in, not a data stream. 2) backuppc expects specifically a tar
stream, not just a file stream(with a list of files preceding the data).
To that end I have thrown out the idea of using tar and I have resorted to
writing m
On 26/04/13 14:39, Les Mikesell wrote:
> On Thu, Apr 25, 2013 at 6:09 PM, Lord Sporkton wrote:
>> I'm aware of zmanda and several other backup options however at this time
>> this is what we have and this is what we are trying to leverage. Perhaps it
>> will turn out that writing to a flat file is
On Thu, Apr 25, 2013 at 6:09 PM, Lord Sporkton wrote:
> I'm aware of zmanda and several other backup options however at this time
> this is what we have and this is what we are trying to leverage. Perhaps it
> will turn out that writing to a flat file is the only option. But the nature
> of the ba
> could get it to work. Tar is of course capable of accepting either stream or
> file as input and mysqldump is capable of outputing to either stream or
> file. I suppose I will just have to play around with it more maybe.
Please show an example of where you can stream data directly into tar
I'm aware of zmanda and several other backup options however at this time
this is what we have and this is what we are trying to leverage. Perhaps it
will turn out that writing to a flat file is the only option. But the
nature of the backuppc commands leads me to believe there is some
possibility t
>From the sound of things backuppc probably isn't the best bet for you. It
>works on the file level, which won't work for mysql. This leaves you with
>really one option for backing up db's and that is writing to a flat file. What
>you may need is some sort of block level backup, this way you can
It is on linux yes. That is not out of the question, but it would be
preferred for management purposes to do it though the command in backuppc.
Its not just one server, its dozens and growing. Its also multiple
customers and departments.
On 25 April 2013 14:53, Sabuj Pattanayek wrote:
> Does yo
Does your mysql db live on a unix system? If so, why not use
automysqlbackup and just have it dump to your backup system over NFS?
On Thu, Apr 25, 2013 at 4:45 PM, Lord Sporkton wrote:
> I'm currently backing up mysql by way of dumping the DB to a flat file then
> backing up the flat file. Which
I'm currently backing up mysql by way of dumping the DB to a flat file then
backing up the flat file. Which works well in most cases except when
someone has a database that is bigger than 50% of the hdd. Or really bigger
than around say 35% of the hdd if you account for system files and a
reasonabl
