L2J Server

If you want to receive support we need this info to help you properly.
» Find Revision
L2J Revision 4488:
L2JDP Revision 7760:

Hi all

I want to make daily backup of my database, but i dont know if i need shoutdown my gameserver for do the backup correctly or i can backup while server is running.

I ask becouse i can have my gameserver one week running, but i think make backup each week is not safe.

If you only want to backup the database, then simple backup it using Navicat, pmpmyadmin or any program you are using to create and manage the databases. Doing that also does not require to shut down the server (although it is not a bad idea)

mysqldump

I'm doing backup every hour for all my projects and I'm removing 7 days old backups. Simply use your cron.

PS: You don't need to restart / shutdown your server or something else.
PS2: Never use Navicat or remote MySQL access, use phpmyadmin(you don't need remote access beacuse you are accessing server from localhost...)

pinkcore wrote:I'm doing backup every hour for all my projects and I'm removing 7 days old backups. Simply use your cron.

PS: You don't need to restart / shutdown your server or something else.
PS2: Never use Navicat or remote MySQL access, use phpmyadmin(you don't need remote access beacuse you are accessing server from localhost...)

Hi pinkcore

Thank you for response

Can you share your cron for bakcup each hour and delete files with 7 days or more?

is your crone for Linux? becouse my server is running on CentoS 5.5

Sorry but you need server shutdown (and hold it off-line) for good backup.

First of all:

because, while your server is running, doesn't record the newest data in database.
It uses ram for speed, no disk access which is very slow.

And second:

If you let players playing while you are in backup, could happen (sure will) players create new object ID which will be referred in some parts of the tables and not in others.

Unless you get a backup in few milliseconds, you're doing wrong, and you will be noticed when console starts with messages because you're using a corrupted database or maybe not, because you couldn't restore it.