reinstalling D7 / import export routine

Hi there!

We have to reinstall D7 on our new server next week. Is there any documentation about reinstalling D7? Or even a script, which can be bought, that pulls out the data from the database and the file system and installs it back into the new setup, just like the data migration module in Dolphin from 6.1 to 7.0 but this time for D7.x to D7.x?

We do have some bugs and errors, which are also reported in the unity forums with no solution yet, and we want to make a fresh installation of D7.0.2 and put in the old consistent data.

We also figured out some Database inconsistences, which I try to fix by now.

It would be really nice, if someone can give me an answer or can help, how to reinstall with importing the old data....

Best Regards

Tom

It's rather simple.

Go to Admin Panel->Tools->Database Backup. Switch to Database Back Tools tab. Choose Save to your PC and click "Backup database."

It's gonna ask you to download an sql file. If it times out and doesn't give you anything, use phpmyadmin or whatever tool you got, to manually export the database.

Here you got your entire database.

Now, login to your server through SSH.

Assuming your dolphin site is in /var/www/dolphin/, use the following command to make a archive of the whole site.

tar pcf /var/www/backup.tar --exclude="/var/www/dolphin/cache/" /var/www/dolphin

Download backup.tar to your computer, and then move to a safe directory.

Then, you can wipe and reinstall the script.

After that, use phpmyadmin to empty all of the tables in your dolphin database. Import the backup sql file.

Now you have finished restoring the database.

The next step is to restore the files.

Extract all the "file" directories in subdirectories within /flash/modules/ and /modules/boonex/. If you have custom modules, extract the entire directories. For example, if you have /modules/blahblah, extract the blahblah directory.

Upload these directories to your server in the same paths.

Test your site.

If everything works, it's done.

Flurmingo, thanks for your quick reply. It sounds logic, I will give it a try. I hope it is done, and I dont import the old problems again :)

I do have some questions, I dont know the system quite well yet, however:

There are some tables in the Database. e.g. sys_modules, where the modules information is stored and sys_modules_file_tracks, where the dependencies, the files and their hashes from the modules are written.

Is it a problem, to install D7.0.2, and link it with a 7.0.1 database? Are e.g. these two tables rewritten from the system, when I import the database after a fresh new D7.0.2 installation? Which part rules? The filesystem or the database?

And when do I implement the cron job? Before replacement or?

You can use the upgrade script to update the database.

Just take a look at sql.sql in the upgrade directory, you will see what's being changed.

The good thing is that there aren't a lot of changes.

Thats a suberb idea!

I just wonder, is it possible to upgrade and upgrade dolphin and then restore an old backup database out of Admin Panel->Tools->Database Backup. The import routine of the restore script of dolphin must be very interessting... hmm Does it also block old backup files, which can corrumpt the whole system? Or are these old backup files prepared by the system and then inserted?

I am really strained, if everything will work fine...

Flurmingo, you said, delete the Tables per phpmyadmin and then insert the DB backup. Why shouldn´t I try the Import routine from Doplhin 7.x itself? Just uploading the SQL Backup into the backup directory of the new Dolphin 7.0.2. I mean, its surely better isnt it? There are more routines...

Flurmingo, we have successfully reinstalled the whole server and installed D7.0.2. This Version is really stable enough to work with, I think. However, when we did the reimport from our "old D7.0.2. Database" we experienced some heavy problems. It looks like, that Dolphin remembers the database, which was in before. (Btw. it does not matter (Version 7.0.2) if you take the dolphin importer or delete the data and reimport by your own.) Our workaround was: We went into all settings and all modules and pressed save. It took us 1 hour. 1 hour too much, if you are in a hurry, so why did that shit happen?

We dont know why. Is it because of the cron jobs? What happens with the filesystem and the Database itself, when you change the backend?

Thats my first question. And my next is:

