Regular data backups are important for any store as they will help prevent serious data loss and corruption that can follow a disaster or mishandling of your store. So do never neglect the necessity of doing backups. Make it a rule! If your hosting does regular backups, good! However, it will be even better if you do spend some time and secure your store with an extra backup any time you decide to apply some major improvement, code customization, or upgrade. This is especially easy with X-Cart Backup Master.
The rule here is to create a full backup copy of the store regularly and before carrying out any tasks that may interfere with the software code and behavior, including software and hardware upgrades, custom programming, adjusting the store design, etc. At that, you should not rely on your hosting provider only, who is likely to include regular data backups into their hosting plan. In case of emergency, data cannot always be restored immediately, while any possible delay can seriously affect your business.
Another typical example of when you may need to back up your store is moving/copying the store to another host or directory. In such a situation, if a backup is available, you will be able to deploy a fully functioning copy of the store in a new location quickly.
When you create a backup copy of a store, you need to carry out some typical steps and procedures, which include making a database dump and creating an archive with the X-Cart code, templates, and related files (images, static pages, the HTML catalog, files in the folder file/, etc.). In fact, X-Cart does not impose any restrictions on what tools you use to create a backup copy of your store - you can use any convenient facility, including SSH, FTP, phpMyAdmin, Remote Desktop, utilities that go with your hosting control panel, and other available facilities. Of course, the exact set may vary depending on the operating system you use.
When you restore the store from a backup copy, it is supposed that you use the same tools and facilities to carry out inverse operations: restoring the store files from the archive and restoring the database content from the MySQL dump. In case you are restoring the store to a different location, in addition to this, you will need to adjust some configuration settings.