This is just a reminder that exporting is still important, especially for those using the default database method (Berkeley/DB_File.pm). Regular exporting of your entries can be a lifesaver if your database becomes corrupted.

Until MT provides a full export feature (configuration, templates, etc.) there are other ways to gather and preserve data aside from just the entries:

1) If you're using MySQL and have access to a tool like phpMyAdmin, you can use this to export your database. Choose "dump structure and data" and save as a text file.

2) If you're using Berkeley, download a copy of your db folder in BINARY mode (more useful if your database merely becomes corrupted; possibly less so if a change in Berkeley versions makes your data unreadable; but some of the db files can be opened in a text editor to recapture data.)

3) link your templates to files (can save you the trouble of copy-and-paste)

4) output templates with MySQL and PHP

5) MT-Medic provides lots of information on your installation. Using File > Save As, you can capture this information.

6) Multiple Blog Suite also provides configuration and template information all in one place.

These are just a few methods I've thought of offhand. If anyone has other suggestions, please add them here.

Don't be caught without backups.

Anyone remember where that posting is that listed the Import format with the MT tags inside it? That's another nice way to automatically backup your entries onto your server, every time you rebuild.

I think the first thread I linked to in my post is the thread you're thinking of - it has the export format in it, which Pat (The Booge) used to create an index template to export entries upon rebuild.

You can see the latest export format in lib/MT/App/CMS.pm - open it up in a text editor and search for export - the format starts in that subroutine with the lines

Amen girlie! I didn't even understand what the export feature was until it was too late

Now my blog is dead, and I'm waiting (impatiently) for Typepad to become available in some form so I can decide whether to pay for a re-install or move to Typepad.

Listen to the girl - back up early and often, else you'll end up like surfmonkey!

Can't you simply ftp your entire blog folder from the server to your PC? Would you do it binary? Then put it on a CDR?

Well, yes (you'd want to download your HTML files in ASCII mode though).

That would enable you to at least get the visible parts of your site back up for readers to see online.

But if you have to actually reinstall MT, you'd be reconfiguring all your blogs; copying and pasting all those entries back in; and recreating your templates by hand (and possibly memory) - because MT cannot recreate this information merely from the static HTML pages it has generated in the past.

The idea here is to create backups that will (hopefully) be the easiest to extract data from if you need to reinstall MT.

Just a question...

Why can't you guys at Movable Type create an easy to use Import/Export feature built into MT?

You can already Import and Export Entries, and Full DB Exports are on the Requested Features List.

But until it becomes a feature, the options in this thread serve the same purpose.

Girlie,

you're a doll--i really appreciate your post on this. i just logged in via phpMyAdmin and saved a backup of all my entries. if i hadn't read your post, i might not have ever thought of this. it was interesting to see my database from phpMyAdmin--kind of helps you visualize what's going on back there in the database.

you're a heroine!

pealeaf

Ok, it's late so bear with me, but I am having trouble following this.

I am actually in the situation where I am having to move domains/servers and had thought I would be ok just using ftp to get them back on my computer.

Am I not right about this? I wasn't the one who set up the original blog so I don't really know what I am doing with databases :-(

Anyone?

If you have shell access on your server, you can backup the entire mysql database using this:


A nightly cron job for backing up everything might be a good idea.

To put back the database:


You will be prompted for your mysql password for each of those two steps.

I also highly recommend Russcam's migrating your MT blog to a new webhost.

Donna

Okay, I have been running MT for about 6 months or so, and worked very hard to install it. I would like to back up my files, but as Im reading through this, Im totally lost by this lingo.

Could someone help me out please? I work on a Mac if that helps!

AAH!

What parts are you having trouble understanding?

The most important thing to backup is your entries. If you have them you can if necessary create a new blog with the default configuration and templates but you still have your content.

You can create a backup of your entries by "exporting" them. Subsequently, you can restore them if needed by "importing".

MT offers an import/export functionality. Go into your blog in MT and look along the lefthand side for a button labeled "import/export". Click on this to be taken to the import/export screen. If you scroll down you'll see the export section. Follow the instructions to create an export of your entries. Store this on your hard drive so you have it in case of need. Be sure to make new exports regularly so it contains your latest entries.

If you'd like to automate the process and especially if you have multiple blogs, you can follow the instructions in this tutorial about creating an export blog.

If you ever need to restore your entries from backup, use the import functionality on MT's import/export page.

If you've designed custom templates for your blog, you may wish to create backup copies of these as well. Girlie provided a link to a tutorial on how to do this.

You may also wish to backup your MT database. Girlie provides instructions for this as well. MT's default database is Berkeley DB and you can back this up by downloading the database files from your server.

If you set up MT to use MySQL then you can do an export from inside your database. Post back if you need help with that.

Hope this helps clarify things

OK, thanks for the reminder.

I notice that when I go into phpMyAdmin to export my database, there are many check boxes under the "Structure" and "Data" sections.

1) Do I select all the check boxes (i. e. drop table, inserts, etc.) in the "Structure" section?

2) Do I select all the check boxes in the "Data" section?

