Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
3.2.7
-
None
-
None
-
Backup created on AMPPS 3.3
Board version: 3.2.7 (successfully upgraded from v2.0.2x modified)
Database size: 395.41 MiB
OS: Windows NT LEN 5.1 build 2600 (Windows XP Professional Service Pack 3) i586
Apache 2
PHP version: 5.4.43
Database server: MySQL(i) 5.6.25
Restore performed on Linux server
Board version: 3.2.7 (clean install)
Database size: 397.88 MiB
OS: Debian 4.9.168-1+deb9u4 (2019-07-19) x86_64
Apache 2
PHP version: 7.0.33-0+deb9u3
Database server: MySQL(i) 10.1.38-MariaDB-0+deb9u1
Backup created on AMPPS 3.3 Board version: 3.2.7 (successfully upgraded from v2.0.2x modified) Database size: 395.41 MiB OS: Windows NT LEN 5.1 build 2600 (Windows XP Professional Service Pack 3) i586 Apache 2 PHP version: 5.4.43 Database server: MySQL(i) 5.6.25 Restore performed on Linux server Board version: 3.2.7 (clean install) Database size: 397.88 MiB OS: Debian 4.9.168-1+deb9u4 (2019-07-19) x86_64 Apache 2 PHP version: 7.0.33-0+deb9u3 Database server: MySQL(i) 10.1.38-MariaDB-0+deb9u1
Description
I just wanted to report a problem I encountered. When changing from one server to another, I used phpbb's back up feature to create a database file. When restoring on the new server, (1) I got a "selected file to backup is invalid" message. This is a known issue that is fixed by correcting line 219 in /includes/acp/acp_database.php. With that fixed, (2) I proceeded to restore the database but was unsuccessful. From what I could tell, most of the basic table structure was in place but only a small fraction of content was filled into the tables, and user information was completely absent. To work around this, on the command line I ran `mysql -u -p dbname < dbfile.sql` (using the same file but uncompressed) and so far everything appears good. My conclusion is the backup worked correctly but restore has issues.
I hope this helps.