Corrupt data fields within sugar

[cmiller]

With admin rights, and custom fields created-- how do I address corrupted files? Data integrity has been compromised ... what admin functions allow me to rebuild the data structure w/out risking loss of custom fields ? running Sugar Suite 4.2.0 please help

[Angel]

We may be able to give you some better assistance if you were to provide us with some details on what type of corruption you are seeing.

Do you mean the data itself is corrupt? In which case, I would look at the SQL server itself.

Or is the problem that Sugar isn't displaying your custom fields correctly?

Please elaborate.

[chrisky]

With admin rights, and custom fields created-- how do I address corrupted files? Data integrity has been compromised ... what admin functions allow me to rebuild the data structure w/out risking loss of custom fields ? running Sugar Suite 4.2.0 please help

Without even thinking of touching the topic of possible solutions for whatever your specific problem is....I do want to touch on what I believe is the MOST IMPORTANT thing.

*Personally I'm barried in the chaos of backups.. I've got so many copies, duplicate copies, triplicate copies, and other backups spanning across the hard drives of numerous servers, my personal machines, my notebook, etc. *Laughing aloud*

I honest can't keep track of them all, and every so often (week or two) burn all those various tar files and backups sitting on 15-20 hd's of various machines or servers, all to a dvd.

To my point, IMMEDIATELY, and especially before you even USE or login into the crm again, you want to recursively tar up the crm and backup the database!

Command line wise, this is my preferred and only used method for backing up sugar installations, i.e. my own example would be along these lines :
cd /var/www/html
tar cvzf sugar450b-backup-server12-92506-1130pm.tar.gz sugarcrm450b/

Then backup your sugar sql database!!! If you're running a lamp server (which you should be) then you should have webmin installed and if not, make it a priority!

Via webmin or phpMyAdmin, go ahead and backup your sql database..

THEN, and only then, should you proceed further...

But then again, my methods are based upon the premise that you have data or customization [of sugar] that you do not wish to lose or have broken..

And, just as Angel was addressing... You need to get WAY specific with regards to what you mean by 'corrupt data fields' , exactly what data or output is corrupt, and just exactly what is being displayed, when and just what do you do or attempt to do or access that results in this 'corrupt' data that you describe..

well... No offense, but I've got work to do and not the time for your difficulty.
I did however want to give you some input on backing up properly a sugar installation which will be critical in resolving difficulties, problems, bugs, and breaks as they will continue to constantly arise..

Good luck,