Would appreciate some help on this as I'm not really familiar with databases.

Ok, so I exported my entries. I saved it as an explorer page and it has all the pics I have used in my entries. The file is only 644k. Is this normal?

Also, I did it with Explorer and they said Explorer has a problem with exporting. Mine had the problem of all the text coming in with no spaces or paragraph returns.

So I just keep this on my hard drive if I ever need it and I'm able to import all the code and type, pics in my MT?

Thanks for the help. This stuff is hard!

Does anyone know how to get a full back of entries without using the Export feature in MT?

My problem is that the server I am on has a limit on processing time and when I try to use the export feature in MT I only get about 2 years of posts before it times out (leaving out the most recent years posts).

What I"m hoping to find is a Windows based program that would allow me to download my MT folder from the server and have it create a backup file I could then break up and upload into a new installation of MT.

Thanks all!

That depends entirely on what database you're using. If you're using MySQL, or some other SQL database, then it's easy. Just use your favourite database client (or whatever your host provider offers...I use phpMyAdmin) and dump the database.

If you're using Berkeley, then it's a little more difficult and will depend on if your host provider has the tools available. You would need db_dump to make a backup of your database tables.

I'm using the BerkleyDB...the problem I seem to have is my web hosting company doesn't have alot of the tools I need installed. That's why I was hoping I could just download a copy of the MT installation folder and then use a program to strip out the posts into a txt file I could then import into a new installation. I was hoping someone had written a little proggie that ran on Windows not the server itself....but thanks for the info!

Ryan

You could use the Multiple Archive Template feature to generate a second set of Monthly Archive files, using the export format and publishing to .txt files.

Then you'd have one .txt file for each month of entries.

Care to explain that one a little better? Also, I think this relates...I can't rebuild my archives except in batches of approx 100. I tried to just create a new index file that would list all my entries in the correct format, but the file won't build, too big. I'd be happy if I could create a index template and export 7-8 files (100 entries on each) but I'm not sure how to specific a date range for each index file.

(did that make any sense? lol)

What about TypeMover?

I have tried it, but I haven't fully tested it yet.

Another warning to do backup:

Server I use suddenly had a whole fileserver crash.

7 months of entries gone.

If any of you are with 1and1.com, frequently backup your stuff, they seem to go down a lot.

rckymtnrfc - you might find Backing Up Your Blog helpful.

Girlie:

One thing I don't understand about backing up. I use MySQL and periodically export using phpmyadmin. Since that export includes the templates and the data, why would I want to make a separate backup of templates and do a data-only export?

Thanks.

(This is covered in the Hacking Movable Type book in case you're curious about other neat database things to do.)
Export section: Export all tables (it's better to do this at the table level in case you need to rename your database at some point).

SQL section: Check the following:
- add drop table
- add AUTO_INCREMENT value
- enclose table and fieldnames in backquotes

Data section: Do not check any of the SQL insert syntax options but make sure that the export type is set to Insert

Save as File section: This spiffy format will save the data to your local computer in a nicely date stamped format: %Y%m%d%H%M%S-__DB__