Plesk Backup Manager Not Working – Missing Tables BackupsSettings, BackupsScheduled, BackupsRunning

Re: Backup Manager Not Working in Plesk

If you get the following message when trying to run a backup in Plesk using the Backup Manager then it is likely that a previous upgrade or installation of the Backup Manager did not complete and so there will be some missing tables.

0: common_func.php3:206
db_query(string 'select `value` from `BackupsSettings` WHERE `param` = 'backup_ftp_settinghost' AND `id` = 6 AND `type` = 'domain'')
1: common_func.php3:253
db_query_ex(string 'select `value` from `BackupsSettings` WHERE `param` = '?(paramName)' AND `id` = ?(objectId) AND `type` = '?(objectType)'', array)
2: BackupFTPRepositorySettings.php:205
BackupFTPRepositorySettings->getRepositorySettingsValue(string 'backup_ftp_settinghost')
3: BackupFTPRepositorySettings.php:43
BackupFTPRepositorySettings->init()
4: BackupFTPRepositorySettings.php:25
BackupFTPRepositorySettings->__construct()
5: BackupFTPRepositorySettings.php:283
BackupFTPRepositorySettingsDomain->__construct(integer '6')
6: client.domain.backup.php:8
plesk__client__domain__backup->getBackupFTPRepositorySettings()
7: backup.ftp-repository.php:35
__backup__ftp_repository->getDumpsStorageCredentials()
8: backup.ftp-repository.php:29
__backup__ftp_repository->getRepositoryList()
9: backup.abstract-repository.php:44
__backup__abstract_repository->accessItemsList(string 'GET', NULL null)
10: backup.abstract-repository.php:26
__backup__abstract_repository->accessItem(string 'GET', NULL null)
11: UIPointer.php:596
UIPointer->access(string 'GET')
12: plesk.php:38

The Plesk Backup Manager needs the following tables in the PSA database:

  • BackupsSettings
  • BackupsScheduled
  • BackupsRunning

Execute the following SQL in phpMyAdmin to create the missing tables:

CREATE TABLE IF NOT EXISTS `BackupsSettings` (
`id` int(10) unsigned default NULL,
`type` enum('domain','client','server') NOT NULL default 'domain',
`param` varchar(255) NOT NULL default '',
`value` varchar(255) character set utf8 default NULL,
UNIQUE KEY `index1` (`id`,`type`,`param`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE IF NOT EXISTS `BackupsScheduled` (
`id` int(10) unsigned NOT NULL auto_increment,
`obj_id` int(10) unsigned NOT NULL,
`obj_type` enum('server','reseller','client','domain') NOT NULL,
`repository` enum('local','ftp') NOT NULL default 'local',
`last` datetime default NULL,
`period` int(10) unsigned NOT NULL,
`active` enum('true','false') NOT NULL,
`processed` enum('true','false') NOT NULL,
`rotation` int(11) NOT NULL default '0',
`prefix` varchar(255) character set utf8 default NULL,
`email` varchar(255) character set utf8 default NULL,
`split_size` int(10) unsigned NOT NULL default '0',
`suspend` enum('true','false') NOT NULL default 'false',
`with_content` enum('true','false') NOT NULL default 'true',
`backup_day` int(10) unsigned NOT NULL default '0',
`backup_time` time NOT NULL default '00:00:00',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=17 ;

CREATE TABLE IF NOT EXISTS `BackupsRunning` (
`sessionId` varbinary(250) NOT NULL,
`param` varchar(250) character set ascii NOT NULL,
`val` varbinary(255) default NULL,
PRIMARY KEY (`sessionId`,`param`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

This will resolve the problem, the Backup Manager will now work correctly!

How to parse PHP in HTML

To parse PHP code inside a .html file you will need to a create a .htaccess file in your document root directory /httpdocs and insert the following code:

AddHandler php-script .html .htm

How do I extend the ‘validity period of domain’ in Plesk?

Re: validity period of domain, validity period is prolonged, extend the validity period

If you get this message then do not worry about the expiry of your domain name or hosting account. This message relates to the period you applied when you added the domain name to your Plesk panel.

The messages usually contain:

  • validity period of domain
  • validity period is prolonged
  • extend the validity period

This problem occurs if you missed out Step 12 in “How to add a domain to multi-domain hosting“.

To resolve, simply log in to your Plesk control panel, select the appropriate domain name, go to Resource Usage and ensure that the “Expiration date” is set to “Never Expires“.

Plesk Migration Manager (PMM) Stalls at 50% Completion

Plesk Migration ManagerRe: Insufficient storage for Plesk  9.5.4 Migration Manager (even though there is)

If you are having problems using the Plesk Migration Manager, one of the first problems you need to solve is the insufficient space problem. There are many problems with the PMM but that’s another story, you’re probably here because you really need to get it working.

You may get a failed migration due to this issue, or a constant hang at 50% completion without any error.

Even though you get the opportunity to set a data dump location (default within /var) and you have likely carefully ensured that there is another psace storage on that device, what you don’t know is an intermediate storage space is also required in /usr/local/psa/PMM.

Luckily this problem is easily dealt with by creating a symbolic link for the PMM directory.

The examples below move the PMM directory to a secondary drive namely /backup.

1. Let’s create the new PMM directory on a drive with plenty of free space.

# mkdir /backup/PMM

2. Now we will copy the PMM directory and its contents to the new PMM directory whilst preserving the ownership and permissions.

# cp -Rp /usr/local/psa/PMM/* .

3. Set the current PMM directory aside

# mv /usr/local/psa/PMM /usr/local/psa/PMM.old

4. Now we create the symbolic link

# ln -s /backup/PMM /usr/local/psa/PMM

The PMM directory is now symbolically mapped to a drive with suffienct space for your migration to complete. You may need to abort any previous migrations and restart as often they do not restart once stopped due to an insufficient storage space problem.

See this entry on Parallels KB: http://forum.parallels.com/showthread.php?t=100327

Upgrade and Fix vulnerabilities in Plesk 9.5.4 for Linux

Re: Upgrade Plesk 9.5.4, Install micro-updates Plesk 9.5.x

If you are still running Linux Plesk 9.5.4 you may think that because 9.5.4 is the latest (and last) 9.5.x version that there are no new patches or upgrades available. If so, you are dangerously wrong.

Parallels regularly release “Micro Updates” which resolve recently discovered vulnerabilities, and there are plenty of them. The latest update is 9.5.4 MU 18.

You can find which version you are running like this:

# cat /root/.autoinstaller/microupdates.xml

You can see here that “patch version=18” which means micro updates up to  (MU) 18 are installed.

Upgrading to Plesk 9.5.4 and installing the Micro Updates

We recommend that you install any new micro updates as soon as possible, it takes only a few minutes and can be run from the command line:

/usr/local/psa/admin/sbin/autoinstaller –select-product-id plesk –select-release-current –reinstall-patch –install-component base

If you are not running Plesk 9.5.4, use the following command to upgrade to latest 9.5.4:

/usr/local/psa/admin/bin/autoinstaller –select-release-id=PLESK_9_5_4 –upgrade-installed-components –ignore-key-errors –notify-email=your@emailaddress.com

If you haven’t already, go to Parallels and subscribe for the panel update notifications:

http://kb.parallels.com/

For further information see Parallels KB Article http://kb.parallels.com/en/9294