From the shell, you can trigger backups manually on demand and also have alternative backup methods available as well ....
However, from WHM backups run on a schedule .....
From Cpanel though, you can run a manual backup anytime on an account by account basis from within the account's Cpanel control panel .....
I personally like to build 'cpmove' archives with /scripts/pkgacct when I need to make a backup snapshot of an account.
From the shell, you can trigger backups manually
>> i want to to ran manually backup from the Shell, please give the command for that.
/scripts/cpbackup --force
At the shell command prompt:
will start a full cPanel backup at any time, using the settings in /etc/cpbackup.conf (which are set in the WebHost Manager at Main >> Backup >> Configure Backup).
There is no provision for doing this from the WebHost Manager. It must be done from the shell.
At the shell command prompt:
Code:
# /scripts/cpbackup --forceThere is no provision for doing this from the WebHost Manager. It must be done from the shell.
nice command
what i want to do is for our VPS server we are talking remotely backup & i have select daily/weekly backup option, the query is daily backup is done but not weekly
what i want to do is for our VPS server we are talking remotely backup & i have select daily/weekly backup option, the query is daily backup is done but not weekly
You just need to select daily backup, it will include weekly and monthly too. Just exclude monthly backup if you dont want it. If you have done exactly same way, there should be some problem with weekly backup, sometimes load on the server kills backup process, not usually though. You need to check your backup logs in order trace exact error...
Seems you are in a vps and usign ftp backup options. So it will tar the backup and upload to remote server. If you have really big accounts , there is a chance the gzip took a lot resources and your vps provider killed your backup process .
/usr/local/cpanel/logs/cpbackup
Each time cpbackup runs, it writes a new log file in /usr/local/cpanel/logs/cpbackup/. Check the timestamps of the files to find the newest one.
Each time cpbackup runs, it writes a new log file in /usr/local/cpanel/logs/cpbackup/. Check the timestamps of the files to find the newest one.
I ran this command
# /scripts/cpbackup --force
& got following output
[cpbackup] Process started in background.
[cpbackup] Log file: /usr/local/cpanel/logs/cpbackup/1281603263.log
How do i come to know that this task is finished ?
# /scripts/cpbackup --force
& got following output
[cpbackup] Process started in background.
[cpbackup] Log file: /usr/local/cpanel/logs/cpbackup/1281603263.log
How do i come to know that this task is finished ?
Watch the logs
Each backup run will have its own log file in /usr/local/cpanel/logs/cpbackup. The logs have numerical filenames; look for the most recent timestamp. You can use "tail -f" to watch the file while it is being written.
Each backup run will have its own log file in /usr/local/cpanel/logs/cpbackup. The logs have numerical filenames; look for the most recent timestamp. You can use "tail -f" to watch the file while it is being written.
@Nilesh : Use the command ps aux | grep cpback and you will be able to find the PID of the process along with some other informations.
@Rnjt : Did you check the logs. If the other accounts are not backed up there will be some errors and you will be able to find the errors in the logs. Please post your log details here.
@Rnjt : Did you check the logs. If the other accounts are not backed up there will be some errors and you will be able to find the errors in the logs. Please post your log details here.
It sounds like Rnjt may have selected only specific users to be backed up. In the WebHost Manager, click Main >> Backup >> Configure Backup, and at the very bottom of the page, next to Select Specific Users, click Select >>. A new window will open, showing which users are selected to have backups run.
Also, if the timestamp on an account's existing backup file is not old enough, the account will not be backed up. If daily backup is selected, and the timestamp on the backup file is not at least 24 hours old, the account will be skipped. If weekly backup is selected and the timestamp is not at least a week old, the backup will be skipped, and the same rule applies to monthly backups.
Also, if the timestamp on an account's existing backup file is not old enough, the account will not be backed up. If daily backup is selected, and the timestamp on the backup file is not at least 24 hours old, the account will be skipped. If weekly backup is selected and the timestamp is not at least a week old, the backup will be skipped, and the same rule applies to monthly backups.
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
| M | Manual backup command is not triggering addional local backups? | Backups | 8 | |
| S | Where are manual own backups in cpanel | Backups | 1 | |
|
Cron Backup (manual) cPanel script no longer works with Jupiter | Backups | 2 | |
| A | Ignore excluded extensions while manual backup | Backups | 1 | |
| T | Manually Pruning older Backups | Backups | 3 |