STAR,
http://www.fokus.gmd.de/resear...ling/private/star.html
AMANDA,
http://www.amanda.org/
OTHERS:
http://www.linux.org/apps/all/...nistration/Backup.html
Is it possible to back up a single application and reinstall it after an O/S upgrade? Sort of, usually.
Check if the application is installed in
RPM.
rpm -qf /bin/someprogram
....and repeat that for the various files you know the application uses. If you discover that it is giving you the name(s) of various RPM packages then you can do something like this to find many of the files in the package:
[root ~]# rpm -qf /bin/mail
mailx-8.1.1-48.fc9.x86_64
[root ~]# rpm -ql mailx
/bin/mail
/etc/mail.rc
/usr/bin/Mail
/usr/share/doc/mailx-8.1.1
/usr/share/doc/mailx-8.1.1/copyright
/usr/share/mailx
/usr/share/mailx/mail.help
/usr/share/mailx/mail.tildehelp
/usr/share/man/man1/Mail.1.gz
/usr/share/man/man1/mail.1.gz
Then you can tar up / back up those files and restore then on your new system and see what you get. Typically there may be some dependencies on various other packages / system libraries that you can identify:
# rpm --query --requires mailx
config(mailx) = 8.1.1-48.fc9
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.7)(64bit)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
# ldd /bin/mail
linux-vdso.so.1 => ()
libc.so.6 => /lib64/libc.so.6 ()
/lib64/ld-linux-x86-64.so.2 ()
...and realize that you'll have to install the various compatibility library versions and other dependency packages that are required by that package on your new system which sometimes is not a problem and sometimes is a problem.
Try to identity the configuration files relating to the package / program, if any, like anything in /etc, /etc/init.d, /etc/sysconfig or whatever, and be sure to save those.
If the package isn't listed in / installed via RPM then often all you can hope for is to find manually a list of the other files / programs / libraries on which the program depends and back those up individually. Hopefully most of them are in a few consistent locations like /opt/whatever/thisprogram, /usr/local/thisprogram, /usr/share/thisprogram, /usr/share/doc/thisprogram, /etc/thisprogram, /etc/init.d/thisprogram, etc.
Use ldd to identify any dynamic link library version dependencies, strings /somewhere/someprogram | less to look for references to other file(s) that may be needed for operation, man someprogram to see what other programs / files are needed, et. al.
If it is too painful to do you can always run a new Fedora version on a reasonable PC and then run your existing Fedora 2 image in a virtual machine under that to have acces to those orphaned programs.
Originally posted by: Excelsior
I am in a community college medical program and we had a computer and appropriate software donated to us. This included a VXA-2 tape backup drive. The computer is a Dell Xeon running Fedora 2 core. The computer runs OK but I am having some trouble getting the VXA-2 to work. It is discovered by the SCSI controller at bootup, and even in the hardware list in Fedora, but neither kdat or kdiskfree will read it.
I saw that Exabyte has a linux utility and firmware updates, so I am gonna try those. Any ideas for freeware tape backup software though?