On Fri, Dec 17, 2010 at 8:44 AM, Matt Shields <m...@mattshields.org> wrote:
> On Fri, Dec 17, 2010 at 8:22 AM, Chris O'Connell <omegah...@gmail.com>wrote: > >> Hey Mark, >> >> IMO I think there are a few important features: >> 1. The backups must be mountable, allowing for file browsing and single >> file restoration. >> 2. The backup should NOT be file based, it should be image based. >> 3. Encrypted backups. I want the backups to be encrypted and I want the >> encryption to be self contained in the backup. This means that you can >> take >> the backup to ANY computer with the backup software and open the backup >> file >> by entering a password. >> >> Acronis has all of these features, but it's expensive and I don't believe >> the software will run on these linux nas devices you've specified. >> >> --Chris >> >> On Fri, Dec 17, 2010 at 8:10 AM, Mark Woodward <ma...@mohawksoft.com> >> wrote: >> >> > While I've got some free time on my hands, I decided to start work on a >> > project. At its core, it is very much like a standard backup system. >> > What makes it different from a regular backup is what you do with the >> > data retrieved after the backup. I know it is a long shot or even a >> > fools errand to start anything so pedantic and well traveled, but there >> > is a specific need that I believe has been identified, but requires >> > "backup" done in a specific manner. Anyway, who knows? I'm already >> > testing and using some of the core pieces and I have to say, I like it. >> > >> > My target OS are Windows, MacOS, and Linux. It will run on desktops, >> > servers, and even some of these little NAS boxes that run Linux. >> > >> > My question for you guys is what do you *want* in a backup. We've all >> > used these feature laden things that are out there, 99% of which is >> > pointless. What are "must haves?" What is something you've wanted but >> > can't find? What are features that are most pointless and why? >> > _______________________________________________ >> > Discuss mailing list >> > Discuss@blu.org >> > http://lists.blu.org/mailman/listinfo/discuss >> > >> _______________________________________________ >> Discuss mailing list >> Discuss@blu.org >> http://lists.blu.org/mailman/listinfo/discuss >> > > The ability for it to work not only through it's native communication > method (usually custom port/protocol), but also be able to run over an SSH > tunnel. Sometimes you don't want to open up that port to the outside world > even if it is encrypted, so being able to tell it to start an SSH tunnel. > Have that be part of the configuration where you can specify the > username/password or keypair to let it establish it's own SSH tunnel. Also, > be able to specify a bandwidth limit on transfers. > > Ability to do full, differentials and incremental backups. > > Like Chris mentioned, the ability to easily browse the backups and pull out > specific files/directories. > > Since it's not a good practice to touch the raw files for MySQL (probably > not for PostgreSQL either), be able to exclude path's. But also be able to > specify there is a database and do a db backup. > > -matt > > > Another useful feature is that the system should automatically verify the backups to make sure they are good and alert you when there's a problem. Nothing like needing to go back to your backups and realizing that they haven't been running for months. -matt _______________________________________________ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
