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?
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?