Drimmie Posted February 18, 2004 Posted February 18, 2004 Hello :) I am currently running OSc Version 2.2-MS2. OSc is already up and running on my web server as well as a local copy that I installed w/ Apache for Windows. Since I have a slow dial-up 'net connection, I prefer updating our product catalog locally then uploading it to the server at the end of the day. The problem is that when I go to "Restore" the DB w/ the Backup tool, my browser appears to be uploading and then I get "Page cannot be displayed" error. Nothing gets updated and I'm left being upset and frustrated. Believe me, I have searched thru this forum for the past week and a half trying to find a solution, unfortunately I had no luck and am now forced to bother you guys :( My ISP is running MySQL 3.23.41 as well as PHPMyAdmin and the "admin/backups" directory is CHMOD'd to 777 as well as the .sql file that i uploaded to that directory to be restored. Is there any way I can get this updated .sql file/catalog up on my site? The only solution I found so far is to upload the /install directory back up on to the server and then replace the default .sql file w/ the current one that I want to restore Thanks in advance for any help given Jason D.
Guest Posted February 18, 2004 Posted February 18, 2004 when you "restore" the db, do you upload the file FIRST, then tell osC to restore the db from a local file, or do you do the upload/restore at the same time? uploading the file first would be better, and phpMyAdmin doesn't seem to like long operations (at least that's what I've seen). -jared
Drimmie Posted February 19, 2004 Author Posted February 19, 2004 when you "restore" the db, do you upload the file FIRST, then tell osC to restore the db from a local file, or do you do the upload/restore at the same time? uploading the file first would be better, and phpMyAdmin doesn't seem to like long operations (at least that's what I've seen). -jared I upload the file first via FTP to the catalog/admin/backups directory. Drimmie
Guest Posted February 20, 2004 Posted February 20, 2004 Sometimes, when the file is large, the db restore seems to bomb out. that happened to me yesterday, in fact. If you have a shell account (i.e. SSH) you can issue a MySQL command from the command line to restore it. The admin utility will give you the suggested syntax if you click on the "restore" button on the right. NOT the one next to the "backup" button, the one next to the "delete" button. You *could* drop all tables with phpMyAdmin, then upload your database in pieces -- edit it with a text editor like Crimson Editor (handles large files well -- good Windows freeware editor) and chop it up into pieces. If you do that, just make sure to do it by full sections. I don't know of any better way to do it. Wish I did. -jared
Drimmie Posted February 20, 2004 Author Posted February 20, 2004 I am not too familiar with Shell access (my isp has granted it tho). The command line you are referring to, how do i access this? Thank you
Guest Posted February 20, 2004 Posted February 20, 2004 you'd access it either via telnet (insecure) or ssh (secure). A free telnet/ssh client is easily locatable from google. My favorite is putty.exe . -jared
Nick1 Posted March 12, 2004 Posted March 12, 2004 when you "restore" the db, do you upload the file FIRST, then tell osC to restore the db from a local file, or do you do the upload/restore at the same time? uploading the file first would be better, and phpMyAdmin doesn't seem to like long operations (at least that's what I've seen). -jared I upload the file first via FTP to the catalog/admin/backups directory. Drimmie This worked for me, I uploaded it to that folder and restored it using Tools -> Database Backup since restoring from local file didn't work thanks
Recommended Posts
Archived
This topic is now archived and is closed to further replies.