paulWTAMU wrote:yeah, I wish. We can't do our own back up, and the exports ARE our backups. The do a full export, clean it up and simplify it for the public site and store a digital copy of the full export in a couple locations.
pikaporeon wrote:someone forgot to type commit;
What type of databases are you dealing with? Though I guess it'd just be one now.
I may be able to offer some advice / tips - if not to recovering your data, at least to do a local backup 'just in case'
[I know this isn't an effective backup practice, it just guards against when someone hits the wrong switch and wipes out the db]
Well, the above is a serious problem if this data is at all meaningful to your business. Backups are critical, in part to prevent exactly the sort of issue that you're dealing with right now. An export is not a backup; there are too many things that can go wrong as a part of an export.
What kind of a database are we talking about here, anyway? You mention in your OP that they somehow lost data in the exports and in the database itself?? That sounds awfully fishy to me.
BIF wrote:I will admit ignorance about Visionlink OS except for what I saw on their homepage.
It's a community OS, whatever that means. Doesn't seem to be an actual database, although a database could be whatever you call it...for example, I might call my spreadsheets "databases" (but that doesn't make them so, haha! ).
I suspect that Visionlink is either lacking in recovery capabilities when compared to a bonafide database such as SQL Server, Sybase, Oracle, DB2, or even "My SQL", or else the support staff may be lacking in recovery knowledge...
Users browsing this forum: just brew it! and 10 guests