Back Ups

[longtom]

man rsync
http://www.samba.org/ftp/rsync/rsync.html

Thanks Joble and O-P.  My word - this is all a bit overwhelming ... but I guess after a study period of 6 months I will be able to make my first test backup over the lan ....

I see you have luckybackup open O-P.  I had a look at that earlier.  It is very easy to use indeed - alas I don't see a way to find a file or directory on a network.  The same applies to grsync.

I'd love to convert my file server from Windows, but that needs 2 prerequisites:

1. I need to be able to work whatever Linux has on offer.
2. It must be as solid as Cobian is right now on WinXP.

Why would I like change that file server if it's working?  Because it is there.  Sancho, give me the lance ... (gallops of in direction of the windmills ...)

[Old-Polack]

man rsync
http://www.samba.org/ftp/rsync/rsync.html

Thanks Joble and O-P.  My word - this is all a bit overwhelming ... but I guess after a study period of 6 months I will be able to make my first test backup over the lan ....

I see you have luckybackup open O-P.  I had a look at that earlier.  It is very easy to use indeed - alas I don't see a way to find a file or directory on a network.  The same applies to grsync.

I'd love to convert my file server from Windows, but that needs 2 prerequisites:

1. I need to be able to work whatever Linux has on offer.
2. It must be as solid as Cobian is right now on WinXP.

Why would I like change that file server if it's working?  Because it is there.  Sancho, give me the lance ... (gallops of in direction of the windmills ...)

If you have a Samba or other connection to whatever server you have, it has a mountpoint on your local machine where you see the files in question. Copying files or directories to them is simply a matter of directing the copy to that mount point, or a directory on the server that is seen from that mountpoint.

I have a mountpoint named /zbackup on this installation. At present a partition from one of my USB hard drives is mounted there. I could just as easily mount a share from a network connected server on /zbackup. Either way the lucky Backup path would be /zbackup/<somedirectoryname>, and lucky Backup couldn't care less if the final location of the backup is a local drive, a local lan server, or a connection to a server in Tennessee, California, or Sydney Au. 

[longtom]

Yeah O-P, you know I was thinking (always dangerous) along similar lines earlier.

Would that mean that in fstab I would have to mount all shares permanently which I would like to backup?  That would be quite a couple ... 

[djohnston]

Would that mean that in fstab I would have to mount all shares permanently which I would like to backup?  That would be quite a couple ... 

Use the noauto option so that you can mount/unmount when you want to.

auto and noauto With the auto option, the device will be mounted automatically (at bootup, or when you issue the mount -a command). auto is the default option. If you don't want the device to be mounted automatically, use the noauto option in /etc/fstab.

[longtom]

Would that mean that in fstab I would have to mount all shares permanently which I would like to backup?  That would be quite a couple ...  

Use the noauto option so that you can mount/unmount when you want to.

auto and noauto With the auto option, the device will be mounted automatically (at bootup, or when you issue the mount -a command). auto is the default option. If you don't want the device to be mounted automatically, use the noauto option in /etc/fstab.

Thank you.  In my case I would like to mount automatically.  However, the fstab file will be quite a big one, that was actually my point. 3 folders per station with 20 stations means 60 fstab entries.  But that would be fine if it has to be - but only then.

The other concern.  What will happen if the pc(s) get switched of in the evening and switched on in the morning?  Some don't run on the weekend?  Would I need to "mount -a" every morning to make sure all permanent shares are seen?

[Old-Polack]

Would that mean that in fstab I would have to mount all shares permanently which I would like to backup?  That would be quite a couple ...  

Use the noauto option so that you can mount/unmount when you want to.

auto and noauto With the auto option, the device will be mounted automatically (at bootup, or when you issue the mount -a command). auto is the default option. If you don't want the device to be mounted automatically, use the noauto option in /etc/fstab.

Thank you.  In my case I would like to mount automatically.  However, the fstab file will be quite a big one, that was actually my point. 3 folders per station with 20 stations means 60 fstab entries.  But that would be fine if it has to be - but only then.

The other concern.  What will happen if the pc(s) get switched of in the evening and switched on in the morning?  Some don't run on the weekend?  Would I need to "mount -a" every morning to make sure all permanent shares are seen?

You are losing me with this last statement. Why would you need 60 permanent connections? What are these three directories per station?

[bobestes]

You state that rsync seems to synchronize files at different locations. That is the very definition of what a backup is. How can it not be what you are looking for?  

Agreed.  However, what does not seem to be possible is to backup anything from another pc on a lan network... which is what is needed for a simple file server - backup arrangement.

