as one of my nextcloud installation is on a 32bit debian jessie, I thought it would be a good idea to install nextcloud on a 64bit jessie. Therefore I installed a clean 64bit jessie, downloaded nextcloud 10 (as my other server has had same version) installed mysql, created a database with the same db name like in my old nextcloud installation.
Furthermore I activated in the new installation the same apps. After that I backuped the nextcloud directy with rysnc -Aax
and I backuped mysql with the following command:
mysqldump --lock-tables -h localhost -u nextclouduser --password=Password nextcloud > /mnt/backup2/backupnc/nextcloud-sqlbkp-20170107.bak
After that I stopped apache at my new server, copied the datadirectory with rsync -Aax
and try to import sql-data with the command:
mysql -h localhost -u nextclouduser --password=Password nextcloud < /mnt/backup/backupnc/nextcloud-sqlbkp-20170107.bak
Then I tried to access my nextcloud install at the new server, I get the message, that 2 apps have to be updated (calender and task), after the update has finished I was able to log in with my useraccount. There I get the error that I have problems with code integrity and I cannot open my files or upload new files.
I have read in another topic, that the import should be in a new database, therefore I created a new database (called nextcloudnew), import mysql-data, edited my config.php but problem seems to be the same.
Here ist an extract of the result of analyse:
[core] => Array
[EXTRA_FILE] => Array
[nextcloud/themes/README] => Array
[current] => 902ad902d14772f4030f4e8aaec8707ada9904c7e59913057769a55b694986df3f6aad04ed66fb7175d2dbe89b0ce014b80c3737306b3cb61e87f947c7664ee2
[nextcloud/themes/example/defaults.php] => Array ( [expected] => [current] => cb787b0bab2df166bed820f1cff9541262d4801a9feb82dac992567256b6bfed2eb3ba8d8cbd97673088081049c2e7378c37c57f745ca8f80fe8c8163957559e )
There are a lot of files that have this error. I think this is the important part, but I don’t know exactely how I can solve this (and maybe how I could prevent such an error for a next import).
Thanks and best regards