simple backup process using server/client technology
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
RSYNC is the best for that.
It is very basic & simple to implement.
It is cutomisable to a pin point to fit your needs, It is the true power of CLI on linux.
Last year, I searched a lot for a good backup system with a client/server base and I finally turned to rsync. If you already know Samba, you will find the server configuration really easy since it is based on the Samba conf file....
On the client side, use -avz options if you want to keep everything as is (date, time, permissions, etc.).
Last year, I searched a lot for a good backup system with a client/server base and I finally turned to rsync. If you already know Samba, you will find the server configuration really easy since it is based on the Samba conf file....
On the client side, use -avz options if you want to keep everything as is (date, time, permissions, etc.).
But ZAK the link you have provided tells you how to set ssh public & private keys for RSYNC to work. It doesnt tell you how to set RSYNC server & its configuration & examples.
Thanks to everyone who replied this post, RSYNC is a very useful,compact and powerful tool. I respect that tool myself. I have used it specially incremental backups. It produces wonderful stress-loss for me.
But i feel its good for someone like me who is a versatile in linux but not too suitable as an implementation for office novice office people. I am ok setting up a backup server with CLI as long as i am going to be the one to use it and its a standalone system and it doesnt have any clients connecting to it. But i just want to implement a solution whereby i can configure it with CLI or /web interface/application or a combination of all and then leave the solution to the companies administrator (someone who is not well versed in linux) to manage and schedule backups or give policies to the various users of the backup system. Apart from this, the various users (workstation owners) can use a web interface/ or application or connect to the server application/web interface on the server to setup their backup schedules or retrieve their backed up files themselves as their access policies permit. of course the workstations mainly will running on MS W indows XP or similar and not likely linux. So there might be 2 ways of the users connecting to the server, either using the client app to connect and perform backup/retrieval/scheduling or they connect to the server thru their web interface or any network platform to perform their various tasks. I as the solution provider will just be responsible for maintaining the solution which will be invisible to their operations.
I never tried this backup solution, but it looks like a good one especially if you have Win box clients. However, you will need to install it on a Samba server (or at least you'll need a Samba network) since there is no real win client (win boxes connects via Samba network). You will also need an Apache server with CGI compiled which is sometimes a security issue on a file server to use the administrator web interface....
i hav started getting the hang of it already and it looks promising. iwell from what i gathered, it feels that the server's samba client (smbclient) will just scan the network for shares that needs to be backed up. u dont need any install of a samba server. U just need the smbclient. Well the CGI shudnt pose crious problems although i am trying to make it work but eventually, it will work well in the hand. What do u feel?
You're right, PCBackup uses smbclient to retrieve shared folders over the network. So you will have to set shares on client pc. You can also use rsync for windows via cygwin (http://sourceforge.net/projects/backuppc/). However, I invite you to read the Security FAQs at http://backuppc.sourceforge.net/faq/security.html to be informed of security risks. Overall, I think you may give it a try! I'm interested in your experience if you decide to try it.
i hav installed it and it looks good. i am just about testing the access control levels for each user and the administrator. And also the trying to setup some clients for a backup scenario. Well i dont know if its customizable coz its looks mundane.
WEll i ll give u a feedback when i have reall treid it out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.