|
I'm not able to restore a database I'm getting the following error: the backup file is from a Sybase SQL Anywhere 11 > [Sybase][ODBC Driver][SQL > Anywhere]Error during backup/restore: > unable to open device > E:\\Micros\\MICROS_2013_06_07_09_36.mbz5 > (Unknown err status reading HDR > labels) SQLCODE: -697 SQLSTATE: HY000 > SQL Statement: RESTORE DATABASE > 'E:\\Micros\\micros.db' FROM > 'E:\\Micros\\MICROS_2013_06_07_09_36.mbz5' |
|
Now when I try to connect to the db it ask for the encryption key. How do I backup and restore with the encryption key? 1
If you don't have the encryption key, you may be out of luck... especially if it is strong encryption. You are also going to need a user id and password. I am not familiar with Micros software, but the vendor may not want you copying the database without permission, etcetera. Try this Google search... "micros" encryption
(07 Jun '13, 14:02)
Breck Carter
|
Petar, do you know how the backup was created? The file name makes me suppose that some kind of compression was applied after the backup.
I don’t know really. But looks like you are correct. I crated my own backup and it work.
Petar, is this a Micros setup? Isn't there already a backup-and-recovery infrastructure delivered with the product? Just asking...
Indeed it is. I am trying to run a copy of the DB only on a workstation that has no EM software install.
OK... there are three basic techniques for copying a SQL Anywhere database, and you may have picked the most difficult.
First technique: Shut down the engine or server normally, then do a file copy of the *.db and *.log file to the new location. The "new location" can even be different hardware, the database file is binary-compatible across, say, different endian computers.
Second technique: If you can't shut the database down, you can create an "image backup" which results in almost the same thing: copies of the *.db and *.log file which can be copied to another location and started there; in this case, the server must to a bit more "recovery" work when starting the database but that's automatic.
Third technique: Create an "archive backup" which is a throwback to the days of tape drives, and it's the only one that requires the special RESTORE command to be used to deal with the special file that is created.
If you need techniques 2 or 3, we can help... BUT I think you can just use the first technique. Important note: SQL Anywhere is not Oracle or SQL Server or MySQL... SQL Anywhere is simple to use :)
Bottom line: If the server will start your copy of the database, then you did it correctly.