[Ubuntu-PH] Help : Ubuntu Recycle Bin

Zak B. Elep zakame at ubuntu.com
Wed Jan 16 09:05:29 UTC 2008


On Jan 16, 2008 4:46 PM, botp <botpena at gmail.com> wrote:
> On Jan 16, 2008 4:22 PM, Zak B. Elep <zakame at ubuntu.com> wrote:
> > This is where another good tool for sysadmins come in: a source
> > control system.  Distributed SCMs make the tasks of script writing and
> > backup even easier, even more than relying on libtrash.
>
> indeed. And now, you'll have to backup your control repository, too
> (just imagine if it gets hosed. para tayong nasunogan). as always,

DSCMs don't really have a notion of a `control' repository that's
hardcoded into the system; rather, such is left as something for the
developer (or sysadmin) to decide.  Every DSCM repository is a clone
of each other, differing only by local modifications (which, for
prudent devs, should typically be in a different branch.)  Because of
this model, DSCM repositories are easily transportable, and can be put
on on FTP or HTTP as Real Men's Backup (as Linus would say it. :P)
(Nowadays, there's also a third option for remote backups as well:
Amazon S3.)

> backup, backup, and backup the backup, too, ie remotely.  for
> configurers/developers, dali lang backup kasi konti lang text
> programs/config. but for admins that administer application/database
> servers, backup is everything. hindi puwede e-sugal.  cliche: better
> safe than sorry. for companies, a backup is a life/company saver. If
> you lose it, you may lose a job too... quite a fact...

Pretty much hitting the nail in the head there.  Some even go so far
as to implement continuous archival and restore (like those found in
database write-ahead-log backups) to keep backups up-to-date with
minimal data loss.

Cheers,

Zakame


-- 
Zak B. Elep  ||  http://zakame.spunge.org
zakame at ubuntu.com  ||  zakame at spunge.org  ||  zakame at morphlabs.com
1486 7957 454D E529 E4F1  F75E 5787 B1FD FA53 851D




More information about the ubuntu-ph mailing list