From: Shyam Prasad N <nspmangalore@gmail.com>
To: Andrew Henry <adhenry.9@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: support for Oracle db consistent backups with btrfs snapshoting?
Date: Mon, 20 Feb 2012 20:59:23 +0530 [thread overview]
Message-ID: <4F4266D3.10108@gmail.com> (raw)
In-Reply-To: <CANLWtDBALsG2S3u_HE21UxMXjUBPjNrEEtKAqR+_tFzPcG4WNQ@mail.gmail.com>
On 02/20/2012 07:49 PM, Andrew Henry wrote:
> Will there be support for consistent backups =C3=A1 la NetApp when us=
ing
> snapshots on btrfs filesystems that contain Oracle databases?
>
> Im not that familiar with NetApp, and don't know whether there needs
> to be "extra support" for the Oracle bits for their snapshoting to
> work, so please forgive me if this is a silly question.
>
> Andrew
> --
> 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
Hi Andrew,
I don't know how exactly oracle db implements consistent backups, but I=
=20
can imagine how.
Oracle db probably runs some sort of script after commit of a database=20
snapshot which commands NetApp filer to create a snapshot.
If that is so, I don't see the oracle/btrfs configuration to be much=20
different either. The oracle-side scripts can be made to run btrfs=20
snapshot creation commands in this case.
Hope that helps.
Thanks,
Shyam
--
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:[~2012-02-20 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 14:19 support for Oracle db consistent backups with btrfs snapshoting? Andrew Henry
2012-02-20 15:29 ` Shyam Prasad N [this message]
2012-02-20 18:48 ` Felix Blanke
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=4F4266D3.10108@gmail.com \
--to=nspmangalore@gmail.com \
--cc=adhenry.9@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.