Is there any module out there, which calculates the whole module file-hashes for the tables in the D7 database? (At the moment there where 1598 Files hashes in the new setup, and 1583 in the old D7.0.2) so we lost 15 during import. What is with those 15 entries? I mean that are inconsistences...

1. navigate to phpmyadmin on your current setup, select the database that dolphin is currently running from, and use the export function from phpmyadmin, save in zip format if available.

2. if you have access to ssh, you can utilize as stated the tar feature, or you can also use zip, now this is where i would do something different, instead of downloading this to your local drive, i would wget the compressed state of the site over to the new server.

3. on the new server, navigate to phpmyadmin, create the database, grant permissions on that database, then using the import tool, you will then import the sql file and the old database will be on the new server setup.

4. after you have used the wget command, you can then untar or unzip whichever compression instance you have opted for, this will unpack the files to the location on the server that is configured in your httpd as your index root.

5. open the /inc/header.inc.php file and make any necessary adjustments to the root directory as well as the database connection strings

what this will do is provide an exact mirror of the site in its current state on the new server that was available on the new server. now as for installing a fresh version.

1. mkdir somedirectory for new install

2. from within the new directory --> wget http://get.boonex.com/Dolphin-v.7.0.2 ( just guessing at that link )

3. unpack the files

4. navigate to phpmyadmin create a new database, grant all permission

5. navigate on the browser to http://yoursite.com/somedirectory ( this will fire the install script )

6.run the install script, and this places a new instance of 7.0.2 onto your server

from there, i am not sure what you are asking, because you mention errors and bugs, you also mention consistencies. if you have not modified your file structure from the previous installation, then there is nothing wrong with the file structure being reused, and just change the database connection string to point to the new database, this would be after you have completed the installation process of the new instance.

there is no migration from 7.0.2 to a new instance of 7.0.2, typically you just back everything up, and move it. if you are utilizing cPanel, there is a feature that allows for cPanel to cPanel imports, otherwise, you will need to do this work manually.

Regards,

DosDawg

DosDawg, thanks for your installation instructions, the problem is, that our productive site was messed up with by our own and with some 3rd party modules, so we really had to do a fresh install.. everything worked fine, even with the 3rd party modules, we trust now, but when we exchanged the databases, there were some of the problems again.

Is there any way, to repair a production backend, if it is messed up? I am writing on some srcipts at the moment. They should check consistencies in the whole backend system and fix it, if necessary and on import/export scripts, if your production site is messed up.

Just look at recovery. Switch back to the last good known system, and then reimport the last good known and uptodate database. Must they are from the same time? No, Dolphin even allows imports from any time... DosDawg, we need a import export script only for the profiles and dependencies and the file dependencies with a click of a button... and I think a good thing would be, if there were some infos in the header of the sql script, if you export from dolphin, just like, Dolphin version, installed modules and some checks, which are read by the database import routine of dolphin...

Hmm I really dont know what to do with our inconsistencies... the sys_modules and sys_modules_file_tracks are different now...

yeah, you are talking about a ton of work, in just trying to track down the module dependencies. this is something that should be written specifically to LEONIDS, or ARAMIS or one of those guys, but i even doubt they can tell you every module dependency that is on this application. i have had issues with these dependencies from the very beginning, since each module in my opinion should stand indedpendent of any other module, and the script should instantiate the cohesive interpolation between modules.

Profiles

Music

Video

Blogs

Ads

Store

Forum Posts

Events

Groups

Wall

so as you can see, when asking for just the profiles and the dependencies of just the profile, you are talking about backing up the entirety of the database.

wish there was a more non-complex solution to this, but i am afraid there is not.

Regards,

DosDawg

Yes DosDawg and thx for your words on this topic, I also hope Aramis will be involved in doing such things, I dont know Leonids yet. I am writing only some scripts, some small workarounds, but only in sql for our database and some views, maybe there are some parts, which can be usefull for others... lets see...

but once again, I hope the messed up hashes and inconsistences in our database concurning the sys_module tables can be fixed. Maybe someone else has a guess on this topic...