You will create a new instance, say 'name' like this:
$ koha-create --create-db name
You will then load your backup on the empty db that was created:
$ koha-mysql name < backup.sql
About step 3, you just need to try. It should work, and we can help with
the data errors.
Looking forward to
Excerpts from Alvaro Cornejo's message of 2022-02-05 19:40:08 -0500:
> I'll however suggest you do the backup load/upgrade before configuring the
> server since some of the data uses DB indexes to be identified.
Let me see if I understand this. Is this the order of steps you're
recommending?
Hi Mark
As Alvaro wrote there is no way to find out the actual password of any
user when just knowing the hash (which since Koha 3.14 is (encrypted by
Crypt::Eksblowfish::Bcrypt). But if for whatever reason you need to
export and reimport the current passwords you can just unload the hashed
There is no way to export unencrypted passwords since the db only has a
hash of it. Not the password itself.
You can just do a full backup of your koha db and move it to the new
server. Then run the DB upgrade process.
I'll however suggest you do the backup load/upgrade before configuring the
You should do all you mention, but instead of creating things, you should
just paste the old db and trigger the upgrade process.
El sáb., 5 feb. 2022 10:31, Mark Alexander escribió:
>
> I'm in the process of upgrading a library's Debian 7/Koha 3.16 setup.
> This installation is so old that an
I'm in the process of upgrading a library's Debian 7/Koha 3.16 setup.
This installation is so old that an in-place upgrade can't be done.
My plan is to first create a test VM with Debian 10 and the latest
stable koha-common. Then after manually setting up various admin
things (library, item
Hello All,
I'm trying to Define new branches from Koha basic parameters in staff
client (http://localhost/cgi-bin/koha/admin/branches.pl), but there are no
branches displayed, I guess it's fetched through the API, and the http Get
request for
7 matches
Mail list logo
