On 22/08/11 14:56, Robert Porter wrote:
The snapshot disk space only needs to hold the amount of the changed data -
not the whole filesystem. To the applications, it appears that a copy was
made, but actually writes are being held behind the scenes. Don't think I'm
explaining this well
Snapshotting doesn't get rid of mirroring just the need to break/merge them.
I'd still suggest using mirrors. The risk of disk failure is too great. Guess
you could use some other level of RAID to get there but it's hard to beat
spindles plus mirrors (0+1) for databases. In fact our snapshot
Thanks to everyone for some very interesting points. I am particularly
intrigued by Stuart's handling of dictionaries using triggers. One particular
challenge I may face is one particular hashed file (not a dictionary) which
contains 2 1/2 million records that are under source control today.
Here is some Pie in the Sky info for ya...
btrfs or Butter FS is being developed by Oracle for Linux.
Its one of the reasons Oracle shutdown the development of ZFS when they
bought Sun.
(ZFS has many of those snapshotting features you are talking about).
So now you have all of these spinoffs
On a relevant note. I was always told that:
The best way to get an accurate backup on U2 is to:
-Pause the writes
-Do a logical volume snapshot (*nix only)
-Resume the writes
-Let the logical volume snapshot finish copying off to your backup space to
disk.
-On top of that you should still do a
in a header with post-data I have to create the header-information like
this:
Content-type: text/xml;charset=UTF-8
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg,
*; q=.2, */*; q=.2
When creating it with setRequestHeader or with addRequestParamete I
will receive the
What source are you keeping that has 2.5 million records
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Perry Taylor
Sent: Wednesday, 24 August 2011 01:39
To: U2 Users List
Subject: Re: [U2] [UV] Microsoft Team
Not source but code lists which are updated at different intervals. Some
examples: ZIP, CPT, ICD9, etc.
- Original Message -
From: Boydell, Stuart [mailto:stuart.boyd...@spotless.com.au]
Sent: Tuesday, August 23, 2011 07:49 PM
To: U2 Users List u2-users@listserver.u2ug.org
Subject: Re:
Hi Perry,
I'd strongly suggest normal backup would be a better strategy for those items.
Source Control is really designed for those things that you use to build a
system. Code, parameters, schema (file dictionary) generation scripts, etc.
The data for that system would typically *not* be
