We’ve often had questions come up on the forums ( like this recent one ) about what the best practice of backing up Sugar instances. Generally speaking, this is what we recommend…
- Backup the database Sugar uses on a minimum of a daily basis. The most common people run into with Sugar deployment management is needing to undo a change made, and the databases we support have tools to handle this well.
- Backup the codebase on a semi-regular basis. Typically most people make changes to the codebase very infrequently, and leveraging a VCS system is a good tool to use here ( see this blog post and this one for some ideas SDLC policies for Sugar ).
What are you best practices? Let us know in the comments below, as we are looking to have this post drive a KB article around this.