D
dotCOM_host
Guest
Re: Re: Re: Re: Re: Backup problems
Anyway, you seem to like the way backups are done in Plesk. I tend to disagree. After being in the hosting business for many years and having experience with several other popular web control panels out there, I find Plesk backups severly lacking in usability and flexibility. Heck - in v8.0 they even removed the option to store backups on remote servers using FTP - a feature which was there before. Why?? What good are local backups if the server crashes and you can't get to the data in the first place? Backups should NEVER be stored on the same physical server as the web sites themselves. Sure, you can add yet another script to the server to copy all local backups to a remote server every night, but why? This feature not only should be there "out of the box", but in fact it was there, and it was removed in the 8.0 release. Again - why?? One stop forward (gzip backup files), two steps back (remove remote storage of backup files). <sigh>
Oh, I don't have a problem converting MIME or UUENCODEd content back into proper binary format. I just find it extremely archaic to go in that direction in the first place. Why even encode all files in MIME format when you can archive all files so you can get direct access to them in one step? MIME/UUENCODE were invented way back when for transmitting binary files via email - which to this day relays on plain text as the transfer medium between servers. Plesk surely doesn't email backup files to anyone, so why use MIME? Why not use tar or similar tools to create binary copies of web sites?About useless formats: since 8.0 things changed. It's still MIME-based, but now MIME-parts are just tar archives. And I sure such an experienced Unix admin have a couple of tools in toolbox which may unpack MIME message.
Anyway, you seem to like the way backups are done in Plesk. I tend to disagree. After being in the hosting business for many years and having experience with several other popular web control panels out there, I find Plesk backups severly lacking in usability and flexibility. Heck - in v8.0 they even removed the option to store backups on remote servers using FTP - a feature which was there before. Why?? What good are local backups if the server crashes and you can't get to the data in the first place? Backups should NEVER be stored on the same physical server as the web sites themselves. Sure, you can add yet another script to the server to copy all local backups to a remote server every night, but why? This feature not only should be there "out of the box", but in fact it was there, and it was removed in the 8.0 release. Again - why?? One stop forward (gzip backup files), two steps back (remove remote storage of backup files). <sigh>