Plesk 12.5 backup and outside webroot directory

[AmaZili Communication]

Hi,

We are using a new server with pesk 12.5 /centos 7.
We were used to the plesk 12 backup and restore that allowed us to restore complete accounts including outside webroot directories.

With our new server with Plesk 12.5, we could not get back the outside webroot directory : our-directory !

our directory structure is the following :
var
|
www
|
vhosts
|
ourdomain.tld
|
_anon_ftp
_conf
_error_docs
_logs
_statistics
_web_users
_cgi-bin
_httpdocs
_private
_subdomains
_our-directory

Is there something special to setup ?
Are we missiing something ?

Thanks for help.

Philippe

 

[abdi]

Hope this can help:
http://download1.parallels.com/Ples...inistrator-guide/index.htm?fileName=68695.htm

 

[AmaZili Communication]

Thanks Joseph for the reply,
I felt it was something like that.

Next problem is when I try to make a new vhost template and it does not work at all ....

my alternate template structure is the following :

alternate-template
_cgi-bin
_conf
_error_docs
_httpdocs
_webspace
_our-directory

All directories exept our one (our-directory) copied from the .skel/0 directory.

I tried to put the alternate-template directory and its subdirectories in a zip, as a result on importation I get nothing in the Gérer le template de l'hôte virtuel page (sorry, we are french )

French message :
Fichiers et répertoires
Aucun(e) éléments dans le répertoire Template de l'hôte virtuel

While when I put only the subdirectories in the zip, I get :

cgi-bin 4.00 Ko conf 4.00 Ko error_docs 4.00 Ko httpdocs 4.00 Ko webspace 4.00 Ko

Template de l'hôte virtuel : 5


No error message but no our-directory in there....

Any ideas ?

 

[AmaZili Communication]

After a chat on twitter with @pleskHelps, I have tried almost every archive format.
RAR and Zip from a windows pc,
Zip from a unix machine,
tar, tgz, tar.gz,
None of them works

tried linux commands :
tar -czvf alternate-template.tar.gz -C/path/to/alternate-domain-template .
cd /path/to/alternate-domain-template/ && tar -zcvf ../alternate-template.tar.gz * && cd ..
cd /path/to/alternate-domain-template/ && tar -cvf ../alternate-template.tar . && cd ..

with or without z to compress.

NO WAY !
No messages, nothing.

It just does not work.

Help please

 

[Sergey L]

I would recommend checking privileges which you set on "_our-directory"
If the backup tool cannot access it, it would be the likely reason for the directory to not get included into the backup
If a directory has been created via Plesk and thus has proper privileges configured, it will be backed up and restored without problems - just checked it personally. Just test it via Plesk File Manager

 

[IgorG]

Could you please clarify with more detail what exact problem do you have?
Sorry, but I know nothing about your twitter chat.
Please describe your problem in detail and step-by-step instruction for reproducing.
Thanks.

 

[Aleksey Filatev]

Hello!

You need to place custom directories and files inside of webspace directory. Content of webspace directory will be placed at the root of subscriptions, created according this template. So, structure of template in your case should be following:

cgi-bin
conf
error_docs
httpdocs
webspace
webspace\our-directory

Just pack it into zip and upload via Tools&Settings.

 

[AmaZili Communication]

Thanks for your responses.


Sergey, I don’t think it is a problem with access rights, I create the directory from the plesk file manager.

Igor, the conversation over twitter is summarized in my #4 message.
Hereunder instruction on how to reproduce....


Aleksey, you gave me the solution for the new template, it works and creates our our-directory outside webroot with a minor glitch, a cgi-bin is created inside the httpdocs in addition to our files (too bad.... ) (documentation should be modified to be more detailed and use your example)
Anyway after succeeding this step, I created a brand new domain with this template, saved the complete account and tried to restore the site part....
Restoration went fine with a success message BUT the content of our-directory was not restored.
There is something wrong in there...

Methodology to reproduce:

Centos 7 plesk 12.5 with all updates applied

Connect to plesk
Create a domain

With the plesk file manager create a directory outside httpdocs (under main directory, on the same level as httpdocs, error_docs, logs)
Always with the file manager go to the directory you created and create a file (say x.php)

Go back to the domain and create a backup with option complete and files and databases (and all the others) checked

When this is done go back to the file manager,
Go to your directory you created before
Suppress the x.php file

Restore the backup
Choose sites as the object to restore
Choose your sitename
Chose restore configuration and content
Get the message: restoration is finished in the green (success) bar

Go to file manager
Check the directory you created
File x.php is not there

You can alternately try with created the directory in a template (see Alksey technique that works fine), and do the same and get the same result :
Nothing restored neither …..

 

[AmaZili Communication]

Should I raise a ticket for the backup problem ?

It is certainly a problem for everyone with directories outside webroot.
If people imagine they have backups as in plesk 12, they will be in deep troubles

 

[Aleksey Filatev]

You have a few options to restore file content of your subscription:

• Restore only document roots of selected domains: What do you want to restore? is Selected objects, and Type of object to restore is Sites, by default
• Restore specific files or directories: What do you want to restore? is Selected objects, and Type of object to restore is Files of domains
• Restore all content: What do you want to restore? is All objects (entire system)

When you restoring sites, only content of Document root of selected domain will be restored. You need to perform restoration of all objects to restore content in the root of webspace, or explicitly specify files and directories to restore.

 

[AmaZili Communication]

I confirm it works just fine.
Thanks Aleksey.
May be the documentation could be made more explicit on both subjects.