I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
Thanks for insights.
Scott
I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
use amanda, www.amanda.org
it rocks
On Tuesday 29 January 2008 12:43:48 Tom Brown wrote:
I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
use amanda, www.amanda.org
it rocks
Or have a look at BackupPC http://backuppc.sourceforge.net/
Tony
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, 29 Jan 2008, Tom Brown wrote:
I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
use amanda, www.amanda.org
it rocks
My fundamental question is why dump claims it cannot access what I want it to back up. What's to say other solutions - Amanda, etc, will work any better? I want to know how to resolve the source problem before looking into other products. How will BackupPC or Amanda do any better?
Thanks.
Scott
My fundamental question is why dump claims it cannot access what I want it to back up. What's to say other solutions - Amanda, etc, will work any better? I want to know how to resolve the source problem before looking into other products. How will BackupPC or Amanda do any better?
well i have not come accross the error(s) you listed when using amanda to do the backup - You posted the quetion to ask for advice and the advice that i would give to solve your problem would be to use amanda to run the backup, which may or may not call dump, as for me this is a known good configuration.
On 29/01/2008 13:35, Scott Ehrlich wrote:
On Tue, 29 Jan 2008, Tom Brown wrote:
I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
use amanda, www.amanda.org
it rocks
My fundamental question is why dump claims it cannot access what I want it to back up. What's to say other solutions - Amanda, etc, will work any better? I want to know how to resolve the source problem before looking into other products. How will BackupPC or Amanda do any better?
Thanks.
Scott
I've never used dump before but reading the manpage seems to indicate that it's a tool for backing up an ext2/3 filesystem, not a CIFS filesystem which is essentialy how a Samba mount is seen by the kernel on your office machine. If I am correct here then I doubt it would work over NFS either.
I can put my vote in for amanda as a good alternative.
cheers Luke
Scott Ehrlich wrote:
I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
use amanda, www.amanda.org
it rocks
My fundamental question is why dump claims it cannot access what I want it to back up. What's to say other solutions - Amanda, etc, will work any better? I want to know how to resolve the source problem before looking into other products. How will BackupPC or Amanda do any better?
Dump is file-system oriented and won't handle remote-mounted directories. You can use file-oriented tar on remote mounts - or smbtar on remote samba/windows shares without mounting them, or use ssh to run some command like tar or dump remotely and return the output.
Amanda works by having a remote client do the work and return the backup data and can use tar or dump. Backuppc uses ssh with tar or rsync, or smbtar or rsync against a remote copy in daemon mode, thus not needing a dedicated remote agent.
Amanda is more tape-oriented, but can also archive to disk. Backuppc is best at archiving to disk (with some clever tricks to reduce the space needed) but can also write to tape.
Scott Ehrlich wrote:
On Tue, 29 Jan 2008, Tom Brown wrote:
I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
use amanda, www.amanda.org
it rocks
My fundamental question is why dump claims it cannot access what I want it to back up. What's to say other solutions - Amanda, etc, will work any better? I want to know how to resolve the source problem before looking into other products. How will BackupPC or Amanda do any better?
I've never had dump try to access anything other than the physical or logical partition. So if you ran
dump 0avf /dev/null /
on your machine(s), it tries to backup remote mounted filesystems? Something's not right . . . .
on 1/29/2008 5:35 AM Scott Ehrlich spake the following:
On Tue, 29 Jan 2008, Tom Brown wrote:
I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
use amanda, www.amanda.org
it rocks
My fundamental question is why dump claims it cannot access what I want it to back up. What's to say other solutions - Amanda, etc, will work any better? I want to know how to resolve the source problem before looking into other products. How will BackupPC or Amanda do any better?
Thanks.
Scott
I do not believe that dump will work over smb. I'm not sure that you can dump over nfs reliably. You might want run dump on the remote systems and have the destination files on smb mounted file system. Then you can tar those to tape (or cpio or whatever you choose). Or share the tape drive over iSCSI and dump to that.
Scott Ehrlich wrote:
I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office.
I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another successful backup I have going on a system with local filesystems. But for remote filesystems, I get errors of File Cannot Be Accessed (//remote_system/subdir) which does exist as an smb mounted filesystem.
I'd use NFS, but I would like a bit more control and some level of encryption for the user authentication and data being transferred.
If a direct dump of remote smb filesystems isn't possible, I may opt to have each system perform their own local dumps, then run a script locally on the tape-connected machine to dump those local dumps, or copy the dumps locally then dump them to tape.
If nothing else works, I can always install Windows XP and use Windows backup program, but I'd really like to try and get this going under Linux before going that route.
Thanks for insights.
Scott
What you could do is to dump from the remote machine to the main backup machine. For this to work I work with ssh keys (no password needed). The example assumes the backup is started from the remote host. But in principle it can also be initiated from the backup server using ssh.
SRC_SERVER=this_hostname BAK_SERVER=backup_server DATE=$(date +%Y%m%d) dumplevel=0 export RSH=ssh
ssh $BAK_SERVER mkdir -p /backup/${SRC_SERVER}/${DATE}_${dumplevel} # file needs to exist backup_file=/backup/somefile ssh $BAK_SERVER touch ${backup_file} dump -${dumplevel} -u -z -f $BAK_SERVER:${backup_file} /dev/VolGroup00/VolGroup00
Theo
dump works at the device level, dumping the raw block device by interpreting the ext2/3 structures there. If you pass it a directory, it converts it to the device mounted there and dumps the device. restore, on the other hand, operates at the filesystem level.
You don't need to be root to dump. Your dump script can run as anyone in the "disk" group, the default group of disk block devices, which by default have group read access. You do need to be root to verify, though, because restore is going through the filesystem.
I back my CentOS box up to a USB-attached hard drive on a Windows XP workstation mounted via cifs. This is effectively a "push" system. After the backup, I run "restore -C" to verify that the data got there successfully.
During the verify pass, I remount the filesystem with the noatime option so that reading it to compare to the "tape" image on the USB drive does not change the atimes. I then re-enable atime when the verify is done. (I use atime to watch for dead email accounts and so that tmpwatch will work correctly.)
dump has its own home page and mailing list, and the author is very helpful with support.