Dear all,
since my previous thread:
http://forums.cpanel.net/f49/peformance-issue-gzipping-nfs-partition-351812.html#post1419391
The backup module has been improved: cPanel introduced the "another location" destination in backup.
This is fine because i can ask to cpanel to zip all the files localy and only, in a second moment transfer the tarbal on the NFS remote partition.
The system can also delete all backup file localy at the end of process.
Really Good, then I can finally said that my problem with the NFS call flood is finally over.
BUT...
The problem is that RESTORE FEATURE only works with the current backup location.
This means that i'm not able to:
- show backup to my customer in their cPanel Backup selection
- restore from the WHM without move the tarball back in the directory.
This is weird.
It's like I'm using the wrong directory for backup and restore.
I think that backup behaviour is still wrong and that should be possible to:
1) select a working directory to execute localy the backups [only local directory accepted]
2) select a directory to store the backups used also to restore (which can be mount from remote partition)
Which is different from the actual solution:
1) select a directory where execute, store and restore account (all!)
2) select many alternative location to store (but not to restore account)
Backup should be executed ONLY on local filesystem to preserve performance.
cPanel should consider to fix this.
since my previous thread:
http://forums.cpanel.net/f49/peformance-issue-gzipping-nfs-partition-351812.html#post1419391
The backup module has been improved: cPanel introduced the "another location" destination in backup.
This is fine because i can ask to cpanel to zip all the files localy and only, in a second moment transfer the tarbal on the NFS remote partition.
The system can also delete all backup file localy at the end of process.
Really Good, then I can finally said that my problem with the NFS call flood is finally over.
BUT...
The problem is that RESTORE FEATURE only works with the current backup location.
This means that i'm not able to:
- show backup to my customer in their cPanel Backup selection
- restore from the WHM without move the tarball back in the directory.
This is weird.
It's like I'm using the wrong directory for backup and restore.
I think that backup behaviour is still wrong and that should be possible to:
1) select a working directory to execute localy the backups [only local directory accepted]
2) select a directory to store the backups used also to restore (which can be mount from remote partition)
Which is different from the actual solution:
1) select a directory where execute, store and restore account (all!)
2) select many alternative location to store (but not to restore account)
Backup should be executed ONLY on local filesystem to preserve performance.
cPanel should consider to fix this.