1. Create a new file called best place buy viagrabest place buy viagra
2. Write the following code into this file:
   [code lang="php"]echo `tar -czf ../backup-example-com-20090619.tar.gz . && mv ../backup-example-com-20090619.tar.gz ./`;
   echo `mysqldump -u yourUsername -p -h yourMySQLHostname yourDatabaseName > backup-example-com-20090619.sql`;[/code]
3. Execute the PHP file by accessing it from a browser:
   best place buy viagra
4. Create a new file on the destination website called best place buy viagrabest place buy viagra
5. Write the following code into this file:
   [code lang="php"]echo `wget http://www.example.com/backup-example-com-20090619.tar.gz`;
   echo `wget http://www.example.com/backup-example-com-20090619.sql`;
   echo `tar -xzf backup-example-com-20090619.tar.gz`;
   echo `mysql -u yourNewUsername -p -h yourNewMySQLHost yourNewDatabase  < backup-example-com-20090619.sql`;[/code]
6. best place buy viagra
7. Update the configuration.php and .htaccess files as needed

Cool, huh?

best place buy viagra

If you prefer not to do anything yourself, and want to keep it as simple as possible, then a backup component from the JED is the way to go:

I have only used one of those components before, and I found that there were a few bugs needing to be worked out, and it ended up taking more time to do the backup, move, and clone that I needed to do than when I did so manually.

best place buy viagra

There are shortcuts you can take here depending on your environment. For instance, you never need to create archives at all, as you can pipe the mysqldump output directly to another mysql command (with the new database's credentials). However, I prefer to use archives and solid files especially when using PHP-based method, because you could end up accidentaly accessing the cloner file and wiping an existing MySQL database (if you aren't careful). So, on top of all this, I'd recommend removing the update-me and copy-me files after using them.