Hello.....
Currently using cPanel 11.24.4-R32603 - WHM 11.24.2 with incremental backups enabled.... few days ago, I restored my first account (previously deleted) from incremental backups.... then...
Can somebody confirm this???
- rsync, or cpanel incremental backup script, does not take care of permissions over files..... by example, if client did "chmod" to 777 a folder or file, but no file or data is added/removed/modified inside, the modified date is the same, so incremental backup does not stored this new information (permissións)........ sometimes you will have to fix manually permissións over files or folders for the websites to run...
- mysql.sql............... Wow!!!! the mysql.sql is not being updated!!!!!!!!!!!!! So new mysql-users are not being stored into package backup the incremental way!?!?!?!?! This king of incremental backup can hurt your head when restoring a user with 8-9-10 mysql-users......
- The mysql folder of an account will have always new databases stored as sql files, but old ones (also deleted ones) may be there forever...... it seems...... it is a bit sad, as they may be restored althought client remove them time ago...
Also for my restore of yesterday, a recent addon domain configured by my client was not "imported" when restoring...... had to do it manually.
It seems incremental backups is such a pain! It is a great sollution when you want to not overload your server when backing-up, as it is quick and not heavy, but cpanels scripts have too many "holes".
Anybody can confirm?
I think I am returning complete backups, but need to modify the cpbackup script to not gzipping the tars..........
Thanks.
Currently using cPanel 11.24.4-R32603 - WHM 11.24.2 with incremental backups enabled.... few days ago, I restored my first account (previously deleted) from incremental backups.... then...
Can somebody confirm this???
- rsync, or cpanel incremental backup script, does not take care of permissions over files..... by example, if client did "chmod" to 777 a folder or file, but no file or data is added/removed/modified inside, the modified date is the same, so incremental backup does not stored this new information (permissións)........ sometimes you will have to fix manually permissións over files or folders for the websites to run...
- mysql.sql............... Wow!!!! the mysql.sql is not being updated!!!!!!!!!!!!! So new mysql-users are not being stored into package backup the incremental way!?!?!?!?! This king of incremental backup can hurt your head when restoring a user with 8-9-10 mysql-users......
- The mysql folder of an account will have always new databases stored as sql files, but old ones (also deleted ones) may be there forever...... it seems...... it is a bit sad, as they may be restored althought client remove them time ago...
Also for my restore of yesterday, a recent addon domain configured by my client was not "imported" when restoring...... had to do it manually.
It seems incremental backups is such a pain! It is a great sollution when you want to not overload your server when backing-up, as it is quick and not heavy, but cpanels scripts have too many "holes".
Anybody can confirm?
I think I am returning complete backups, but need to modify the cpbackup script to not gzipping the tars..........
Thanks.