The following procedure describes the basic needs for moving your magento-shop to another server. There might be additional things to consider (changing domains, DNS, PHP-Configuration, tools & programms on your server) which need to take care of on your own.
1. Backup files in your Magento directory on your old server:
You might empty your var/cache, ...
It is fine to change the data type to InnoDB, assuming one of the following is true:
You are using MySQL 5.6.4+ where the InnoDB storage engine supports fulltext search
You are not using the default Magento Search functionality which relies on underlying MyISAM fulltext search capabilities. That functionality is troublesome to begin with and the feature ...
Note: More detail on the Magento code that causes the issue and how to clean up over here...
The Magento backup system in 1.6 and later has an unfortunate feature where it will change certain file/folder permissions which then can fall afoul of security measures like SuExec, SuPHP or cPanel WHM settings.
The root error that causes a 500 error page will ...
1) You need to get the sql dump from the old database and import the sql file in the new database.
2) You need to make change in the local.xml. To do so goto app/etc/local.xml
Enter the username, password and dbname of the new database you created.
NOTE : Normally host name as localhost works. But for some servers you need to get the host name from the ...
You should always use the --single-transaction option when dumping an InnoDB/Magento database. I'm not sure if it prevents tables from being locked (couldn't find any reference), but it will give you a consistent snapshot of the database you're backing up at least.
Without this command, you will dump data as they are written to the database real-time, and ...
There is a function in n98-magerun that allows for developer backups that allows removal of several table groups from the backup. If the table groups don't include a table you want ignored, you can also list the tables out in an ignore list that may also include the predefined group.
$ n98-magerun.phar db:dump --strip="@stripped"
$ n98-magerun.phar db:...
To expand on Marius's comment above, the best solution would be an extension which contains setup scripts which insert each of these attributes. n98-magerun.phar can be handy here. n98-magerun.phar dev:module:create can create the basic module structure for you. Then you can use n98-magerun.phar dev:setup:script:attribute to create setup scripts based on ...
It depends on the version.
For CE 1.5 and lower you can only back-up your database.
In version CE 1.6 you can back-up your media folder also along with the database, and you can back-up the file system of your Magento instance. All files and folders.
Starting CE 1.7, in addition to what CE 1.6 offers, you can choose to back-up your file system ...
It may be that Magento doesn't have write permissions to your var/ directory and uses system temp directory instead.
Look on Mage_Core_Model_Config_Options::getVarDir() method implementation. If Magento uses system tmp directory as fallback, your backups can be created in /tmp/magento/var/backups/ directory.
Probably there is no need to copy keys to the backup table, just store the data. You can create foreign keys when (if) you restore.
Moreover, you're adding foreign key for parent_item_id column referencing item_id from original table, but should reference it from this new table you're creating, this might be reason of the issue.
So just delete all the ...
So just came across this error myself, thought I might mention it for those who may come across this in future (since it does block updates).
Looks like the db dump crashed while trying to add rows for or around "importexport_importdata" table
A quick glance it looks like a small issue with not checking for a non-zero denominator.
The code/file in ...
Since the 2.2.0 release the customer_group_id field has type INT(10):
CREATE TABLE `customer_group` (
`customer_group_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`customer_group_code` varchar(32) NOT NULL COMMENT 'Customer Group Code',
`tax_class_id` int(10) unsigned NOT NULL DEFAULT '0' COMMENT 'Tax Class Id',
PRIMARY KEY (`customer_group_id`)
To make sure cronjobs are executed, start off by installing the excellent AOE Scheduler: http://www.magentocommerce.com/magento-connect/aoe-scheduler.html
After installing this you'll know whether cronjobs are running, which ones are and at what time.
If they aren't working please write in details what you have done so far to get cronjobs running. (what ...
I want to add one more useful suggestion:
In order to simplify the process of migration from one server to another, I would suggest you copying files over ssh instead of downloading and uploading zip files, as It's much faster and efficient way.
scp -r <source> <destination>
To copy a file from B(new server) to A(old server) while ...
I won't repeat the other answers. Some advice:
Download and zip the entire folder and keep it for a long time as a backup.
Backup the database, zip it and keep it as backup.
Set rights for all files properly, not only those in the var and media folder.
Let the old install run until you know how to move the install in one go.
Create a test store on the new ...
I think this is more related to http://dba.stackexchange.com and has already been answered there quite often.
Take a look:
How can I optimize a mysqldump of a large database?
How can I backup a large SQL Server database without impacting performance?
Best practices for backing up a MySQL DB
For a quick and easy solution where you could stick to mysqldump ...
Why don't you try to copy the entire database ? Then you only has to change all the old URL for the new ones. ( for example the old URL www.oldone.com/x to -> www.newone.com/x ).
What I do is to copy the old database, change the urls automatically and then upload to the new database.
Hope this can help you.
See the screenshot:
After Backup file path
1) assign your backupname.
2) after create click on .gz format.
If generate error on backup time:
What I'm doing is changed the PEAR file permissions to 755
To change the PEAR file permissions, I need to go thru my File
Manager on hosting cpanel.
I have ...
This should definitely be possible as long as any changes in between two time period were minimal.
I suggest that you test this with a staging environment first.
To do so, create new directory and a new database.
After that, update "/app/etc/local.xml" to reflect the
new database name, username, password
and clear all caches and sessions under "/...
Most likely a timeout of some type was encountered, be it either a MySQL or PHP timeout.
You are correct with the assuming the backup is triggered via cron:
I would double check MySQL's timeout and logs as PHP's timeout is set to 0 to avoid such issues when the cron job is executed:
The best and safest route is doing manual backups via CLI, with mysqldump,...
I finally managed to find the correct php error log on this stupid server:
mod_fcgid: read data timeout in 61 seconds
Solution is to increase FcgidIOTimeout and FcgidBusyTimeout massively. As this process runs very slow (multiple hours in this case) and the store is not loading during this time this is not a good option for me. If you have a small store it ...
The absolute simplest method.
If you have SSH access and the disk space, the easiest way is to create a tarball (archive similar to windows Zip) of your webserver doc root and a compressed mysqldump of the database to a backup folder in your home directory (above your web server doc root so it's not web accessible).
Use SFTP to download the tarball and ...
You need to rewrite the model Mage_Backup_Model_Fs_Collection and replace this line
$this->_baseDir = Mage::getBaseDir('var') . DS . 'backups';
with the folder you want.
Also rewrite the helper Mage_Backup_Helper_Data and change the return of the method getBackupsDir. Make it return your folder.
the folder has always been var/backups.
See the method Mage_Backup_Helper_Data::getBackupsDir()
public function getBackupsDir()
return Mage::getBaseDir('var') . DS . 'backups';
it's there in 1.9 and it has been there since the backup module was introduced.
Make sure the folder is writeable and you have enough disk space.
I was half ...
I'm not aware of a ready made script to make a development copy of a site and a database.
As a freelance Magento developer, I've worked in many teams and companies. Every one had their own development and deployment methodology.
Creating a development backup of a site would have been different under every circumstance, too.
That said, it almost never ...
Based on the comments above, the original poster solved this problem by
changing the permission for index.php fromm 666 to 644
This is likely a security precaution of their shared web host — many shared web hosts systems consider 666 an invalid permission and have special monitors in place to prevent users from serving such files.
Thanks for all the help. I fixed it easily using FileZilla FTP, I just selected the root folder for magento and changed permissions for all files and it did it automatically. No running of scripts required.
FileZilla also has an option for changing all folder permissions automatically.
Hope it helps.