• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Standard layout backupsScheduled table

BezNu

New Pleskian
Hi all,

is this the standard layout for the Plesk 9.2.3 backupsScheduled table:

id int(10) Nee
obj_id int(10) Nee
obj_type enum('server', 'reseller', 'client', 'domain') Nee
repository enum('local', 'ftp') Nee local
last datetime Nee
period int(10) Nee
active enum('true', 'false') Nee
processed enum('true', 'false') Nee
rotation int(11) Nee 0
prefix varchar(255) Ja NULL
email varchar(255) Ja NULL
split_size int(10) Nee 0
suspend enum('true', 'false') Nee false
with_content enum('true', 'false') Nee true

Or are there any fields missing in this layout?

My hosting co says that this is the standard layout, but since I somehow can't operate scheduled backups and have been reading something about the fields backup_day and backup_time that should part of this table, I doubt that his remark is correct.

So, is this the table that's being shipped with the standard setup, or not?
 
Here is default BackupsScheduled table desc for Plesk 9.2.3 version:

mysql> desc BackupsScheduled;
+--------------+---------------------------------------------+------+-----+----------+----------------+
| Field | Type | Null | Key | Default | Extra |
+--------------+---------------------------------------------+------+-----+----------+----------------+
| id | int(10) unsigned | NO | PRI | NULL | auto_increment |
| obj_id | int(10) unsigned | NO | | NULL | |
| obj_type | enum('server','reseller','client','domain') | NO | | NULL | |
| repository | enum('local','ftp') | NO | | local | |
| last | datetime | YES | | NULL | |
| period | int(10) unsigned | NO | | NULL | |
| active | enum('true','false') | NO | | NULL | |
| processed | enum('true','false') | NO | | NULL | |
| rotation | int(11) | NO | | 0 | |
| prefix | varchar(255) | YES | | NULL | |
| email | varchar(255) | YES | | NULL | |
| split_size | int(10) unsigned | NO | | 0 | |
| suspend | enum('true','false') | NO | | false | |
| with_content | enum('true','false') | NO | | true | |
| backup_day | int(10) unsigned | NO | | 0 | |
| backup_time | time | NO | | 00:00:00 | |
+--------------+---------------------------------------------+------+-----+----------+----------------+
16 rows in set (0.03 sec)
 
Back
Top