Re: Disappearing data

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 43017
interpreted = N
texte = Kenneth Grome wrote:[snip]> > This will not solve the problem if the RAM-cached data gets screwed > up and then WebDNA writes that bad data to disk thereby overwriting > the 'good' data that was stored on disk. The only real solution to > this problem is to duplicate your db files at periodic intervals, and > then preferably to store those duplicates offline or on another > volume.yes, a synchronizeing backup is your friend here.> > > >We have 1500 products or so in our main store and > >haven't lost a single character. > >Site has been running for approx. 8 months or so now. > >MacOS - 4.5 > > 1500 products is a very small db compared to the db's some other > people are using. And this problem may also be related to how busy > the store is. It may just be that you will never see the same > problems others are experiencing -- until your db gets big enough to > start creating those problems, or until your store gets so busy that > ot severely taxes webcat's ability to keep up with the traffic.I agree.> I would tend to think that this data loss problem may have something > to do with how much RAM is available for the webcat db's to reside > in. If RAM is too limited then webcat has to perform repetitive db > swaps into and out of memory. If this is happening a lot, especially > on a busy site, it seems like there would be a much higher chance for > data corruption (since there's far more writing of data to disk) than > on a site that never has to swap db's into and out of RAM ... > > Sincerely, > Kenneth GromeI also manage a 400+ gig file server with a gigE backbone utilizing RAID that is hit pretty hard by a hungry group of Pre-Press Artists.If we lose (see Rob I can occassionally spell if I put my mind to it) the data on this machine then we might as well tell our 100+ employees to go find another job. We have 3 levels of back up on this machine. RAID 1 (for instant uptime in case of failure) DAILY backup that spans approx 3 months: (so we can recreate the drives how they were at any one of those days) And finally alternating backups. (We are also supposed to store the alternate backups offsite but in hindsite we've lost site of that part.) ;-)DonovanP.S. my point being that backup all depends on how imparative it is to not lose that data... ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Disappearing data (Timur Ruban 2002)
  2. Re: Disappearing data (Timur Ruban 2002)
  3. Re: Disappearing data (Kenneth Grome 2002)
  4. Re: Disappearing data (Donovan Brooke 2002)
  5. Re: Disappearing data [OT] (Donovan Brooke 2002)
  6. Re: Disappearing data (Bob Minor 2002)
  7. Re: Disappearing data (Dan Strong 2002)
  8. Re: Disappearing data (Kenneth Grome 2002)
  9. Re: Disappearing data (Timur Ruban 2002)
  10. Re: Disappearing data (Dan Strong 2002)
  11. Re: Disappearing data [OT] (Rob Marquardt 2002)
  12. Re: Disappearing data (Sal D'anna 2002)
  13. Re: Disappearing data (Donovan Brooke 2002)
  14. Re: Disappearing data (Timur Ruban 2002)
  15. Re: Disappearing data (marc malacarme 2002)
  16. Disappearing data (Timur Ruban 2002)
  17. Re: Disappearing Databases (Larry Hewitt 2000)
  18. Re: Disappearing Databases (Kenneth Grome 2000)
  19. Re: Disappearing Databases (Larry Hewitt 2000)
  20. Re: Disappearing Databases (Kenneth Grome 2000)
  21. Re: Disappearing Databases (Paul Uttermohlen 2000)
  22. Re: Disappearing Databases (Kenneth Grome 2000)
  23. Disappearing Databases (Alex Cheparev 2000)
  24. Re: Disappearing Database (Ross Markbreiter 1998)
  25. Disappearing Database (Angel Bennett 1998)
Kenneth Grome wrote:[snip]> > This will not solve the problem if the RAM-cached data gets screwed > up and then WebDNA writes that bad data to disk thereby overwriting > the 'good' data that was stored on disk. The only real solution to > this problem is to duplicate your db files at periodic intervals, and > then preferably to store those duplicates offline or on another > volume.yes, a synchronizeing backup is your friend here.> > > >We have 1500 products or so in our main store and > >haven't lost a single character. > >Site has been running for approx. 8 months or so now. > >MacOS - 4.5 > > 1500 products is a very small db compared to the db's some other > people are using. And this problem may also be related to how busy > the store is. It may just be that you will never see the same > problems others are experiencing -- until your db gets big enough to > start creating those problems, or until your store gets so busy that > ot severely taxes webcat's ability to keep up with the traffic.I agree.> I would tend to think that this data loss problem may have something > to do with how much RAM is available for the webcat db's to reside > in. If RAM is too limited then webcat has to perform repetitive db > swaps into and out of memory. If this is happening a lot, especially > on a busy site, it seems like there would be a much higher chance for > data corruption (since there's far more writing of data to disk) than > on a site that never has to swap db's into and out of RAM ... > > Sincerely, > Kenneth GromeI also manage a 400+ gig file server with a gigE backbone utilizing RAID that is hit pretty hard by a hungry group of Pre-Press Artists.If we lose (see Rob I can occassionally spell if I put my mind to it) the data on this machine then we might as well tell our 100+ employees to go find another job. We have 3 levels of back up on this machine. RAID 1 (for instant uptime in case of failure) DAILY backup that spans approx 3 months: (so we can recreate the drives how they were at any one of those days) And finally alternating backups. (We are also supposed to store the alternate backups offsite but in hindsite we've lost site of that part.) ;-)DonovanP.S. my point being that backup all depends on how imparative it is to not lose that data... ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Donovan Brooke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Req: Row DB feature (2004) WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997) My X-Mas Wish (1999) Possible to reset Linux file permissions w/in webcat [shell] ? (2000) Emailer (1997) triggers (2000) WebCat for Unix?? (1997) Plugin or CGI or both (1997) Yet another db manager (2004) [WebDNA] TCPConnect w/ user:pass (2009) t or f (1997) Banner DNA (1997) HideIf ip= OR ip= (1998) OT: Weird table rendering w/ WebCat in Explorer (2005) Include a big block of text (1997) [WebDNA] Friday's.. WIP thread (2009) ghost dbs!? (2003) TeaRoom (1997) Newbie problem blah blah blah (1997) Erotic Sites (1997)