The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Recommended Backup/Restore Strategy
Posted: 08 Oct 08 9:40 AM
|
Recommended backup strategy
Hi everyone,
I would like to just get some suggestions with regards to backing up / restoring Saleslogix. From what I can gather so far, is that you need at least a recent backup of the Database as well as an up-to-date web-bundle.
So, please let me know what experiences / tips you have with regards backing up AND restoring (should your server blow-up  )
Regards
Al
|
|
|
|
Re: Recommended Backup/Restore Strategy
Posted: 08 Oct 08 11:30 AM
|
| For 7.2 just a database backup will do - and the documents/library folder where you store the attachments and library documents. |
|
|
|
Re: Recommended Backup/Restore Strategy
Posted: 08 Oct 08 11:30 AM
|
| For 7.2 just a database backup will do - and the documents/library folder where you store the attachments and library documents. |
|
|
|
Re: Recommended Backup/Restore Strategy
Posted: 08 Oct 08 11:31 AM
|
For 7.2 just a database backup will do - and the documents/library folder where you store the attachments and library documents.
You can rebuild the web app from the database backup no problem.
Sorry about the repeated posts - I blame Google Chrome |
|
|
|
Re: Recommended Backup/Restore Strategy
Posted: 08 Oct 08 4:18 PM
|
| Hi Al. We are doing some pretty cool stuff with a BDR device to maintain backups of the SLX environment, but more importantly provide the ability on the BDR hardware to virtualize the entire environment as fail-over for the Production systems. We call it our "Runflat tire" for Saleslogix. In terms of individual file and stuff Nick is right on there's not a lot to it, but recovering the environment to keep business going if a server fails is a little trickier. |
|
|
|
Re: Recommended Backup/Restore Strategy
Posted: 08 Oct 08 4:48 PM
|
Do people here also back up the SyncLogs folders?
What happens if the effective backup times for sync logs, documents and database are all slightly different (and therefore out of step)? Thankfully, I've never yet had to deal with this one. I imagine that the Integrity Checker will help track down most anomalies afterwards ...
Phil |
|
|
|
Re: Recommended Backup/Restore Strategy
Posted: 09 Oct 08 6:47 AM
|
| We tried this once, no use. Too many sync irregularities. Once you have to restore a DB, you have to create remote databases for everyone. |
|
|
| |
|
Re: Recommended Backup/Restore Strategy
Posted: 09 Oct 08 9:16 AM
|
Essentially yes - it is a enough. As long as you havent stored the backups on the server disk that crashed 
Like Todd says though, there is still the arduous task of recreating your server environment. I ghost servers from time to time so I have an image I can restore from. Way easier.... |
|
|
|