[DiscordArchive] I've been using a 3.3.5 TrinityCore repack for a good bit but I'm going to swap to stock TrinityCore
[DiscordArchive] I've been using a 3.3.5 TrinityCore repack for a good bit but I'm going to swap to stock TrinityCore
Original source
I've been using a 3.3.5 TrinityCore repack for a good bit but I'm going to swap to stock TrinityCore and merge in the specific modules I want before compliling. However, a few friends and I already have progress on the personal server. If I properly recompile and only merge in the specific things I want, can I safely reuse the DB from the server I've been using? Or will that cause issues?
rektbyfaith
04-16-2023, 12:56 AM #1Archived author: Lexaraj • Posted: 2023-04-16T00:56:47.923000+00:00
Original source
I've been using a 3.3.5 TrinityCore repack for a good bit but I'm going to swap to stock TrinityCore and merge in the specific modules I want before compliling. However, a few friends and I already have progress on the personal server. If I properly recompile and only merge in the specific things I want, can I safely reuse the DB from the server I've been using? Or will that cause issues?
Original source
Sorry if that's an obvious yes or no. I'm learning as I go
rektbyfaith
04-16-2023, 12:57 AM #2Archived author: Lexaraj • Posted: 2023-04-16T00:57:24.618000+00:00
Original source
Sorry if that's an obvious yes or no. I'm learning as I go
Original source
depends on the state of the "old" db
rektbyfaith
04-16-2023, 12:57 AM #3Archived author: ModoX • Posted: 2023-04-16T00:57:31.838000+00:00
Original source
depends on the state of the "old" db
Original source
if its outdated it might be incompatible
rektbyfaith
04-16-2023, 12:57 AM #4Archived author: ModoX • Posted: 2023-04-16T00:57:35.667000+00:00
Original source
if its outdated it might be incompatible
Original source
if it has custom changes it might be incompatible aswell
rektbyfaith
04-16-2023, 12:57 AM #5Archived author: ModoX • Posted: 2023-04-16T00:57:42.906000+00:00
Original source
if it has custom changes it might be incompatible aswell
Original source
What you always can do is using the ". pdump" command to make backups of characters. You can manually import them later again. Quite time intense but possible if not for too many characters
rektbyfaith
04-16-2023, 07:46 AM #6Archived author: Jinnai • Posted: 2023-04-16T07:46:24.253000+00:00
Original source
What you always can do is using the ". pdump" command to make backups of characters. You can manually import them later again. Quite time intense but possible if not for too many characters
Original source
I did this a few months ago after starting off on a repack. If you run within a VM it makes a quite simple to make a new build and practice and revert if it goes wrong. If you don't you could still practice the migration in a VM. My method once having a fresh build working was to export the auth and character DB's (careful check box selection as by default the data select on the export window) as a file for each one (keeping world db as is in the new build) using Heidi SQL. Then on the new build, using Heidi SQL again, 'dropping' those same two DB's on the new build and importing the one's from my repack. And yes backup backup and backup, hard to have enough backups
rektbyfaith
04-28-2023, 07:45 AM #7Archived author: Deleted User • Posted: 2023-04-28T07:45:01.111000+00:00
Original source
I did this a few months ago after starting off on a repack. If you run within a VM it makes a quite simple to make a new build and practice and revert if it goes wrong. If you don't you could still practice the migration in a VM. My method once having a fresh build working was to export the auth and character DB's (careful check box selection as by default the data select on the export window) as a file for each one (keeping world db as is in the new build) using Heidi SQL. Then on the new build, using Heidi SQL again, 'dropping' those same two DB's on the new build and importing the one's from my repack. And yes backup backup and backup, hard to have enough backups
Original source
A lil bit confusing, but you got the point...
Have a working System? - Back it up... Keep that Backup!
Work/Change/Tryout anything...
Not working?
Revert to the initial working Backup...
Profit... Also Spare on Nerves and Blood-Pressure Issues...
rektbyfaith
04-28-2023, 11:22 PM #8Archived author: Ｈｏｂｏ • Posted: 2023-04-28T23:22:03.153000+00:00
Original source
A lil bit confusing, but you got the point...
Have a working System? - Back it up... Keep that Backup!
Work/Change/Tryout anything...
Not working?
Revert to the initial working Backup...
Profit... Also Spare on Nerves and Blood-Pressure Issues...
Original source
Someone got a good, non-fuss Backup solution to go with??? <:call:770403425199849483>
rektbyfaith
04-28-2023, 11:24 PM #9Archived author: Ｈｏｂｏ • Posted: 2023-04-28T23:24:53.460000+00:00
Original source
Someone got a good, non-fuss Backup solution to go with??? <:call:770403425199849483>
Original source
I'll put a big * here I by no means want you to risk losing your toons so better advice might come through on whole machine backups and restores. Assuming you current repack is not a VM my approach would be put the fresh build into a VM. 2 core and 4GB of ram is enough to do a build. keep if mind if you give 8 cores for example to the VM you'll need more ram for the compile process to avoid a system hang. Virtual Box (my choice) is not a datacentre grade product but its easy to use, simple to make backups for whole machines and port forwarding can be done in the gui unless you 'bridge' the virtual machine to be on the same IP address range as the host computer. With a new build complete in virtual box the only part you need from the existing server is the export of the auth and character DB's *I'm going to label this as low risk using a GUI app like Heidi SQL. Take those two sql files through a cloud sync app or enable drag and drop to your VM, then you could do what I outlined above to replace the DB's in the new build with your own accounts and characters. Key area to be careful with, again IMO, is to make sure you are just doing an export of the DB's of current server and nothing else. But as I started with, if there advice on whole machine backups including SQL go with that first for more peace of mind.
rektbyfaith
04-29-2023, 12:43 AM #10Archived author: Deleted User • Posted: 2023-04-29T00:43:48.176000+00:00
Original source
I'll put a big * here I by no means want you to risk losing your toons so better advice might come through on whole machine backups and restores. Assuming you current repack is not a VM my approach would be put the fresh build into a VM. 2 core and 4GB of ram is enough to do a build. keep if mind if you give 8 cores for example to the VM you'll need more ram for the compile process to avoid a system hang. Virtual Box (my choice) is not a datacentre grade product but its easy to use, simple to make backups for whole machines and port forwarding can be done in the gui unless you 'bridge' the virtual machine to be on the same IP address range as the host computer. With a new build complete in virtual box the only part you need from the existing server is the export of the auth and character DB's *I'm going to label this as low risk using a GUI app like Heidi SQL. Take those two sql files through a cloud sync app or enable drag and drop to your VM, then you could do what I outlined above to replace the DB's in the new build with your own accounts and characters. Key area to be careful with, again IMO, is to make sure you are just doing an export of the DB's of current server and nothing else. But as I started with, if there advice on whole machine backups including SQL go with that first for more peace of mind.