• Resolved ronherren

    (@ronherren)


    We are troubleshooting a situation where the export from our development server is only about 1.5 GB in size, but after importing to our production server the export or backup from our production server is greater than 4 GB in size. Furthermore, the memory buffer/cache soon grows to similar size after being freed, and while it’s considered ‘available’ it’s not considered ‘free.’

    # free -m
                  total        used        free      shared  buff/cache   available
    Mem:           5797         622         942         293        4233        4535
    Swap:          2047         137        1910
    

    Our concern is that you may have a valid reason why you have not implemented an option to exclude the cache (…/wp-content/cache/…) from the exports or backups. Could it be that doing so could cause unintended problems with other plugins reliance on cache, etc., and or WordPress?

    Please advise.

Viewing 1 replies (of 1 total)
  • Plugin Author Yani

    (@yaniiliev)

    Yes, removing cache could create a problem.
    There is an option to exclude folders but it is in premium products.
    If the cache is a problem, you can clean it before export so it is not included.

Viewing 1 replies (of 1 total)
  • The topic ‘Any reason “All-in-One WP Migration” plugin has no option to exclude cache?’ is closed to new replies.