Hopefully, you saw the potential of Yurbi for your organization in our Demo mode and you’re eager to get going in “Bringing Your Data To Life®”
As we like to say, it’s time to start cooking with oil now.
But before we jump right in, here are a couple of things to know about backing up Yurbi. The most important thing to backup is the Yurbi backend database (remember back in the installation step, that was either in PostgreSQL or MS SQL).
If you accidentally delete a report or make a change to a report that you didn’t mean to, or you break your Yurbi App, or you have a complete server failure, if you have a recent backup of your Yurbi database, restoring Yurbi is a piece of cake (a tasty one).
Talk to your IT team and make sure they have included the yurbi database in their normal backup routine. If you are using MS SQL, that means using whatever SQL tools you normally use and include the Yurbi database in the configuration of those. Here are some steps to do it manually (but it needs to be automated).
If you are using the embedded PostgreSQL, that means the database is on the Yurbi server and you need to regularly (i.e. daily) make a copy of that folder. Here are some steps to do it manually (but again, it needs to be automated).
In addition to the regular daily backups, we recommend you back up:
- Before applying the latest Yurbi updates (always do a backup before applying the Upgrade file)
- Before doing a refresh of your MS Excel/CSV data (in case you import some bad data, you can easily recover)
- When you hit a milestone, like finishing up your Yurbi App or creating a pristine set of dashboards and reports
- Before doing any sort of mass update via the API or the interface (uploading a lot of users, security policies, etc)
When in doubt, make a backup.