From: Freddie Cash <fjwcash@gmail.com>
To: CACook@quantum-sci.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Backup Command
Date: Fri, 21 Jan 2011 11:44:24 -0800 [thread overview]
Message-ID: <AANLkTikpV70ktA4+m1gpKpArMQRTVRQEMPMB=POV5Pue@mail.gmail.com> (raw)
In-Reply-To: <201101211107.25039.CACook@quantum-sci.com>
On Fri, Jan 21, 2011 at 11:07 AM, <CACook@quantum-sci.com> wrote:
>
> Well thanks to some help from you guys I seem to have my backup serve=
r almost fully running and functional with rsync. =C2=A0Amazing functio=
ns, this snapshotting and rsync.
>
> I still don't know why I cannot remove snapshots though. (Debian Test=
ing with 2.6.32-28)
>
> And I don't know how to reach out from the backup server to the HTPC =
and stop MythTV there, so I can export the Mysql database safely, from =
a cron job on the backup server. =C2=A0Suggestions?
Simplified, but workable:
#!/bin/sh
ssh someuser@mythtv.pc "/path/to/some/script stop"
/path/to/your/rsync/script
ssh someuser@mythtv.pc "/path/to/some/script start"
The above script would be your backup wrapper script, that gets called =
by cron.
On the HTPC, "/path/to/some/script" would be a script that takes 2
arguments (stop|start).
The stop argument would stop mythtv using the init script for it.
Then would do whatever you need to do to the database (stop it, dump
it, whatever).
The start argument would do the reverse, starting the database and Myth=
TV.
And, "/path/to/your/rsync/script" would call your actual backups
script that runs rsync.
--=20
=46reddie Cash
fjwcash@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-21 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 19:07 Backup Command CACook
2011-01-21 19:14 ` Goffredo Baroncelli
2011-01-21 19:15 ` Niklas Schnelle
2011-01-21 19:44 ` Freddie Cash [this message]
2011-01-21 21:54 ` CACook
-- strict thread matches above, loose matches on Subject: below --
2011-01-10 13:25 Carl Cook
2011-01-10 13:36 ` Hubert Kario
2011-01-11 13:54 ` Ivan Labáth
2011-01-11 14:19 ` Hubert Kario
2011-01-11 14:33 ` Ivan Labáth
2011-01-11 14:40 ` Hubert Kario
2011-01-11 14:53 ` Ivan Labáth
2011-01-15 1:17 ` Carl Cook
2011-01-15 5:25 ` cwillu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikpV70ktA4+m1gpKpArMQRTVRQEMPMB=POV5Pue@mail.gmail.com' \
--to=fjwcash@gmail.com \
--cc=CACook@quantum-sci.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).