Re: Backup is missing some records

Hendrik,

Shut down the database and do a filesystem level back up of the 
database, then run the repair tool.  The repair tool will rebuild the 
indexes and report any errors with the index on the table in question. 
If the problem is with indexes, this should correct any problems and fix 
the backup problem.

You can perform a system level backup of the files in the 'data' 
directory while the database is live, however you should ensure that no 
operations are performed on the database while it happens.  Copying the 
data files like this, and then restoring later will be like starting a 
database after a system failure.  The journal logs will be used to 
rebuild the database up to the last commit.  The most robust solution 
would be to cleanly shutdown the database, perform the backup of the 
data files, and then restart the database.

Toby.

Hendrik Schwachenwalde wrote:
> The records that are missing in the backup were
> already present before the backup was made. They are
> still present in the database but they are not
> included in any subsequent backups either. I assume
> that an index might be corrupted/not updated when
> these records were added (ca. 15 records out of 7580).
> 
> At this point I have a couple of goals:
> 
> I would like to make a copy of all the data files at
> system level (like: mkdir snapshot;cp data/* snapshot)
> while the McKoi database is running but with no
> processes connected preserving that corrupted state. I
> would then zip all snapshot files move the archive to
> a different computer, unzip them there in the data
> directory of McKoi and hopefully have a copy of the db
> in the corrupted state. The reason for this is because
> the application connecting to McKoi behaved strangly
> when walking over those records (before and after the
> backups) and I would like to figure out exactly what
> happens. Unfortunately I cannot do that on the
> original computer (production system running 24/7).
> 
> The second goal is to figure out a way to validate a
> backup against the db. Surprisingly the backup call
> does not report anything unusual! If I hadn't been
> interested in those records I would have never figured
> out that something is missing! Therefore I need a way
> to make sure the backups are ok. Does the backup call
> create any log entry with a timestamp that I could
> programatically use to determine which records (with a
> creation timestamp field) were already present when
> the backup started and which  ones were created later?
> 
> Finally a need to fix the db, but of course only after
> I saved the corrupted state for further investigation.
> Fortunately the whole problem is limited to these
> missing records. Everything else is fine.
> 
> I hope that clarifies the context of the backup
> problem.
> 
> Thanks in advance,
> Hendrik
> 
>  --- Tobias Downer <[email protected]> wrote: 
> 
>>Hi,
>>
>>Using the live system backup function, the copy made
>>should be the 
>>database in the state it is when the backup is made.
>> If any records are 
>>added or removed during the backup, this change will
>>not be present in 
>>the backed up version.  In other words, the backup
>>copy will be the 
>>state of the database at the last commit immediately
>>before the backup 
>>command was run.
>>
>>What sort of records are missing from the backup? 
>>Is it records that 
>>have recently been added or longer term records? 
>>You should expect that 
>>records added close to or during the backup command
>>will not make it 
>>into the backed up version.
>>
>>Toby.
>>
>>Hendrik Schwachenwalde wrote:
>>
>>
>>>Hi Toby,
>>>
>>>I am in the process of tracking down a weird
>>
>>problem
>>
>>>regarding missing records in the backup. In order
>>
>>to
>>
>>>nail the cause I would like to know if the files
>>>created by the backup system call should be:
>>>
>>> 1. an exact copy of the files in the data
>>
>>directory
>>
>>>of the still active database if nobody has issued
>>
>>any
>>
>>>SQL commands since the backup was made, or
>>>
>>> 2. an exact copy of the files in the data
>>
>>directory
>>
>>>after database shutdown if nobody had issued any
>>
>>SQL
>>
>>>commands since the backup was made.
>>>
>>>Would creating unused connections to the database
>>>after the backup have any impact on the files in
>>
>>the
>>
>>>data directory, and if so on which ones?
>>>
>>>Do you have any suggestions what might cause
>>
>>records
>>
>>>to be missing in a backup?
>>>
>>>The problem occured on a backup of a McKoi 1.02
>>>database running in standalone server mode btw.
>>>I am restoring on a different machine running
>>
>>McKoi
>>
>>>1.03! Is there something that should be aware of
>>
>>when 
>>
>>>restoring from an older version? I have done that
>>
>>on
>>
>>>several occasions without encountering any
>>
>>problems so
>>
>>>far.
>>>
>>>P.S.:
>>>Thanks Toby for this excellent database.
>>>I really enjoy using it!
>>
>>
>>
>>
> ---------------------------------------------------------------
> 
>>Mckoi SQL Database mailing list 
>>http://www.mckoi.com/database/
>>To unsubscribe, send a message to
>>[email protected]
>>
>> 
> 
> 
> ______________________________________________________________________ 
> Post your free ad now! http://personals.yahoo.ca
> 
> 
> ---------------------------------------------------------------
> Mckoi SQL Database mailing list  http://www.mckoi.com/database/
> To unsubscribe, send a message to [email protected]
> 
> 



---------------------------------------------------------------
Mckoi SQL Database mailing list  http://www.mckoi.com/database/
To unsubscribe, send a message to [email protected]