I know of many companies who has a "back up" server where they back up all there files on their main server. So now my question is does it really matter what type of server it is since it is just for backups? Or should it be a certain type of server (better for backups)?
Yes it can use alot of bw but it depends on how much you are backing up. I use cpanel and have it set to do a full server backup daily and it auto ftp's it over to my backup server. A shared server with alot of HD space.
The type of server really isn't that big of a deal. Just make sure it is kinda fast and reliable. HD capacity is the key.
Another method that you might look into is a type of balance backing up. This is where one server backs up another 2 servers and another server backs up another 2 servers and so on and so forth. Basically all servers will be backed up on two different boxes and the bandwidth gets shared around. Now this might not be popular in all situations, especially if you are using expensive boxes, but it will def work for some. The only problem is keeping things organized.
Originally posted by Torith I know of many companies who has a "back up" server where they back up all there files on their main server. So now my question is does it really matter what type of server it is since it is just for backups? Or should it be a certain type of server (better for backups)?
The type of server doesn't matter all that much, as long as you have enough capacity for your needs. Even if you're using real-time compression and encryption via SSH, your CPU usage is going to be modest.
Any computer that was made in the last 4 years or so should do well. As for a new computer, the lowest end available will do.
Originally posted by QBert Dosent it rape your bandwith when you backup? and server resorces whyle its happening? also if youve got a server that has lots of forums and allwase being updated what happens when you backup?
If you're using Rsync, your bandwidth usage should be minimal. Unlike a standard compressed TAR backup, Rsync compares the files on both ends individually, and only transfers files that have changed. It can also do real-time compression.
As far as server resources, it also uses significantly less CPU time than a standard .tar backup.