Even if cPremote was secure it isn't good practice to push backups anyway.I'll never use for my customers cPremote, it is full of exploits, and the developers if hiding some really bad security problems.
Even if cPremote was secure it isn't good practice to push backups anyway.
It is better to have remote server 'pull' backups from web server. If you 'push' to remote server and your web server is compromised then your remote server is also vulnerable.who says. I would say its the best practice to push backups to a remote server.
It is better to have remote server 'pull' backups from web server. If you 'push' to remote server and your web server is compromised then your remote server is also vulnerable.
who says. I would say its the best practice to push backups to a remote server.
Its no good keeping backups on the same server as the sites as if the server goes down so does all the backups.
we use cpremote and push the backups to a remote server and then even have the remote/backup server mirrored to a second server, so we have the backups on at least 2 other servers in different Datacenters
@nodepacket usually a good host will have gigabit connectivity to the Internet....We use an offsite vault and the speed between them and using a more local different server is minimal.
We don't pay for incoming transit either so that's a bonus!
Why don't any Web hosts run offsite backups?
We offer free basic off-server FTP backups for those that want it. Surprised at how many don't bother though(!)
It's often neglected due to the expense. The reality is that hosting businesses need to factor off-site data backup costs into their business models, because it's an absolute necessity.
I think that when it's neglected due to expense, the true 'expense' hasn't really been calculated by the company; the cost of NOT having backups is infinitely larger than the few dollars a start-up hosting company will pay for a small bit of off-site storage.
The safest way to secure cPremote backups would be to pull the backups (from backup server) to another server rather than push again.