![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
"Cesar Inacio Martins" <cesar_inacio_martins (AT) yahoo (DOT) com.br> wrote in message news:mailman.667.1267739579.6236.informix-list (AT) iiug (DOT) org... Hi, Someone use LVM snapshot on linux with Informix (using onmode -c block)? There some issues with it? or is simple like Informix, just works... Do you, or your friend, have the Informix chunks as raw devices, or as regular files on a file system? |
#4
| |||
| |||
|
|
"Cesar Inacio Martins" <cesar_inacio_martins (AT) yahoo (DOT) com.br> wrote in message news:mailman.667.1267739579.6236.informix-list (AT) iiug (DOT) org... Hi, Someone use LVM snapshot on linux with Informix (using onmode -c block)? There some issues with it? or is simple like Informix, just works... Do you, or your friend, have the Informix chunks as raw devices, or as regular files on a file system? |
#5
| |||
| |||
|
|
We have the 2 situations, one instance running with RAW (configured with raw module) and other instance (differ machine) as cooked. And yes, ALL LVs (used by the database) will be snaped... |
#6
| |||
| |||
|
|
From: neil.truby (AT) ardenta (DOT) com Subject: Re: Linux LVM snapshot Date: Fri, 5 Mar 2010 12:44:30 +0000 To: informix-list (AT) iiug (DOT) org "Cesar Inacio Martins" <cesar_inacio_martins (AT) yahoo (DOT) com.br> wrote in message news:mailman.671.1267786544.6236.informix-list (AT) iiug (DOT) org... Hi Neil, We have the 2 situations, one instance running with RAW (configured with raw module) and other instance (differ machine) as cooked. And yes, ALL LVs (used by the database) will be snaped... Provided all the LVs are snapped *** WITHIN THE SAME ONMODE -C BLOCK ... **** The raw one will be fine. The cooked one will be unpredictable. Interesting. How long does a snapshot take? |
#7
| |||
| |||
|
|
"Cesar Inacio Martins" <cesar_inacio_martins (AT) yahoo (DOT) com.br> wrote in message news:mailman.671.1267786544.6236.informix-list (AT) iiug (DOT) org... Hi Neil, We have the 2 situations, one instance running with RAW (configured with raw module) and other instance (differ machine) as cooked. And yes, ALL LVs (used by the database) will be snaped... Provided all the LVs are snapped *** WITHIN THE SAME ONMODE -C BLOCK ... **** The raw one will be fine. The cooked one will be unpredictable. _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#8
| |||
| |||
|
|
From: neil.truby (AT) ardenta (DOT) com Subject: Re: Linux LVM snapshot Date: Fri, 5 Mar 2010 13:31:20 +0000 To: informix-list (AT) iiug (DOT) org Interesting. How long does a snapshot take? Should just be a few seconds. But if the db is blocked it doesn't really matter how long it takes, save of course the impact on the users of the source system! |
#9
| |||
| |||
|
|
"Art Kagel" <art.kagel (AT) gmail (DOT) com> wrote in message news:mailman.676.1267797083.6236.informix-list (AT) iiug (DOT) org... Cooked should be OK also. IDS always opens COOKED chunks with either the O_DIRECT or O_SYNC flags so everything is sync'd to disk immediately and the IO doesn't return until the write is complete. So, once the onmode -c BLOCK returns and IDS reports that the engine is blocked even COOKED chunks should be safe to snap-copy. |
#10
| ||||
| ||||
|
|
Correct me if I am wrong but with a SAN snapshot you can only recover to the point of the last snapshot, but with HDR/RSS you always have a backup system that is in sync with the Primary and can be made Primary in a few seconds with a few simple onmode commands or automatically with oncmsm and the failover arbitrator. Does a SAN replicated image solve this problem and is it just as good as HDR as far as recoverability is concerned? (serious question, I don't know the answer) |
|
With HDR/RSS you also get the benefit of a read only secondary (or multiple secondaries) for reporting and can use updateable secondaries if you want to make all of your HDR nodes appear updateable (all updates will be sent to the primary, so this only gives the impression that all nodes are updateable). |
|
Add on top of this the benefit of HDR being an Informix feature that works well with the application side (I'm thinking mostly about connection redirection via sqlhost groups or the connection manager). In my experience HDR is pretty hands off once it is up and running, so the administration overhead is pretty low. Also, HDR is something you have control over vs. a SAN based solution where a sysadmin or storage admin may have control. |
|
When we migrated to a new storage solution, the SAN snapshot and replication stuff required an additional license which we did not purchase. |
![]() |
| Thread Tools | |
| Display Modes | |
| |