You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by user 01 <us...@gmail.com> on 2014/05/28 14:34:43 UTC
What are the advantages of static column family over a dynamic column family?
What are the advantages of static column family over a dynamic column
family? Otherwise why shouldn't I just make all my column families just
dynamic for the reasons of ease?
Do static column families save diskspace or offer better reads/writes
performance ?
Re: What are the advantages of static column family over a dynamic
column family?
Posted by Jens Rantil <je...@tink.se>.
Hi user 01 (firstname and lastname?),
I'll give you one technical answer and one related to modelling:
Technical: Sure, you could really put all your data on a single row. The
problem is it will simply not scale horizontally. More cassandra nodes will
not make your cluster perform better and will not give you more resources
in terms of disk or RAM.
Modelling: A single row might only have static columns. To have a self
documenting schema you might want to make your columns for that particular
reason.
Cheers,
Jens
On Wed, May 28, 2014 at 2:34 PM, user 01 <us...@gmail.com> wrote:
> What are the advantages of static column family over a dynamic column
> family? Otherwise why shouldn't I just make all my column families just
> dynamic for the reasons of ease?
>
>
> Do static column families save diskspace or offer better reads/writes
> performance ?
>
RE: Backup Cassandra to
Posted by S C <as...@outlook.com>.
Despite storing a replica in the "backup node", what is the guarantee that the "backup node" has all the data? Unless you make consistency a priority over availability of your cluster.
I could think of another approach.
You can design your cluster with a topology such that your work load is split into to virtual datacenters and you keep replicas in both datacenters. During read you can do LOCAL_QUORUM and during write you can do EACH_QUORUM. With this set up you can call the second virtual datacenter as a backup. Sorry there are no tapes involved here.
Thanks,KumarFrom: maria.camacho@nsn.com
To: user@cassandra.apache.org
Subject: RE: Backup Cassandra to
Date: Fri, 13 Jun 2014 10:04:49 +0000
Thanks a lot for your responses.
Maria.
From: ext Jabbar Azam [mailto:ajazam@gmail.com]
Sent: Thursday, June 12, 2014 10:09 PM
To: user@cassandra.apache.org
Cc: Jack Krupansky
Subject: Re: Backup Cassandra to
Yes, I never thought of that.
Thanks
Jabbar Azam
On 12 June 2014 19:45, Jeremy Jongsma <je...@barchart.com> wrote:
That will not necessarily scale, and I wouldn't recommend it - your "backup node" will need as much disk space as an entire replica of the cluster data. For a cluster with a couple of nodes that may be OK, for dozens of nodes, probably
not. You also lose the ability to restore individual nodes - the only way to replace a dead node is with a full repair.
On Thu, Jun 12, 2014 at 1:38 PM, Jabbar Azam <aj...@gmail.com> wrote:
There is another way. You create a cassandra node in it's own datacentre, then any changes going to the main cluster will be replicated to this node. You can backup from this node. In the event of a disaster the data from both clusters
and wiped and then replayed to the individual node. The data will then be replicated to the main cluster.
This will also work for the case when the main cluster increases or decreases in size.
Thanks
Jabbar Azam
On 12 June 2014 18:27, Andrew <re...@gmail.com> wrote:
There isn’t a lot of “actual documentation” on the act of backing up, but I did research for my own company into the act of backing up and unfortunately, you’re not going
to have a similar setup as Oracle. There are reasons for this, however.
If you have more than one replica of the data, that means each node in the cluster will likely be holding it’s own unique set of data. So you would need to back up the
ENTIRE set of nodes in order to get an accurate snapshot. Likewise, you would need to restore it to the cluster of the same size in order to restore it (and then run refresh to tell Cassandra to reload the tables from disk).
Copying the snapshots is easy—it’s just a bunch of files in your data directory. It’s even smaller if you use incremental snapshots. I’ll admit, I’m no expert on tape
drives, but I’d imagine it’s as easy as copy/pasting the snapshots to the drive (or whatever the equivalent tape drive operation is).
What you (and I, admittedly) would really like to see is a way to back up all the logical *data*, and then simply replay it. This is possible on Oracle because it’s typically
restricted to either one (plus maybe one or two standbys) that don’t “share” any data. What you could do, in theory, is literally select all the data in the entire cluster and simply dump it to a file—but this could take hours, days, or even weeks to complete,
depending on the size of your data, and then simply re-load it. This is probably not a great solution, but hey—maybe it will work for you.
Netflix (thankfully) has posted a lot of their operational observations and what not, including their utility Priam. In their documentation, they include some overviews
of what they use: https://github.com/Netflix/Priam/wiki/Backups
Hope this helps!
Andrew
On June 12, 2014 at 6:18:57 AM, Jack Krupansky (jack@basetechnology.com) wrote:
The doc for backing up – and restoring – Cassandra is here:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_backup_restore_c.html
That doesn’t tell you how to move the “snapshot” to or from tape, but a snapshot is the starting point for backing up Cassandra.
-- Jack Krupansky
From:
Camacho, Maria (NSN - FI/Espoo)
Sent: Thursday, June 12, 2014 4:57 AM
To:
user@cassandra.apache.org
Subject: Backup Cassandra to
Hi there,
I'm trying to find information/instructions about backing up and restoring a Cassandra DB to and from a tape unit.
I was hopping someone in this forum could help me with this since I could not find anything useful in Google :(
Thanks in advance,
Maria
RE: Backup Cassandra to
Posted by "Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com>.
Thanks a lot for your responses.
Maria.
From: ext Jabbar Azam [mailto:ajazam@gmail.com]
Sent: Thursday, June 12, 2014 10:09 PM
To: user@cassandra.apache.org
Cc: Jack Krupansky
Subject: Re: Backup Cassandra to
Yes, I never thought of that.
Thanks
Jabbar Azam
On 12 June 2014 19:45, Jeremy Jongsma <je...@barchart.com>> wrote:
That will not necessarily scale, and I wouldn't recommend it - your "backup node" will need as much disk space as an entire replica of the cluster data. For a cluster with a couple of nodes that may be OK, for dozens of nodes, probably not. You also lose the ability to restore individual nodes - the only way to replace a dead node is with a full repair.
On Thu, Jun 12, 2014 at 1:38 PM, Jabbar Azam <aj...@gmail.com>> wrote:
There is another way. You create a cassandra node in it's own datacentre, then any changes going to the main cluster will be replicated to this node. You can backup from this node. In the event of a disaster the data from both clusters and wiped and then replayed to the individual node. The data will then be replicated to the main cluster.
This will also work for the case when the main cluster increases or decreases in size.
Thanks
Jabbar Azam
On 12 June 2014 18:27, Andrew <re...@gmail.com>> wrote:
There isn’t a lot of “actual documentation” on the act of backing up, but I did research for my own company into the act of backing up and unfortunately, you’re not going to have a similar setup as Oracle. There are reasons for this, however.
If you have more than one replica of the data, that means each node in the cluster will likely be holding it’s own unique set of data. So you would need to back up the ENTIRE set of nodes in order to get an accurate snapshot. Likewise, you would need to restore it to the cluster of the same size in order to restore it (and then run refresh to tell Cassandra to reload the tables from disk).
Copying the snapshots is easy—it’s just a bunch of files in your data directory. It’s even smaller if you use incremental snapshots. I’ll admit, I’m no expert on tape drives, but I’d imagine it’s as easy as copy/pasting the snapshots to the drive (or whatever the equivalent tape drive operation is).
What you (and I, admittedly) would really like to see is a way to back up all the logical *data*, and then simply replay it. This is possible on Oracle because it’s typically restricted to either one (plus maybe one or two standbys) that don’t “share” any data. What you could do, in theory, is literally select all the data in the entire cluster and simply dump it to a file—but this could take hours, days, or even weeks to complete, depending on the size of your data, and then simply re-load it. This is probably not a great solution, but hey—maybe it will work for you.
Netflix (thankfully) has posted a lot of their operational observations and what not, including their utility Priam. In their documentation, they include some overviews of what they use: https://github.com/Netflix/Priam/wiki/Backups
Hope this helps!
Andrew
On June 12, 2014 at 6:18:57 AM, Jack Krupansky (jack@basetechnology.com<ma...@basetechnology.com>) wrote:
The doc for backing up – and restoring – Cassandra is here:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_backup_restore_c.html
That doesn’t tell you how to move the “snapshot” to or from tape, but a snapshot is the starting point for backing up Cassandra.
-- Jack Krupansky
From: Camacho, Maria (NSN - FI/Espoo)<ma...@nsn.com>
Sent: Thursday, June 12, 2014 4:57 AM
To: user@cassandra.apache.org<ma...@cassandra.apache.org>
Subject: Backup Cassandra to
Hi there,
I'm trying to find information/instructions about backing up and restoring a Cassandra DB to and from a tape unit.
I was hopping someone in this forum could help me with this since I could not find anything useful in Google :(
Thanks in advance,
Maria
Re: Backup Cassandra to
Posted by Jabbar Azam <aj...@gmail.com>.
Yes, I never thought of that.
Thanks
Jabbar Azam
On 12 June 2014 19:45, Jeremy Jongsma <je...@barchart.com> wrote:
> That will not necessarily scale, and I wouldn't recommend it - your
> "backup node" will need as much disk space as an entire replica of the
> cluster data. For a cluster with a couple of nodes that may be OK, for
> dozens of nodes, probably not. You also lose the ability to restore
> individual nodes - the only way to replace a dead node is with a full
> repair.
>
>
> On Thu, Jun 12, 2014 at 1:38 PM, Jabbar Azam <aj...@gmail.com> wrote:
>
>> There is another way. You create a cassandra node in it's own datacentre,
>> then any changes going to the main cluster will be replicated to this node.
>> You can backup from this node. In the event of a disaster the data from
>> both clusters and wiped and then replayed to the individual node. The data
>> will then be replicated to the main cluster.
>>
>> This will also work for the case when the main cluster increases or
>> decreases in size.
>>
>> Thanks
>>
>> Jabbar Azam
>>
>>
>> On 12 June 2014 18:27, Andrew <re...@gmail.com> wrote:
>>
>>> There isn’t a lot of “actual documentation” on the act of backing up,
>>> but I did research for my own company into the act of backing up and
>>> unfortunately, you’re not going to have a similar setup as Oracle. There
>>> are reasons for this, however.
>>>
>>> If you have more than one replica of the data, that means each node in
>>> the cluster will likely be holding it’s own unique set of data. So you
>>> would need to back up the ENTIRE set of nodes in order to get an accurate
>>> snapshot. Likewise, you would need to restore it to the cluster of the
>>> same size in order to restore it (and then run refresh to tell Cassandra to
>>> reload the tables from disk).
>>>
>>> Copying the snapshots is easy—it’s just a bunch of files in your data
>>> directory. It’s even smaller if you use incremental snapshots. I’ll
>>> admit, I’m no expert on tape drives, but I’d imagine it’s as easy as
>>> copy/pasting the snapshots to the drive (or whatever the equivalent tape
>>> drive operation is).
>>>
>>> What you (and I, admittedly) would really like to see is a way to back
>>> up all the logical *data*, and then simply replay it. This is possible on
>>> Oracle because it’s typically restricted to either one (plus maybe one or
>>> two standbys) that don’t “share” any data. What you could do, in theory,
>>> is literally select all the data in the entire cluster and simply dump it
>>> to a file—but this could take hours, days, or even weeks to complete,
>>> depending on the size of your data, and then simply re-load it. This is
>>> probably not a great solution, but hey—maybe it will work for you.
>>>
>>> Netflix (thankfully) has posted a lot of their operational observations
>>> and what not, including their utility Priam. In their documentation, they
>>> include some overviews of what they use:
>>> https://github.com/Netflix/Priam/wiki/Backups
>>>
>>> Hope this helps!
>>>
>>> Andrew
>>>
>>> On June 12, 2014 at 6:18:57 AM, Jack Krupansky (jack@basetechnology.com)
>>> wrote:
>>>
>>> The doc for backing up – and restoring – Cassandra is here:
>>>
>>> http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_backup_restore_c.html
>>>
>>> That doesn’t tell you how to move the “snapshot” to or from tape, but a
>>> snapshot is the starting point for backing up Cassandra.
>>>
>>> -- Jack Krupansky
>>>
>>> *From:* Camacho, Maria (NSN - FI/Espoo) <ma...@nsn.com>
>>> *Sent:* Thursday, June 12, 2014 4:57 AM
>>> *To:* user@cassandra.apache.org
>>> *Subject:* Backup Cassandra to
>>>
>>>
>>> Hi there,
>>>
>>>
>>>
>>> I'm trying to find information/instructions about backing up and
>>> restoring a Cassandra DB to and from a tape unit.
>>>
>>>
>>>
>>> I was hopping someone in this forum could help me with this since I
>>> could not find anything useful in Google :(
>>>
>>>
>>>
>>> Thanks in advance,
>>>
>>> Maria
>>>
>>>
>>>
>>>
>>
>
Re: Backup Cassandra to
Posted by Jeremy Jongsma <je...@barchart.com>.
That will not necessarily scale, and I wouldn't recommend it - your "backup
node" will need as much disk space as an entire replica of the cluster
data. For a cluster with a couple of nodes that may be OK, for dozens of
nodes, probably not. You also lose the ability to restore individual nodes
- the only way to replace a dead node is with a full repair.
On Thu, Jun 12, 2014 at 1:38 PM, Jabbar Azam <aj...@gmail.com> wrote:
> There is another way. You create a cassandra node in it's own datacentre,
> then any changes going to the main cluster will be replicated to this node.
> You can backup from this node. In the event of a disaster the data from
> both clusters and wiped and then replayed to the individual node. The data
> will then be replicated to the main cluster.
>
> This will also work for the case when the main cluster increases or
> decreases in size.
>
> Thanks
>
> Jabbar Azam
>
>
> On 12 June 2014 18:27, Andrew <re...@gmail.com> wrote:
>
>> There isn’t a lot of “actual documentation” on the act of backing up, but
>> I did research for my own company into the act of backing up and
>> unfortunately, you’re not going to have a similar setup as Oracle. There
>> are reasons for this, however.
>>
>> If you have more than one replica of the data, that means each node in
>> the cluster will likely be holding it’s own unique set of data. So you
>> would need to back up the ENTIRE set of nodes in order to get an accurate
>> snapshot. Likewise, you would need to restore it to the cluster of the
>> same size in order to restore it (and then run refresh to tell Cassandra to
>> reload the tables from disk).
>>
>> Copying the snapshots is easy—it’s just a bunch of files in your data
>> directory. It’s even smaller if you use incremental snapshots. I’ll
>> admit, I’m no expert on tape drives, but I’d imagine it’s as easy as
>> copy/pasting the snapshots to the drive (or whatever the equivalent tape
>> drive operation is).
>>
>> What you (and I, admittedly) would really like to see is a way to back up
>> all the logical *data*, and then simply replay it. This is possible on
>> Oracle because it’s typically restricted to either one (plus maybe one or
>> two standbys) that don’t “share” any data. What you could do, in theory,
>> is literally select all the data in the entire cluster and simply dump it
>> to a file—but this could take hours, days, or even weeks to complete,
>> depending on the size of your data, and then simply re-load it. This is
>> probably not a great solution, but hey—maybe it will work for you.
>>
>> Netflix (thankfully) has posted a lot of their operational observations
>> and what not, including their utility Priam. In their documentation, they
>> include some overviews of what they use:
>> https://github.com/Netflix/Priam/wiki/Backups
>>
>> Hope this helps!
>>
>> Andrew
>>
>> On June 12, 2014 at 6:18:57 AM, Jack Krupansky (jack@basetechnology.com)
>> wrote:
>>
>> The doc for backing up – and restoring – Cassandra is here:
>>
>> http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_backup_restore_c.html
>>
>> That doesn’t tell you how to move the “snapshot” to or from tape, but a
>> snapshot is the starting point for backing up Cassandra.
>>
>> -- Jack Krupansky
>>
>> *From:* Camacho, Maria (NSN - FI/Espoo) <ma...@nsn.com>
>> *Sent:* Thursday, June 12, 2014 4:57 AM
>> *To:* user@cassandra.apache.org
>> *Subject:* Backup Cassandra to
>>
>>
>> Hi there,
>>
>>
>>
>> I'm trying to find information/instructions about backing up and
>> restoring a Cassandra DB to and from a tape unit.
>>
>>
>>
>> I was hopping someone in this forum could help me with this since I
>> could not find anything useful in Google :(
>>
>>
>>
>> Thanks in advance,
>>
>> Maria
>>
>>
>>
>>
>
Re: Backup Cassandra to
Posted by Jabbar Azam <aj...@gmail.com>.
There is another way. You create a cassandra node in it's own datacentre,
then any changes going to the main cluster will be replicated to this node.
You can backup from this node. In the event of a disaster the data from
both clusters and wiped and then replayed to the individual node. The data
will then be replicated to the main cluster.
This will also work for the case when the main cluster increases or
decreases in size.
Thanks
Jabbar Azam
On 12 June 2014 18:27, Andrew <re...@gmail.com> wrote:
> There isn’t a lot of “actual documentation” on the act of backing up, but
> I did research for my own company into the act of backing up and
> unfortunately, you’re not going to have a similar setup as Oracle. There
> are reasons for this, however.
>
> If you have more than one replica of the data, that means each node in the
> cluster will likely be holding it’s own unique set of data. So you would
> need to back up the ENTIRE set of nodes in order to get an accurate
> snapshot. Likewise, you would need to restore it to the cluster of the
> same size in order to restore it (and then run refresh to tell Cassandra to
> reload the tables from disk).
>
> Copying the snapshots is easy—it’s just a bunch of files in your data
> directory. It’s even smaller if you use incremental snapshots. I’ll
> admit, I’m no expert on tape drives, but I’d imagine it’s as easy as
> copy/pasting the snapshots to the drive (or whatever the equivalent tape
> drive operation is).
>
> What you (and I, admittedly) would really like to see is a way to back up
> all the logical *data*, and then simply replay it. This is possible on
> Oracle because it’s typically restricted to either one (plus maybe one or
> two standbys) that don’t “share” any data. What you could do, in theory,
> is literally select all the data in the entire cluster and simply dump it
> to a file—but this could take hours, days, or even weeks to complete,
> depending on the size of your data, and then simply re-load it. This is
> probably not a great solution, but hey—maybe it will work for you.
>
> Netflix (thankfully) has posted a lot of their operational observations
> and what not, including their utility Priam. In their documentation, they
> include some overviews of what they use:
> https://github.com/Netflix/Priam/wiki/Backups
>
> Hope this helps!
>
> Andrew
>
> On June 12, 2014 at 6:18:57 AM, Jack Krupansky (jack@basetechnology.com)
> wrote:
>
> The doc for backing up – and restoring – Cassandra is here:
>
> http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_backup_restore_c.html
>
> That doesn’t tell you how to move the “snapshot” to or from tape, but a
> snapshot is the starting point for backing up Cassandra.
>
> -- Jack Krupansky
>
> *From:* Camacho, Maria (NSN - FI/Espoo) <ma...@nsn.com>
> *Sent:* Thursday, June 12, 2014 4:57 AM
> *To:* user@cassandra.apache.org
> *Subject:* Backup Cassandra to
>
>
> Hi there,
>
>
>
> I'm trying to find information/instructions about backing up and
> restoring a Cassandra DB to and from a tape unit.
>
>
>
> I was hopping someone in this forum could help me with this since I could
> not find anything useful in Google :(
>
>
>
> Thanks in advance,
>
> Maria
>
>
>
>
Re: Backup Cassandra to
Posted by Andrew <re...@gmail.com>.
There isn’t a lot of “actual documentation” on the act of backing up, but I did research for my own company into the act of backing up and unfortunately, you’re not going to have a similar setup as Oracle. There are reasons for this, however.
If you have more than one replica of the data, that means each node in the cluster will likely be holding it’s own unique set of data. So you would need to back up the ENTIRE set of nodes in order to get an accurate snapshot. Likewise, you would need to restore it to the cluster of the same size in order to restore it (and then run refresh to tell Cassandra to reload the tables from disk).
Copying the snapshots is easy—it’s just a bunch of files in your data directory. It’s even smaller if you use incremental snapshots. I’ll admit, I’m no expert on tape drives, but I’d imagine it’s as easy as copy/pasting the snapshots to the drive (or whatever the equivalent tape drive operation is).
What you (and I, admittedly) would really like to see is a way to back up all the logical *data*, and then simply replay it. This is possible on Oracle because it’s typically restricted to either one (plus maybe one or two standbys) that don’t “share” any data. What you could do, in theory, is literally select all the data in the entire cluster and simply dump it to a file—but this could take hours, days, or even weeks to complete, depending on the size of your data, and then simply re-load it. This is probably not a great solution, but hey—maybe it will work for you.
Netflix (thankfully) has posted a lot of their operational observations and what not, including their utility Priam. In their documentation, they include some overviews of what they use: https://github.com/Netflix/Priam/wiki/Backups
Hope this helps!
Andrew
On June 12, 2014 at 6:18:57 AM, Jack Krupansky (jack@basetechnology.com) wrote:
The doc for backing up – and restoring – Cassandra is here:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_backup_restore_c.html
That doesn’t tell you how to move the “snapshot” to or from tape, but a snapshot is the starting point for backing up Cassandra.
-- Jack Krupansky
From: Camacho, Maria (NSN - FI/Espoo)
Sent: Thursday, June 12, 2014 4:57 AM
To: user@cassandra.apache.org
Subject: Backup Cassandra to
Hi there,
I'm trying to find information/instructions about backing up and restoring a Cassandra DB to and from a tape unit.
I was hopping someone in this forum could help me with this since I could not find anything useful in Google :(
Thanks in advance,
Maria
Re: Backup Cassandra to
Posted by Jack Krupansky <ja...@basetechnology.com>.
The doc for backing up – and restoring – Cassandra is here:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_backup_restore_c.html
That doesn’t tell you how to move the “snapshot” to or from tape, but a snapshot is the starting point for backing up Cassandra.
-- Jack Krupansky
From: Camacho, Maria (NSN - FI/Espoo)
Sent: Thursday, June 12, 2014 4:57 AM
To: user@cassandra.apache.org
Subject: Backup Cassandra to
Hi there,
I'm trying to find information/instructions about backing up and restoring a Cassandra DB to and from a tape unit.
I was hopping someone in this forum could help me with this since I could not find anything useful in Google :(
Thanks in advance,
Maria
RE: Backup Cassandra to
Posted by Romain HARDOUIN <ro...@urssaf.fr>.
So you have to install a backup client on each Cassandra node. If the
NetBackup client behaves like EMC Networker, beware the resources
utilization (data deduplication, compression). You could have to boost
CPUs and RAM (+2GB) of each nodes.
Try with one node: make a snapshot with nodetool and configure NetBackup
so the backup client sends data to your tape library or virtual tape
library. And of course, try to restore ;-)
The tricky part is not Cassandra itself, it's to follow NetBackup (or
whatever) best practices.
"Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com> a écrit sur
12/06/2014 13:12:18 :
> De : "Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com>
> A : "user@cassandra.apache.org" <us...@cassandra.apache.org>,
> Date : 12/06/2014 13:12
> Objet : RE: Backup Cassandra to
>
> Hi,
> Thanks for the quick response Romain.
>
> We would like to avoid using extra disk space, so no DAS/SAN.
> We are more interested in achieving something like what is now being
> done with Oracle – Symantec’s NetBackup is used to backup directly
> to tape, no intermediate storage is needed.
>
> It could be NetBackup or whatever product supported by Cassandra
> that writes the backup on tape without storing it on disk first.
>
> Regards,
> Maria
RE: Backup Cassandra to
Posted by "Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com>.
Hi,
Thanks for the quick response Romain.
We would like to avoid using extra disk space, so no DAS/SAN.
We are more interested in achieving something like what is now being done with Oracle - Symantec's NetBackup is used to backup directly to tape, no intermediate storage is needed.
It could be NetBackup or whatever product supported by Cassandra that writes the backup on tape without storing it on disk first.
Regards,
Maria
From: ext Romain HARDOUIN [mailto:romain.hardouin@urssaf.fr]
Sent: Thursday, June 12, 2014 12:32 PM
To: user@cassandra.apache.org
Subject: RE: Backup Cassandra to
Hi Maria,
It depends which backup software and hardware you plan to use. Do you store your data on DAS or SAN?
Some hints regarding Cassandra is either to drain the node to backup or take a Cassandra snapshot and then to backup this snapshot.
We backup our data on tape but we also store our data on SAN, so it's pretty vendor specific.
Best,
Romain
"Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com>> a écrit sur 12/06/2014 10:57:06 :
> De : "Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com>>
> A : "user@cassandra.apache.org<ma...@cassandra.apache.org>" <us...@cassandra.apache.org>>,
> Date : 12/06/2014 10:57
> Objet : Backup Cassandra to
>
> Hi there,
>
> I'm trying to find information/instructions about backing up and
> restoring a Cassandra DB to and from a tape unit.
>
> I was hopping someone in this forum could help me with this since I
> could not find anything useful in Google :(
>
> Thanks in advance,
> Maria
>
RE: Backup Cassandra to
Posted by Romain HARDOUIN <ro...@urssaf.fr>.
Hi Maria,
It depends which backup software and hardware you plan to use. Do you
store your data on DAS or SAN?
Some hints regarding Cassandra is either to drain the node to backup or
take a Cassandra snapshot and then to backup this snapshot.
We backup our data on tape but we also store our data on SAN, so it's
pretty vendor specific.
Best,
Romain
"Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com> a écrit sur
12/06/2014 10:57:06 :
> De : "Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com>
> A : "user@cassandra.apache.org" <us...@cassandra.apache.org>,
> Date : 12/06/2014 10:57
> Objet : Backup Cassandra to
>
> Hi there,
>
> I'm trying to find information/instructions about backing up and
> restoring a Cassandra DB to and from a tape unit.
>
> I was hopping someone in this forum could help me with this since I
> could not find anything useful in Google :(
>
> Thanks in advance,
> Maria
>
Backup Cassandra to
Posted by "Camacho, Maria (NSN - FI/Espoo)" <ma...@nsn.com>.
Hi there,
I'm trying to find information/instructions about backing up and restoring a Cassandra DB to and from a tape unit.
I was hopping someone in this forum could help me with this since I could not find anything useful in Google :(
Thanks in advance,
Maria