I have a customer running ASA v8.0.2.4322 (windows environment using
dbsrv8). She setup an automated backup using a "Backup" event. When the
event kicked off it was not able to write to the path specified in the
event. The backup failed and the two databases she attempted to backup are
now corrupt. Any attempt to login to those databases or to recover them
gives a windows level crash. (no sybase errors are displayed).

Is this a known issue? Has anyone run across this before? Any ideas on
possibly recovering the 2 databases?

Hmmmm



Are they backing up to the same drive where a database file exists?
Any .LOG, .MLG, .DB or a dbspace files there?

If so, running out of backup target diskspace also means running out
of production disk space. That latter event, could cause the server
to come to a grinding halt and go down dirty.

Failure to log into a database usually means log file corruption.
Failure to recover could also be log file corruption but it could
be a checkpoint problem as well.

Since the log file continually grows (even during a backup of the
log ... except at the last page ...) this outcome does indicate the
possibility that the log files are on the same drive as the target
directory for the backups.


Treat this the same way as an assertion failure

http://www.sybase.com/detail?id=1010805


If going to previous backups out of the question?
If so, try to apply (automatic recovery) or translate the current logs
and manually apply the SQL (after some investigation and editing).

Depending upon your situation (replication etc) you may or may
not be able to hide the current logs and try to dbeng -f the databases
1 at a time.

If nothing works for you, then you may want to consider paying for our
salvage service [described in that link above]





"David DeRam" <ns_xxxdderam (AT) progenyns_xxx2000 (DOT) com> wrote

i believe the situation that they ran into was they tried to set up a server
backup from their client machine. however, when they specified the
directory to backup to they entered the mapped drive on their local machine,
not the actual path on the server machine. as stated in the earlier post,
when it tried to back the databases up, it failed and now the databases
cannot be opened.

-f did not work. i deleted the log, ran dbeng8 -f and it produced the same
windows error.

thanks for the help, i will look into the assertion failure link you
provided. hopefully it does not come down to paying for the salvage
service, but nothing we've tried has worked yet.

"Nick Elson" <no_spam_nicelson (AT) sybase (DOT) com> wrote

Can you reproduce this on a consistent basis? We've love to see a repro if
you can.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"David DeRam" <ns_xxxdderam (AT) progenyns_xxx2000 (DOT) com> wrote

Do you have a better description of the "Backup Event"? We
are using a combination of dbbackup.exe and xcopy.exe and
have encountered a fairly wide range of network, technical
and disk space issues without ever losing both ends of a
backup.