Micros 3700 Low Disk Space Warning

[eatatparkys]

Our Micros 3700 keeps gving us a warning message: "Warning--Server Disk Space Low, 245 MB Remaining." The number of MB continues to decrease and is now down to 47 in just a couple of days. We have cleared everything off the hard drive except for a Microsoft Office and our Micros software. Could we crash? The message is annoying and keeps popping up in every guest check entry.

 

[eatatparkys]

Problem solved. Spoke with Micros support. They advised me to check the Micros\Database\Data]Backup\Archive folder and delete any backup files that were marked .BAD and then to delete all backups except the most recent.

They said the problem was that when one backup went bad, it caused all new backups to be saved rather than be replaced with new ones. Eventually, it filled up the hard drive disk space.

Once I trashed those files from both my hard drives (we have two drives and backups are saved to both), the message went away.

Yay Me!

 

[pmegan]

Is your backup still generating .BAD files? If it is you'll run into this problem again. Micros is supposed to hold onto .BAD files until a successful backup is created, then delete all the bad backups.

 

[eatatparkys]

Micros concurs and instructed me to also purge any files mark .BAD.

I will look again and be sure the backups aren't starting to backup again. ; )

 

[pmegan]

I'd monitor them for a few days. If you're still getting .BAD backups the database will have to be rebuilt. It's an automated process, but the system has to be down and it can take a few hours depending on the size of your db. Micros can usually do this overnight.

Backups with a .BAD extension indicate that there's somthing wrong with your db and they usually can't be restored. I'm just worried that you're not protected if your db crashes.

 

[eatatparkys]

Thanks for your input. I checked the archives and it appears to be purging the old backups and only keeping the most recent three. I will continue to monitor every week or so.

 

[DrZogg]

A .bad file is where a compressed DB file does not pass validation.

I think you should take a time to perform a DB Validation, followed by a DB rebuild.

 

[eatatparkys]

I'm sure you're right, but we're probably talking a $200 service call, which I can't really afford. It's January in the restaurant business . . .

 

[DrZogg]

Hey,

Go to Start\Programs\Micros Applications\Utilities\Database\Validate Running Database

Select Next, then "all tables".

No special permissins are needed.

Save the results to File. The text document it produces, go through it with Notepad and press F3 to search for the word "error".

Delete all the lines that are not about the errors, this will give you a starting point.

 

[eatatparkys]

Thank you for your input. I tried what you suggested.

After I got to: Start\Programs\Micros Applications\Utilities\Database . . . choices then became a folder named Sybase Adaptive Server Anywhere or an app (I think) named Microbase Database Manager.

Never could find anything named Validate Running Database.

 

[DrZogg]

The other way to validate the database.

1. Select Start | Run type runbackup –c –p and and OK (–c is for
compression & –p is for validation)
Once complete both the Database and Log file are backed up,
validated and compressed. These backups reside in the following
directory D:\Micros\Database\Data\Backup
These backups will be date and time stamped (as below) and should
have a .good extension.