Hello Jon, just for your and the mailing lists information. Starting from 7.6.00 the medium name does not longer determine the usage of an external backup tool. "Unfortunately" you used 7.5.00.
Best regards, Tilo Heinrich SAP Labs Berlin -----Original Message----- From: Jon Loken [mailto:[EMAIL PROTECTED] Sent: Monday, August 22, 2005 5:45 PM To: maxdb@lists.mysql.com Subject: RE: File bsi.env is missing or unreadable - SOLVED Hi again, My apologies for sending the last email as it is not relevant. A previous email referencing the bsi.env missing issue is correct and WAS the solution to my problem. I.e.: When making a backup, ENSURE that the MEDIUM name does not start with characters "back". Regards Jon -----Original Message----- From: Jon Loken Sent: 22 August 2005 16:31 To: maxdb@lists.mysql.com Subject: File bsi.env is missing or unreadable Hi All, I have created an instance based on a backup on a Linux machine through the windows management GUI, where I logged on as a non-root user (The non-root user was included in group sdb). The installation seems to work fine. However, when I try to make a new backup in order to activate auto-log, I get an error message saying: "/var/opt/sdb/data/wrk/KAINAO/bsi.env is missing or unreadable". There is indeed no such bsi.env file. Googling told me that the backup file should not start with "BACK". This is not relevant in this case, as I have tried several file names to no avail. Have I lost it? Any ideas? Thanks for your help! Many regards Jon Kernel version: 7.5.0 Windows GUI client: 7.5.00.18 -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
