• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Infinite backup

A

andreyb

Guest
When I switch on the backupmng at crontab then the backup is made cyclically without halt.
If I shall switch off backupmng at crontab and I shall wait the finish of all processes of backup then all created temporary files will be deleted:

#
#ls -l /var/lib/psa/dumps/tmp
total 0
# ls -l /usr/local/psa/tmp
total 252
-rwxrwxrwx 1 root root 126857 Sep 18 07:40 default_skeleton.tgz
-rwxrwxrwx 1 root root 479 Sep 18 07:14 ftp.pamd
-rwxrwxrwx 1 root root 34001 Sep 18 07:14 psa.key
-rwxrwxrwx 1 root root 20480 Sep 18 07:14 run-root.tar
-rwxrwxrwx 1 root root 59487 Sep 18 07:41 vhosts.tar.gz
#

But value of column "last" don't change:

mysql> select id, obj_type, repository, last, period, active, processed, files, prefix, objects, split_size from BackupsScheduled where active=true;
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+------------+
| id | obj_type | repository | last | period | active | processed | files | prefix | objects | split_size |
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+------------+
| 1 | domain | ftp | 2007-11-06 06:45:00 | 86400 | true | true | 7 | | 1 | 0 |
| 2 | domain | ftp | 2007-11-06 05:30:00 | 86400 | true | true | 7 | | 2 | 0 |
| 4 | domain | ftp | 2007-11-06 06:15:00 | 86400 | true | true | 7 | | 4 | 0 |
| 5 | domain | ftp | 2007-11-06 06:30:00 | 86400 | true | true | 3 | | 5 | 0 |
| 6 | domain | ftp | 2007-11-06 06:00:00 | 86400 | true | true | 7 | | 6 | 0 |
| 8 | domain | ftp | 2007-11-06 08:15:00 | 86400 | true | true | 7 | | 8 | 0 |
| 11 | domain | ftp | 2007-11-06 07:00:00 | 86400 | true | true | 7 | | 11 | 0 |
| 12 | domain | ftp | 2007-11-06 07:15:00 | 86400 | true | true | 7 | | 12 | 0 |
| 13 | domain | ftp | 2007-11-06 07:30:00 | 86400 | true | true | 7 | | 13 | 0 |
| 15 | domain | ftp | 2007-11-06 08:30:00 | 86400 | true | true | 7 | | 15 | 0 |
| 16 | domain | ftp | 2007-11-06 07:45:00 | 86400 | true | true | 7 | | 16 | 0 |
| 17 | domain | ftp | 2007-11-06 08:00:00 | 86400 | true | true | 7 | | 17 | 0 |
| 18 | domain | ftp | 2007-11-06 08:45:00 | 86400 | true | true | 7 | | 18 | 0 |
| 19 | domain | ftp | 2007-11-06 09:00:00 | 86400 | true | true | 7 | | 19 | 0 |
| 20 | domain | ftp | 2007-11-06 09:15:00 | 86400 | true | true | 7 | | 20 | 0 |
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+------------+

What is reason of cyclically backup.
 
hi there:

it wouldn't change until the backup is done. you see, perhaps it is not cycling, but rather is slow...

have you tried doing a 'normal' backup? like this:
ftp://download1.swsoft.com/Plesk/Plesk8.2/Doc/plesk-8.2-unix-backup-restore-guide/index.htm

See if it works. Then you can schedule backup of the server configuration and all user data from control panel:

Server > Scheduled Tasks > Add New Task > specify when backup.

Here is a how-to from Plesk Help:

"...To schedule the time using the crontab format: enter several values separated by commas, e.g.: to run a task on the 4th, 5th, 6th, and 20th of a month, type 4-6,20.

Then pecify the command in the Command input box:
usr/local/psa/bin/pleskbackup all <filename> , where the <filename> is a target backup file name with absolute or relative path to its location.
[Click OK]

The data will be backed up without disruption of hosting services and downtime. The resulting backup archive will be placed in the directory you specified."

Hope this helps a bit.
 
These problems are concerned with each other. backupmng is launched from root crontab every 15 minutes, it examines records 'period' and 'last' in table psa.BackupsScheduled and starts scheduled backup task /usr/local/psa/admin/plib/backup/scheduled_backup.php --dump <psa.BackupsScheduled.id> if it is time.

For an unknown reason backupmng does not update psa.BackupsScheduled.last after it has "finished" and starts the task next time. Another guess-work is that backupmng could not finish successfully and does not update the table therefore.

What I offer to do for the problem investigation, is disabling all scheduled backup tasks except of one of them and run backupmng, check either the utility updates the table.

Using the mysql command below you may find all domains and clients names where active scheduled backup tasks are set.

Clients:

mysql> select clients.pname from clients, BackupsScheduled where BackupsScheduled.obj_id=clients.id and BackupsScheduled.active='true' and BackupsScheduled.obj_type='client';

Domains:

mysql> select domains.name from domains, BackupsScheduled where BackupsScheduled.obj_id=domains.id and BackupsScheduled.active='true' and BackupsScheduled.obj_type='domain';

To disable scheduled backup tasks

for client: Clients -> CLIENT_NAME -> Back up -> Schedule Backup -> Switch Off

for domain: Domains -> DOMAIN_NAME -> Back up -> Schedule Backup -> Switch Off

You may may examine either backupmng and scheduled_backup.php are still running with 'ps -ax'.

I hope this helps.

./anb
 
I left one domain. The situation is same. Every 15 minutes I have new backup.

mysql> select id, obj_type, repository, last, period, active, processed, files, prefix, objects, split_size from BackupsScheduled where active=true;
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+------------+
| id | obj_type | repository | last | period | active | processed | files | prefix | objects | split_size |
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+------------+
| 1 | domain | ftp | 2007-11-11 06:45:00 | 86400 | true | true | 7 | | 1 | 0 |
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+---------
 
In admin panel:

domain.tld_2007.11.12_15-00-02 Nov 12, 2007 01:05 PM Scheduled backup of the domain ... 617 MB
domain.tld_2007.11.12_14-45-02 Nov 12, 2007 12:50 PM Scheduled backup of the domain ... 617 MB
domain.tld_2007.11.12_14-30-02 Nov 12, 2007 12:35 PM Scheduled backup of the domain ... 617 MB
 
Originally posted by andreyb
I left one domain. The situation is same. Every 15 minutes I have new backup.

mysql> select id, obj_type, repository, last, period, active, processed, files, prefix, objects, split_size from BackupsScheduled where active=true;
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+------------+
| id | obj_type | repository | last | period | active | processed | files | prefix | objects | split_size |
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+------------+
| 1 | domain | ftp | 2007-11-11 06:45:00 | 86400 | true | true | 7 | | 1 | 0 |
+----+----------+------------+---------------------+--------+--------+-----------+-------+--------+---------+---------

It looks like the backupmng does not finish its work successfully, it does not update the when backup has been created, otherwise BackupsScheduled.last gets creation date of the latest backup.

If BackupsScheduled.last has value '2007-11-11 06:45:00', next scheduled backup will be launched not earlier then in 86400 seconds, on 2007-11-12 06:45:00.

Check the destination FTP repository and try reconfiguring scheduled backup to local repository, instead of FTP.
If the problem was caused by destination FTP server that did not allow backupmng to complete its work, backup cycling stops.

./anb
 
Back
Top