OroCommerce Forums

Covering OroCommerce topics, including community updates and company announcements.

Forums OroCommerce Recreate server from backup

This topic contains 2 replies, has 2 voices, and was last updated by  peeush 5 months, 2 weeks ago.

  • Creator
    Topic
  • #39625

    peeush
    Participant

    Hello – Can someone please provide be step by step guidance on recreating a production install on a new server? Specifically, I am unsure of the following:

    1. What should be backed up on a production server – database is obvious, but I am sure there must be other files/folders that need to be backed up (where are uploaded images and attachments in the application stored?).
    2. My production server has some Entity updates (done using System->Entities->Entity Management) like new Entities and new Entity Fields. What is required to move them correctly to the new server?
    3. Should any extensions/customisations (like new storefront UI theme bundle) be simply reinstalled? or is there a better way of backing these up and restoring them on the new server?

    Below is what I have tried:
    1. Installed application fresh on the new server.
    2. Stopped cron tasks and running consumers
    3. Restored the database
    4. Tried clearing the cache – that’s when I started getting errors (for example,
    In MappingException.php line 772: The target-entity Extend\Entity\EV_Customer_Customer_Type_Fe542000 cannot be found in ‘Oro\Bundle\CustomerBundle\Entity\Customer#customer_type’.)

    Many thanks for your help!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
    Replies
  • #39650
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    Hi, Peeush.

    Reinstall is not an option when you move the website to another server.

    Please follow the below steps:
    1) Copy all the source code from an old server to the new one, except var/cache and var/logs folders. Or when you prefer to install from SVC, copy Assets in var/attachments and public folder and artifacts in var/import_export folder, they are required.
    2) Change credentials at the config/parameters.yml file for the database and optionally to other used services (ElasticSearch, RabbitMq, Redis etc).
    3) Copy the database
    4) Follow the upgrade guide from step #7 (or step #6 if you haven’t copied all the vendors from the previous server). This will warm up all the required caches and so on.

    #39652

    peeush
    Participant

    Thank you for guiding me in the right direction Andrey! I will try out the steps you have outlined and will reach out if I am still running into issues.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

You will be redirected to [title]. Would you like to continue?

Yes No