starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #764] Backup function: exclude backups directory #615

New issue

Closed

opened 2026-02-27 02:02:39 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 02:02:39 +03:00

Owner

Originally created by @pix0wl on GitHub (Mar 18, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/764

Originally assigned to: @UltimateByte on GitHub.

Hi,

the backup function includes per default the backups dir.
So every new backup includes the old backups and is growing unnecessarily.

Originally created by @pix0wl on GitHub (Mar 18, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/764 Originally assigned to: @UltimateByte on GitHub. Hi, the backup function includes per default the backups dir. So every new backup includes the old backups and is growing unnecessarily.

kerem

2026-02-27 02:02:39 +03:00

closed this issue
added the
type: bug
label

kerem commented

2026-02-27 02:02:40 +03:00

Author

Owner

@UltimateByte commented on GitHub (Mar 18, 2016):

Hi,
For now, the backup hasn't been designed to be run multiple times, it's something that you should use once to transfer your server.
However, i wish to improve it, and i could code your suggestion before anything else.

Here is an idea of what i've got in mind afterwards :
https://github.com/dgibbs64/linuxgsm/issues/716

@UltimateByte commented on GitHub (Mar 18, 2016): Hi, For now, the backup hasn't been designed to be run multiple times, it's something that you should use once to transfer your server. However, i wish to improve it, and i could code your suggestion before anything else. Here is an idea of what i've got in mind afterwards : https://github.com/dgibbs64/linuxgsm/issues/716

kerem commented

2026-02-27 02:02:40 +03:00

Author

Owner

@UltimateByte commented on GitHub (Mar 18, 2016):

OK, after having a look at the code, the backup directory should already be excluded from the backup.
https://github.com/dgibbs64/linuxgsm/blob/master/functions/command_backup.sh#L56

So are you sure that you're experiencing that issue ?
With what game ? And what version of LGSM ? Can you try updating your functions, running ./gameserver update-functions , ant try again ?

Maybe your game and backup folders becomes bigger for another reason ?

@UltimateByte commented on GitHub (Mar 18, 2016): OK, after having a look at the code, the backup directory should already be excluded from the backup. https://github.com/dgibbs64/linuxgsm/blob/master/functions/command_backup.sh#L56 So are you sure that you're experiencing that issue ? With what game ? And what version of LGSM ? Can you try updating your functions, running ./gameserver update-functions , ant try again ? Maybe your game and backup folders becomes bigger for another reason ?

kerem commented

2026-02-27 02:02:40 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Mar 18, 2016):

yeah i designed the code with not backing up the backups in mind. Would be pretty dumb to backup the backups :P

@dgibbs64 commented on GitHub (Mar 18, 2016): yeah i designed the code with not backing up the backups in mind. Would be pretty dumb to backup the backups :P

kerem commented

2026-02-27 02:02:40 +03:00

Author

Owner

@UltimateByte commented on GitHub (Mar 18, 2016):

@pix0wl You sir were actually right, so thanks ! :)
It's fixed, and you gained an improved display with file size information.

To get the update :
./gameserver update-functions
or
./gameserver uf

@UltimateByte commented on GitHub (Mar 18, 2016): @pix0wl You sir were actually right, so thanks ! :) It's fixed, and you gained an improved display with file size information. To get the update : `./gameserver update-functions` or `./gameserver uf`

kerem commented

2026-02-27 02:02:40 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.