=== DreamObjects Connection === Contributors: Ipstenu, DanCoulter Tags: cloud, dreamhost, dreamobjects, backup Requires at least: 3.4 Tested up to: 3.7 Stable tag: 3.3 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html Connect your WordPress site to DreamHost's DreamObjects. == Description == DreamHost has its own Cloud - DreamObjects™ - an inexpensive, scalable object storage service that was developed from the ground up to provide a reliable, flexible cloud storage solution for entrepreneurs and developers. It provides a perfect, scalable storage solution for your WordPress site. Well now that we've gotten the sales-pitch out of the way, DreamObjects Connections will plugin your WordPress site into DreamObjects, tapping into the amazing power of automated backups, fileuploaders, and more! Please do not open DreamHost Support Tickets for this plugin. Honestly, the support techs are fantastic, but they can't debug this yet, so they'll just send you here anyway. Post in the support forum here, and I'll get to you ASAP. = Backup Features = * Automatically backs up your site (DB and files) to your DreamObjects cloud on a daily, weekly, or monthly schedule. * Retains 15, 30, 60, or 90 backups at any given time (so as not to charge you the moon when you have a large site). * Provides wp-cli hooks to do the same = Uploader = * Allows you to upload files to any bucket * Determine if files are public (default) or private * If configured, the shortcode [dreamobjects] will display a list of all your upload files = To Do = * CDN (when available) * Better [dreamobjects] support for folders * Option to email results (if logging, email log? Have to split up by attempt for that) * Better advanced logging via s3's debug. == Installation == 1. Sign up for DreamObjects 1. Install and Activate the plugin 1. Fill in your Key and Secret Key = Backups = 1. Pick your backup Bucket 1. Select what you want to backup 1. Chose when you want to backup 1. Relax and let DreamHost do the work = Uploader = 1. Pick your bucket 1. Upload a file to the bucket == Frequently asked questions == = General Questions = What does it do? DreamObjects Connection connects your WordPress site to your DreamObjects cloud storage, allowing you to upload files directly to your cloud, or automatically store backups. What does it backup? Your database and your wp-content folder. In a perfect world it would also backup your wp-config.php and .htaccess, but those are harder to grab since there aren't constant locations. Do you work for DreamHost? Yes, but this isn't an official DreamHost plugin at this time. It just works. Do I have to host my website on DreamHost? No, but using it anywhere else is unsupported. You have to use DreamObjects, which belongs to DreamHost. This plugin was built on and specifically for DreamHost servers, so I can give you no assurance it'll work on other hosts. Can I use this on a Windows Server? This is unsupported. You can try, and let me know how it goes. I built this for DreamHost, so it has only been tested on Linux boxes. Can I use this on Multisite? Not at this time. Backups for Multisite are a little messier, and I'm not sure how I want to handle that yet. How big a site can this back up? The hard limit is 2G. I've personally tested up to 250MB without any issues. Why does my backup run but not back anything up? In pre 3.1 versions, that happened because of size. A quick way to test if this is happeneing still is by trying to only backup the SQL. If that works, then it's the size of your total backup. Wait, you said it could back up 2G! What gives? There are a few things at play here: 1. The size of your backup 2. The file upload limit size in your PHP 3. The amount of server memory 4. The amount of available CPU In a perfect world, you have enough to cope with all that. When you have a very large site, however, not so much. You can try increasing your PHP filesize upload limit, or if your site really is that big, consider a VPS. Remember you're using WordPress to run backups here, so you're at the mercy of a middle-man. The DreamObjects itself can handle 2G, PHP may not make it. I have, personally, verified a 250MB zip file, with no timeouts, no server thrashing, and no PHP errors, so if this is still happening, turn on debugging and check the log. If the log stalls on creating the zip, then you've hit the memory wall. It's possible to increase your memory limit via PHP, however doing this on a shared server means you're probably getting too big for this sort of backup solution in the first place. If your site is over 500megs and you're still on shared, you need to seriously think about your future. This will be much less of an issue on VPS and dedi boxes, where you don't have the same limits. Where's the Database in the zip? I admit, it's in a weird spot: /wp-content/upgrade/dreamobject-db-backup.sql Why there? Security. It's a safer spot, though safest would be a non-web-accessible folder. Maybe in the future. My backup is small, but it won't back up! Did you use defines for your HOME_URL and/or SITE_URL? For some reason, PHP gets bibbeldy about that. I'm working on a solution! = Using the Plugin = How often can I schedule backups? You can schedule them daily, weekly, or monthly. Can I force a backup to run now? Yep! It actually sets it to run in 60 seconds, but works out the same. I disabled wp-cron. Will this work? Yes, provided you still call cron via a grownup cron job (i.e. 'curl http://domain.com/wp-cron.php'). That will call your regular backups. ASAP backup, however, will need you to manually visit the cron page. I kicked off an ASAP backup, but it says don't refresh the page. How do I know it's done? By revisiting the page, but not pressing refresh. Refresh is a funny thing. It re-runs what you last did, so you might accidently kick off another backup. You probably don't want that. The list isn't dynamically generated either, so just sitting on the page waiting won't do anything except entertain you as much as watching paint dry. My suggestions: Visit another part of your site and go get a cup of coffee, or something else that will kill time for about two minutes. Then come back to the backups page. Just click on it from the admin sidebar. You'll see your backup is done. (Yes, I want to make a better notification about that, I have to master AJAX.) How long does it keep backups? Since you get charged on space used for DreamObjects, the default is to retain the last 15 backups. If you need more, you can save up to 90 backups, however that's rarely needed. Can I keep them forever? If you chose 'all' then yes, however this is not recommended. DreamObjects (like most S3/cloud platforms) charges you based on space and bandwidth, so if you have a large amount of files stored, you will be charged more money. Who can upload files? Anyone who can upload media can upload files, so this generally covers Authors and up. Only the Administrators can set the upload bucket, however. How do I use the CLI? If you have wp-cli installed on your server (which DreamHost servers do), you can use the following commands: 
wp dreamobjects backup
That runs an immediate backup and is great if you're going to, say, upgrade WP. Then you backup, upgrade your site, and everything is happy! = Errors = It's reporting page not found when I access the pages Upgrade to version 3.2 and tell PHP it's drunk. Can I see a log of what happens? You can enable logging on the main DreamObjects screen. This is intended to be temporary (i.e. for debugging weird issues) rather than something you leave on forever. If you turn off logging, the log wipes itself for your protection. Why don't my buckets list? Do you see an error like this? Fatal error: Call to undefined method SimpleXMLIterator::__toString() in /wp-content/plugins/dreamobjects/AWSSDKforPHP/utilities/simplexml.class.php on line 164 If so, you're on PHP 5.2 and you need to upgrade to 5.3 or higher. AWSSDK dropped support for 5.2 when it added 5.4, so it was either support 5.2 and 5.3 OR 5.3 and 5.4. I went with the future. What's this S3::listBuckets() error? Any time you see an error like this, it means the plugin can't talk to your DreamObjects buckets: "warning: S3::listBuckets(): [403] Unexpected HTTP status in /wp-content/plugins/dreamobjects/lib/S3.php on line 249" Reasons why include the key/secretkey pair aren't actually setup correctly, the bucket was deleted after adding it to the plugin, or your DreamObjects account is disabled. Double check that your keys are correct and the bucket exists. My backups don't work, and when I turned on debugging, I see a 'failed' message Example error: [2013/01/22 08:58:17] File failed to create /home/name/domain.com/wp-content/upgrade/dreamobject-backups.zip in DreamObjects as domain.com/2013-01-22-085817.zip. Status: . This means the file was zipped up, but could not copy up to the server. Turn on debug mode, and then turn on verbose debugging. Then, via command line, run the backup wp dreamobjects backup That will output a whole mess of code. Save that output and post in the forums that this is happening. I'll get in touch with you so you can email me the output privately. The automated backup is set to run at 3am but it didn't run till 8am! That's actually not an error. WordPress kicks off cron jobs when someone visits your site, so if no one visted the site from 3am to 8am, then the job to backup wouldn't run until then. Nothings happening when I press the backup ASAP button. First turn on logging, then run it again. If it gives output, then it's running, so read the log to see what the error is. If it just 'stops', then it's a bug. If it says it can't upload the file to DreamObjects, it's probably size. Then log in via SSH and run 'wp dreamobjects backup' to see if that works. == Screenshots == 1. DreamObjects Private Key 1. Your DreamObjects Public Key 1. The Settings Page 1. The backup page 1. The uploader page, as seen by Admins 1. The uploader page, as seen by Authors == Changelog == = 3.4 = XXX, 2013 by Ipstenu * Typo in echo -- _e() should be __() (props Marko and Shredder) = 3.3 = June 24, 2013 by Ipstenu * Changing how the backup is done to make it smaller but also to support more configurations. Now it only backs up wp-content. * Increased timeouts for SQL = 3.2.1 = Mar 28, 2013 by Ipstenu * Dropping support for PHP 5.2, since AWSSDK did it first. It's not me, Mom! = Version 3.2 = Mar 19, 2013 by Ipstenu * PHP 5.4 support required updating the AWSSDK (props Shredder) * Added in an actual checkbox for super debug mode * Edited AWSSDKforPHP/services/s3.class.php to work with CEPH = Version 3.1.1 = Feb 11, 2013 by Ipstenu * The shortcode was broken. No one noticed. Not sure what that means ;) = Version 3.1 = Jan 23, 2013 by Ipstenu * Fixing timeout with large zips * Fixed Multipart for files over 100megs (props Stephon) = Version 3.0 = Jan 16, 2013 by Ipstenu * Massive re-write. Now using The full SDK instead of Amazon S3 PHP Class (Thank you Stephon, Shredder/@GetSource, and Justin at DreamHost) * Security level up: Using register settings and the nonces the way WP intended (thank you @no_fear_inc, @rarst, @trepmal) * Logging now covers uploads, plus has more information for debugging. * Moving DHDO::, messages, registering settings, and many other things to their own files. * Fixed lingering debug warning with translations. * Using the MultiPart uploader, which should handle larger files. = Version 2.3 = Jan 3, 2013 by Ipstenu * Optional logging (good for debugging) * No longer takes a backup right away when saving settings (good for testing lots of stuff) * Hiding keys if set for security * Reset option (wipes all settings) = Version 2.2 = Dec 30, 2012 by Ipstenu * Fixed date/time issue with backups displaying wrong (did not impact functionality, just bad date conversion) * Changed refs of siteurl to home_url, in order to fix wp-cli backups going astray under certain conditions * Security fixes (from duck_ aka Jon Cave) = Version 2.1 = Dec 21, 2012 by Ipstenu * Made a change to how times are generated using current_time correctly, vs time (props Regan, a DreamHost customer, for letting me log into your site!) * Changed date() to date_i18n() (thank you @Rarst for your 'tsk' - it lights a fire) * Cleaning up debug errors * Fixed uninstall = Version 2.0 = Nov 1, 2012 by Ipstenu * Backup retention - chose your own adventure. = Version 1.2 = Oct 11, 2012 by Ipstenu * Uploader added * Shortcode to list uploaded files added * Moved New Bucket code to the main settings page, where you can see your buckets now = Version 1.1 = Sept 27, 2012 by Ipstenu * All minor changes, but since people had been using 1.0, I thought a kick was in order. * Security (nonce, abspath, etc) * Better defines * wp-cli (still not 100%) = Version 1 = Sept 2012, by Ipstenu * Forked WP S3 Backups to work with DreamObjects. * Upgraded Amazon S3 PHP Class to latest version * Pretified, consolidated, organized, and formatted. * Saving temp files to upgrade (vs it's own folder) == Upgrade notice == PHP 5.2 is no longer supported. Also now only wp-content/uploads is backed up (in the effort of making this smaller)