Suggestions for new functionality

From The Open Source Backup Wiki (Amanda, MySQL Backup, BackupPC)

Jump to: navigation, search

Note: All suggestions below are published verbatim. Many requests are similar or the same, but we publish all suggestions anyway to demonstrate relative demand for functionality.

  • GUI and reporting
    • GUI to manage the backup on the server and GUI to recover files
    • Portable GUI, but not in Java please
    • no flames - a tk front end and a lot of python for website reports for managers
    • GUI similar to Retrospect
    • GUI for Windows
    • GUI for stats and running backup (easier for clients)
    • GUI for restore
    • GUI for restore
    • GUI for restore
    • GUI for configuring and setting tape jobs
    • GUI
    • GUI
    • GUI
    • GUI
    • GUI
    • Front end Gui for easy configurations
    • web GUI
    • Web or Mac or X-Win GUI
    • GUI
    • some sort of GUI, e.g. web front end
    • Better user interface
    • GUI to restore files
    • Web GUI
    • Webinterface
    • GUI for restoring files
    • GUI
    • Better statistics output for visualizing data and a
    • Better reporting
    • its awfully good right now, maybe it is GUI time?
    • easier restore and index browse for end users
    • a nice GUI for YaST!
    • amplot is a bit crude
    • All the scripts I had to write myself: publish reports and statistics to a web page, send failure reports to client owners
  • Stability
    • stability
    • quit messing up the code
    • Making the 'bare metal' recovery work. It doesn't in 2.4.5
    • fix issues with 2.5.1 on Solaris 10
    • Clean up getfsent.c Yuch!
  • Scalability and performance
    • speed up
    • Restore speed improvement
    • Performance
    • multiple recovery streams from sets of tapes
  • Operating Systems support
    • windows client
    • VxFS support and
    • VSS integration
    • Exchange, Windows state and Oracle support
    • support for AFS
    • Real Windows client
    • VxFS support and
    • Open files support on Windows
    • Native windows client, no Cygwin hacks
    • Native windows client
    • Backup NT ACLs and we might convert a few thousand servers over!
    • Support for OS-X
    • Better support for backups over samba/cifs
    • better native Windows (would allow us to scrap our commercial Windows solution)
    • Samba compatibility, I had several problems with filenames (truncated filenames)
    • Backup of Windows registry and other system critical and open files
  • Database and applications support
    • NDMP support
    • MySQL plugin
    • Support for databases
    • direct support for MySQL
    • Lotus Domino backup from transaction logs
    • NDMP
    • Postgress support
    • Postgress support
  • Backup to disk improvements
    • Parallel writing to disk
    • snapshot support
    • dumping directly to disk
    • the amrecover to disk to automatically know where my hard drive dumps are
    • Automatic tape loading for vtape restoration
    • Make disk backup not like tape
    • block level continues backup with roll back to any point in time for any file
    • I would like more sensible options for backing up to disk rather than being limited to configuring vtapes. If the tape sizes are too big, then amanda thinks that it has more resources than it does, but if they are too small the full backup fails due to not enough disk space
    • better support for backup to disk
    • Holding disk backups, synthetic full backups (currently uses rsync)
    • backup to disk
  • General usability improvements
    • support for file names with spaces
    • centralized storage of exclude lists on the server
    • More complete exclude patterns for samba shares. Currently you can exclude one thing
    • plugins to start/stop servers to use snapshots
    • more client programs other than dump/tar, e.g. rsync like in backupPC
    • It would be nice to schedule a full backup on a weekend and incremental during the week in the same set
    • i18n
    • Client side pre-backup and post-backup scripts
    • easier integration of client side scripts,
    • integrated backup of Amanda DBs (curinfo and index dir)
    • easier configuration
    • Ease of use
    • Amanda self-backup, database backup and recovery if disaster. I use other backup servers to backup each other
    • Hardware compression estimations
    • 2.5.1 implemented my entire wish list (thanks!), but how about automatic verification of written tapes against holding disk or checksums
  • Tape and device management
    • automatically manage vtape space by deleting old backups
    • append to tapes for daily incrementals
    • append to tapes
    • Append to tape for better resource utilization.
    • Multiple backups per tape
    • Workable tape spanning on Solaris
    • proper archive tape support
    • More efficient use of tape
    • Spanning large filesystems to multiple tapes -- this is very important to me and I guess I'm going to have some work-around before very long
    • Simpler usage of tapes would be nice
    • Robust tape spanning
    • Tape usage metering
    • better support for tapes spanning several tapes
    • Ability to write to multiple tape drives at the same time
    • Direct support for DVD+RW
    • Autospan tapes, which sort of does happen but only if the DLE is less that one tape size. Currently I split up the disk into DLT less than one tape size. Support for larger than 4TB (holding disk etc..)
    • better support for spanning filesystems across tapes
    • better support for virtual tape changer
    • Seamless integration of vtapes and tapes (tiered backup/restores)
    • a way not to use holding disk without damaging tape/drive and at full speed
    • Backup spanning multiple tapes
    • Archiving
    • automatic read back of tapes would be cool, but really you've done just about everything we want!
    • Be able to make copies of backup tapes for off-site storage
  • Ease of initial configuration
    • Need easier configuration
    • Simplification of configuration tools
    • Simplicity of installation. I think the complex installation discourages a lot of people who don't really understand the full power of automated scheduling that is significantly different from other backup schemas
    • Improve setup
    • Change all/most of compiled-in options to be read from config file at runtime
    • configurable paths to external tools like tar without recompiling, convert all configurables to files, not compiled-in
    • easier to configure
  • Documentation
    • would someone please write a decent how to auto-generate labels?
    • Improve documentation
    • better examples for use
    • better documentation for 2.5.1
    • Documentation - provide a chapter describing the big picture. I had problems understanding what the components are doing
  • Ease of troubleshooting
    • Better diagnostics
    • tuning and performance tools and utilities
    • easier diagnostics to assist in identifying client software versions (such as differing tar's when one distro upgrades before another distro)
  • Security
    • Encryption (transmission and storage) to be more easily available. There are some hoops to jump through in order to enable it.
    • integrate encryption
    • less complex authentication
    • Tape encryption
    • backup and restore ext3 ACLs
  • Other
    • decoupling of dump and flush
    • Bare metal recovery and
    • amoverview was better in 2.4 -- I liked the daily matrix
    • Evaluation phase
    • dealing with changing files during backup, provide consistency
Personal tools