Have you read    man rsync   yet? Rsync is what is used to load the repository at ibiblio and sync all the mirrors to it. The rsync man page will make your head spin with all the possibilities presented, with examples.

I have looked at it.  The first sentence in the description is "Rsync is a fast and extraordinarily versatile file copying tool."  Copying files from one location to another might be considered a form of backup, but it doesn't fit the criteria I'm looking for.  My idea of a backup program for a stand-a-lone computer would allow me to easily select specific folders and files and insert them into a compressed file on removable media.  It would also allow me to easily restore those files and folders in the event of data loss.

Since my last post, I've found a program in the repository called Areca Backup.  I've gone through the tutorial, and while it may not be the ideal backup program, it does seem to fit my basic criteria.

I thank all of you for your responses and suggestions.

Bob

[longtom]

Would that mean that in fstab I would have to mount all shares permanently which I would like to backup?  That would be quite a couple ...  

Use the noauto option so that you can mount/unmount when you want to.

auto and noauto With the auto option, the device will be mounted automatically (at bootup, or when you issue the mount -a command). auto is the default option. If you don't want the device to be mounted automatically, use the noauto option in /etc/fstab.

Thank you.  In my case I would like to mount automatically.  However, the fstab file will be quite a big one, that was actually my point. 3 folders per station with 20 stations means 60 fstab entries.  But that would be fine if it has to be - but only then.

The other concern.  What will happen if the pc(s) get switched of in the evening and switched on in the morning?  Some don't run on the weekend?  Would I need to "mount -a" every morning to make sure all permanent shares are seen?

You are losing me with this last statement. Why would you need 60 permanent connections? What are these three directories per station?

That's ok, O-P.  Probably my poor English.  If I have a network with 20 PCs and I want to backup 3 directories/folders from every PC I will have to permanently share 60 directories/folders.  This is how I understand it.

The other issue is:

What will happen if the pc(s) get switched of in the evening and switched on in the morning?  Some don't run on the weekend?  Would I need to "mount -a" every morning to make sure all permanent shares are seen?

[Old-Polack]

You are losing me with this last statement. Why would you need 60 permanent connections? What are these three directories per station?

That's ok, O-P.  Probably my poor English.  If I have a network with 20 PCs and I want to backup 3 directories/folders from every PC I will have to permanently share 60 directories/folders.  This is how I understand it.

The other issue is:

What will happen if the pc(s) get switched of in the evening and switched on in the morning?  Some don't run on the weekend?  Would I need to "mount -a" every morning to make sure all permanent shares are seen?

I have two partitions for my backups. They are never mounted except when a backup is to be performed, or a recovery needed. procedure is;

1. mount a backup partition
2. run backup or recovery process
3. unmount partition

Whether the partition being mounted is on a server, or a local drive, doesn't change anything.

Even if you connect to each station continuously, I'm still seeing only 20 mounts. one per station. The three directories being backed up would only need to be backed up to a single directory per station on the backup partition, and would not require a separate mounting for each. They are directories, not partitions, and backups, not shares. Why would you want to share backups?

I can backup my entire system, thousands of directories and files, over a single, temporary, mount/connection. So again I say, your logic is eluding me when you mention 60 permanent connections in fstab.

[longtom]

I can backup my entire system, thousands of directories and files, over a single, temporary, mount/connection. So again I say, your logic is eluding me when you mention 60 permanent connections in fstab.

I am lost ...

I am talking about the directories to be backed up, which need a mention in the fstab file.  I had no plans to share the backup directory ...

There are 60 different directories which need to be backed up.  All of these directories are on PCs which are part of a lan network.

On the server (PC were the backup process takes place):

Lets say I want to backup directory1 on Petes PC (ip 192.168.1.122), I would write in fstab something like this:

Code: [Select]

//192.168.1.122/directory1 /media/Petedirectory1 cifs domain=workgroup,guest, etc ..
directory2 on Petes PC:

Code: [Select]

//192.168.1.122/directory2 /media/Petedirectory2 cifs domain=workgroup,guest, etc ...
directory3 on Petes PC

Code: [Select]

//192.168.1.122/directory3 /media/Petedirectory3 cifs domain=workgroup,guest, etc ...
Next PC: directory1 on Mikes PC (ip is 192.168.1.123)

Code: [Select]

//192.168.1.123/directory1 /media/Mikedirectory1 cifs domain=workgroup,guest, etc ...
and so on, until all directories I need to backup are mounted.  Only than can I start backing up those directories an automate the process.

Where is my thinking wrong.

If this is still to confusing, ignore me, O-P, and I write this one off...