CentOS - Jun 2016 - remote backup

Gordon Messmer wrote:
> On 06/09/2016 11:43 AM, Valeri Galtsev wrote:
>> When databases are concerned, I would never rely on a snapshot of their
>> storage files. Either stop relevant daemon(s), then do fs snapshot, or
>> better though do dbdump and restore databases from dump when you need
to
>> restore it.
>
> Dumping and restoring files can be *really* slow, so "better" is
highly
> subjective.
>
> Instead, you could quiesce your databases to get a filesystem snapshot.
> I wrote a framework for doing this that is filesystem and application
> agnostic, which I mentioned in a previous message.
That's what "middle of the night maintenance window" is for.

       mark

On 6/9/2016 1:16 PM, m.roth at 5-cent.us wrote:
> That's what "middle of the night maintenance window" is for.
in today's 24/7 global business world, there is no middle of the night, 
its midday *somewhere*.



-- 
john r pierce, recycling bits in santa cruz

John R Pierce wrote:
> On 6/9/2016 1:16 PM, m.roth at 5-cent.us wrote:
>> That's what "middle of the night maintenance window" is
for.
>
> in today's 24/7 global business world, there is no middle of the night,
> its midday *somewhere*.
>
You pick the least buy day/time. For example, when I was supporting the
City of Chicago 911 system, 16 years ago, they'd let us schedule software
upgrades for Mon night, between 02:00  and 06:00. Tuesday, and then
Thursday, were second and third choice - that's when there were the least
number of calls. And allow me to venture to suggest that life-or-death
calls to a 911 ctr (the calltakers went back to cards during that time)
wasn't more important than world-wide business....

Besides, if it's that big a business, management *really* needs to spring
for a hot spare complete system, to deal with hardware outages, and there
should be mirrored d/bs, and *those* could be taken down, copied, and then
brought back online and all the transactions that had been done while it
was down updated to the backup.

        mark