How to do a full restore of xampp

Problems with the Windows version of XAMPP, questions, comments, and anything related.

How to do a full restore of xampp

Postby gwmbox » 29. October 2014 04:19

Hi all

Can someone please guide me on doing a full restore of my xampp please. I had a hard drive failure, but I had a backup of the full xampp directory on my backup drive.

Can someone point me to read about or guide me on how to do a proper working restore please.

I have tried to install a fresh copy of xampp and then copy over the stuff in htdocs and the mysql data folder but mysql will not startup

I also tried just copying everything from the backup to the new xampp folder by overwriting everything but that did not work either,

What am I doing wrong please

Win 8.1 Pro, Xampp 1.8.3, exe install, E:/xampp (its own partition)

Logs
1:41:09 PM [main] Initializing Control Panel
1:41:09 PM [main] Windows Version: Windows 8 Pro 64-bit
1:41:09 PM [main] XAMPP Version: 1.8.3
1:41:09 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
1:41:09 PM [main] You are not running with administrator rights! This will work for
1:41:09 PM [main] most application stuff but whenever you do something with services
1:41:09 PM [main] there will be a security dialogue or things will break! So think
1:41:09 PM [main] about running this application with administrator rights!
1:41:09 PM [main] XAMPP Installation Directory: "e:\xampp\"
1:41:09 PM [main] Checking for prerequisites
1:41:09 PM [main] All prerequisites found
1:41:09 PM [main] Initializing Modules
1:41:09 PM [main] Starting Check-Timer
1:41:09 PM [main] Control Panel Ready
1:41:19 PM [Apache] Attempting to start Apache app...
1:41:19 PM [Apache] Status change detected: running
1:43:47 PM [mysql] Attempting to start MySQL app...
1:43:47 PM [mysql] Status change detected: running
1:43:49 PM [mysql] Status change detected: stopped
1:43:49 PM [mysql] Error: MySQL shutdown unexpectedly.
1:43:49 PM [mysql] This may be due to a blocked port, missing dependencies,
1:43:49 PM [mysql] improper privileges, a crash, or a shutdown by another method.
1:43:49 PM [mysql] Press the Logs button to view error logs and check
1:43:49 PM [mysql] the Windows Event Viewer for more clues
1:43:49 PM [mysql] If you need more help, copy and post this
1:43:49 PM [mysql] entire log window on the forums

Mysql Error Log File: http://gmwebfiles.com/data/g/forumposts ... _error.txt

Cheers

GW
User avatar
gwmbox
 
Posts: 18
Joined: 15. January 2011 03:34
Operating System: Windows 7 64-bit

Re: How to do a full restore of xampp

Postby Nobbie » 29. October 2014 10:36

You should not install a new Xampp, if you want to restore(!) a Xampp. Instead you simply have to restore the full Xampp folder of your backuped Xampp (exactly to the same Drive and directory).

A new installation means an upgrade, what is by far more work, you have to adapt all config-files as well (the MySQL Error message results from a configuration, which does not fit to your data).
Nobbie
 
Posts: 8779
Joined: 09. March 2008 13:04

Re: How to do a full restore of xampp

Postby gwmbox » 30. October 2014 01:44

Thanks, I have uninstalled xampp and then restored the xampp from backup, but I still cannot get mysql to start up, any other suggestions please.
User avatar
gwmbox
 
Posts: 18
Joined: 15. January 2011 03:34
Operating System: Windows 7 64-bit

Re: How to do a full restore of xampp

Postby Nobbie » 30. October 2014 23:35

Sorry, i dont have any other suggestions, due to lack of any error messages.
Nobbie
 
Posts: 8779
Joined: 09. March 2008 13:04

Re: How to do a full restore of xampp

Postby gwmbox » 31. October 2014 00:18

Are there any other logs I could attach to help?

I really really need this working again

Today's mysql error log

2014-10-31 07:25:24 3720 [Note] Plugin 'FEDERATED' is disabled.
2014-10-31 07:25:24 164 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-10-31 07:25:24 3720 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-10-31 07:25:24 3720 [Note] InnoDB: The InnoDB memory heap is disabled
2014-10-31 07:25:24 3720 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-10-31 07:25:24 3720 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-10-31 07:25:24 3720 [Note] InnoDB: Not using CPU crc32 instructions
2014-10-31 07:25:24 3720 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-10-31 07:25:24 3720 [Note] InnoDB: Completed initialization of buffer pool
2014-10-31 07:25:24 3720 [Note] InnoDB: Highest supported file format is Barracuda.
2014-10-31 07:25:24 3720 [Note] InnoDB: The log sequence numbers 1626134 and 1626134 in ibdata files do not match the log sequence number 73082441 in the ib_logfiles!
2014-10-31 07:25:24 3720 [Note] InnoDB: Database was not shutdown normally!
2014-10-31 07:25:24 3720 [Note] InnoDB: Starting crash recovery.
2014-10-31 07:25:24 3720 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-10-31 07:25:25 3720 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace a@002dmydbname/wp_comments uses space ID: 8 at filepath: .\a@002dmydbname\wp_comments.ibd. Cannot open tablespace phpmyadmin/pma_navigationhiding which uses space ID: 8 at filepath: .\phpmyadmin\pma_navigationhiding.ibd
InnoDB: Error: could not open single-table tablespace file .\phpmyadmin\pma_navigationhiding.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Someone, anyone, please help

Surely I am not the only one that has had to do a full restore?
User avatar
gwmbox
 
Posts: 18
Joined: 15. January 2011 03:34
Operating System: Windows 7 64-bit

Re: How to do a full restore of xampp

Postby Nobbie » 31. October 2014 10:54

Did you try all the suggestions from the error message? There are some very good hints at the end, it will qoute them for you:

InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
Nobbie
 
Posts: 8779
Joined: 09. March 2008 13:04

Re: How to do a full restore of xampp

Postby gwmbox » 01. November 2014 03:18

Ok thanks, I moved out the tables that the error message tell me are causing the issues, mysql is now running - hooray

So I now have 4 tables (idb) files that are not working, is there a way I can extract the contents of the idb files so I can import or add them to the correct table?

Thanks
User avatar
gwmbox
 
Posts: 18
Joined: 15. January 2011 03:34
Operating System: Windows 7 64-bit

Re: How to do a full restore of xampp

Postby Nobbie » 01. November 2014 12:18

I dont know, i never had that issue before.
Nobbie
 
Posts: 8779
Joined: 09. March 2008 13:04


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 49 guests