注意!
翻译的是配置文件“AdvancedBackups.properties”。
不是“AdvancedBackups-client.properties”,不要搞混了!
配置文件的原文注释+翻译双语对照
#Enable or disable automatic backups.
#启用或禁用自动备份。
config.advancedbackups.enabled=true
#Whether to save before making a backup.
#是否在备份前保存。
config.advancedbackups.save=true
#Buffer size, in bytes, to use when reading / writing files. Higher will improve speeds, but increase memory usage.
#读取/写入文件时使用的缓冲区大小,以字节为单位。设置较大的缓冲区可以提高速度,但也会增加内存使用。
#Too high can cause an OOM. I'd advise against editing this unless you experience issues.
#过大可能会导致内存不足。建议除非遇到什么问题否则不要修改。
#Range : 1-2147483647 #Default : 1048576
#范围:1-2147483647 #默认:1048576
config.advancedbackups.buffer=1048576
#Whether to flush when making the aforementioned save. Can cause a lag spike, and is usually not required.
#在进行上述保存时是否刷新。可能会导致延迟高峰,通常来说并不需要。
#Unused prior to minecraft 1.16.
#在Minecraft 1.16之前未使用。
#Options : true, false #Default : false
#选项:true, false #默认:false
config.advancedbackups.flush=false
#Whether to require player activity between backups.
#是否要求玩家在两次备份之间有所活动。
#Options : true, false #Default : true
#选项:true, false #默认:true
config.advancedbackups.activity=true
#The type of backups to use.
#使用的备份类型。
#Options : zip, differential, incremental #Default : differential
#选项:zip, differential, incremental #默认:differential(三者有什么区别又是什么意思可见最低说明。)
config.advancedbackups.type=differential
#A list of files, relative paths within the world directory, to skip backing up.
#列出在世界目录中需要跳过备份的文件。用的是相对路径。
#Comma separated, * is a wildcard, and backslashes are replaced with forward slashes.
#以逗号分隔,* 是通配符,反斜杠将替换为正斜杠。
#Default : session.lock,*.dat_old
#默认:session.lock,*.dat_old
config.advancedbackups.blacklist=session.lock,*_old
#The absolute or relative path to the backup location.
#备份位置的绝对或相对路径。
#Options : any file path. Default : ./backups
#选项:任何文件路径。默认:./backups
config.advancedbackups.path=./backups
#Minimum time between backups, in hours. This can prevent a shutdown backup from triggering immediately after a scheduled backup or similar situations.
#备份之间的最短时间(小时)。这可以防止在计划备份后立即触发关闭备份或类似情况。
#Set to 0 to disable.
#设置为0以禁用。
#5 minutes = ~ 0.083 hours.
#5分钟 = ~ 0.083小时。
#Range: 0 - 500 #Default: 0.5
#范围: 0 - 500 #默认: 0.5
config.advancedbackups.frequency.min=2
#Triggers a backup if none has already happened within this time. Can be combined with an uptime-based schedule.
#如果在此时间内没有发生任何备份,则触发备份。可以与基于正常运行时间的计划结合使用。
#Range: 0.5 - 500 #Default: 24
#范围: 0.5 - 500 #默认: 24
config.advancedbackups.frequency.max=4.0
#Whether the schedule below uses uptime (true) or real-world time (false).
#以下时间表是否使用游戏启动后的运行时间(true)或现实世界的时间(false)。
#Default: true
#默认: true
config.advancedbackups.frequency.uptime=true
#When using server uptime:
#使用服务器正常运行时间时:
#A looping comma-separated backup schedule, based off of server uptime, hours:minutes. Examples:
#基于服务器开机后的运行时间来算的时间表进行循环备份,每个备份时间点用逗号隔开,格式为 小时:分钟 。例子:
#4:00 - Makes a backup every four hours.
#4:00 - 每四小时备份一次。
#4:00,7:00 - Makes a backup after four hours, then three, then four, and so on.
#4:00,7:00 - 四小时后进行一次备份,然后三小时,然后四小时,以此类推。
#1:00 - Makes a backup every hour.
#1:00 - 每小时进行一次备份。
#4:00,8:00,12:00,16:00,17:00,18:00,19:00,20:00,21:00,24:00 - Makes a backup following a strict schedule.
#4:00,8:00,12:00,16:00,17:00,18:00,19:00,20:00,21:00,24:00 - 按照严格的时间表分别进行备份。
#When using real-world time:
#使用现实世界时间时:
#A strict schedule, using hours:minutes to follow real-world time. Examples:
#一个严格的时间表,用 小时:分钟 来跟紧现实世界时间。例子:
#4:00 - Makes a backup at 4am each day.
#4:00 - 每天凌晨4点进行备份。
#4:00,8:00,12:00,16:00,17:00,18:00,19:00,20:00,21:00,24:00 - Makes a backup at specific times of day.
#4:00,8:00,12:00,16:00,17:00,18:00,19:00,20:00,21:00,24:00 - 在特定时间分别进行备份。
#Default: 1:00
#默认: 1:00
config.advancedbackups.frequency.schedule=1:00
#Whether to force a backup on server shutdown. Respects min frequency.
#在服务器关闭时是否强制备份。遵循最小频率。
#Options: true, false #Default: false
#选项: true, false #默认: false
config.advancedbackups.frequency.shutdown=false
#Whether to force a backup on server startup. Respects min frequency.
#在服务器启动时是否强制备份。遵循最小频率。
#Options: true, false #Default: false
#选项: true, false #默认: false
config.advancedbackups.frequency.startup=true
#Delay to use after startup, in seconds. Is always at least 5 seconds.
#启动后使用的延迟时间,以秒为单位。一般都是至少5秒。
#Range: 5-1000 #Default: 30
#范围: 5-1000 #默认: 30
config.advancedbackups.frequency.delay=30
#--------------------------------------------------------------------------------------------------------------------
##The following options control logging of backup progress, including which clients to contact.
##以下选项控制备份进度的记录,包括通知哪些客户端。
##Backup start and end are always logged to console. The rest is configurable.
##备份开始和结束总会在控制台上记录。其他部分都可以根据需要进行配置调整。
#--------------------------------------------------------------------------------------------------------------------
#Which clients to send progress updates to. Behaviour before this was added was `ops`
#向哪些客户端发送进度更新。在添加此选项之前的行为是`ops`
#Options: ops, all, none #Default: ops
#选项: ops, all, none #默认: ops
config.advancedbackups.logging.clients=ops
#How often to send progress info to clients, measured in milliseconds. Old behaviour was `0`, not recommended for servers due to network load.
#多久向客户端发送一次进度信息,以毫秒为单位。传统做法是设置为`0`,但由于会导致网络负载,不推荐用于服务器。
#Range: 0 - ~infinite #Default: 500
#范围: 0 - ~无限 #默认: 500
config.advancedbackups.logging.clientfrequency=500
#Whether to log backup progress to console. Start / finish are always logged. Old behaviour was `false`.
#是否将备份进度记录到控制台。开始/结束都会记录。传统行为是`false`。
#Options: true, false #Default: true
#选项: true, false #默认: true
config.advancedbackups.logging.console=false
#How often to send log progress info in the console, measured in milliseconds.
#多久在控制台中发送一次日志进度信息,以毫秒为单位。
#Range: 0 - ~infinite #Default: 5000
#范围: 0 - ~无限 #默认: 5000
config.advancedbackups.logging.consolefrequency=5000
#--------------------------------------------------------------------------------------------------------------------
##The following options control deletion of old backups, meeting a criteria. A backup only needs to meet ONE of the below criteria to be purged.
##以下选项控制旧备份的删除,满足一个以下标准即被删除。
#--------------------------------------------------------------------------------------------------------------------
#The maximum size to keep, in GB. Keep relatively high for zips, tighter space requirements should instead use differential or incremental backups.
#保留的最大大小,以GB为单位。对于zip文件,保留相对较高的值,如果空间需求很紧张,应使用差异备份或增量备份。
#Set to 0 to disable.
#设置为0以禁用。
#Range: 0 - 9999 #Default: 50
#范围: 0 - 9999 #默认: 50
config.advancedbackups.purge.size=10.0
#The maximum days to keep backups for. Higher amounts will keep a longer "history" but take up more space in return.
#保留备份的最大天数。较高的值会保留更长的“历史”,但会占用更多的空间。
#Set to 0 to disable.
#设置为0以禁用。
#Range: 0 - 9999 #Default: 0
#范围: 0 - 9999 #默认: 0
config.advancedbackups.purge.days=5
#The maximum amount of backups to keep. Older backups will be purged if this is exceeded.
#保留的最大备份数量。如果超过此数量,将删除旧备份。
#Set to 0 to disable.
#设置为0以禁用。
#Range: 0 - 9999 #Default: 0
#范围: 0 - 9999 #默认: 0
config.advancedbackups.purge.count=0
#Whether to delete incremental backup chains if max size is exceeded. If not, incremental backups do not respect the above options and never delete.
#是否在增量备份文件超过最大大小限制时删除。否则增量备份就不会按照设定规则删除,也就是说会永远保留。
#This is because you can't delete part of an incremental backup chain without breaking the links. Differentials do not have this downside.
#这是因为你删除了增量备份链中的任何一部分,整个备份链的完整性都会被破坏。差异备份没有这种问题。
#Options: true, false #Default: true
#选项: true, false #默认: true
config.advancedbackups.purge.incrementals=true
#The minimum number of incremental chains to keep before purging any that meet the criteria. Only relevant if the above option is set to true.
#在删除满足条件的增量备份链之前,想要保留的最小增量链数量。仅在上述选项设置为true时才起效。
#Range: 1 - 9999 #Default: 1
#范围: 1 - 9999 #默认: 1
config.advancedbackups.purge.incrementalchains=1
#--------------------------------------------------------------------------------------------------------------------
##The following options only affect zip files, whether that's for zip backups, export commands or some other option.
##以下选项仅影响zip文件,无论是用于zip备份、导出命令还是其他选项。
#--------------------------------------------------------------------------------------------------------------------
#The compression level to use for zip files. Higher numbers space usage, but decrease performance.
#用于zip文件的压缩级别。数字越高,空间使用越多,但性能也会相应下降。
#Range: 1-9 #Default: 4
#范围: 1-9 #默认: 4
config.advancedbackups.zips.compression=4
#--------------------------------------------------------------------------------------------------------------------
##The following options only affect differential and incremental backups.
##以下选项仅影响差异备份和增量备份。
#--------------------------------------------------------------------------------------------------------------------
#The maximum 'chain' length to keep.
#保留的最大“链”长度。
#Range: 5-500 #Default: 50
#范围: 5-500 #默认: 50
config.advancedbackups.chains.length=50
#Whether to compress 'chains'. This compresses the base backup and all sequential backups. Reduces space usage, but decreases performance.
#是否压缩“链”。这会压缩基础备份和所有顺序备份。减少空间使用,但性能也会下降。
#Options: true, false #Default: true
#选项: true, false #默认: true
config.advancedbackups.chains.compress=true
#Whether to enable "smart" reset for chains - if every file is being backed up, mark the backup as complete and reset chain length regardless of intended backup type.
#是否启用链的“智能”重置——如果每个文件都在备份,则将备份标记为完成,并重置链长度,不管预期的备份类型是什么。
#Options: true, false #Default: true
#选项: true, false #默认: true
config.advancedbackups.chains.smart=true
#What % of a full backup is allowed to be contained in a partial before forcing it into a full backup. Useful for reducing partial backup size.
#允许一个非全备份包含多少百分比的完整备份内容,超过这个比例就会强制进行一次完整的备份。这样做有助于控制部分备份的大小。
#Range: 1-100 #Default: 50
#范围: 1-100 #默认: 50
config.advancedbackups.chains.maxpercent=50.0
“zip”、“differential”、“incremental ”都是啥意思?
Zip备份(Zip Backup):
解释:这是最简单的备份类型。它将所有需要备份的文件和文件夹压缩成一个单独的zip文件。
优点:操作简单,所有数据都集中在一个文件中,便于管理和恢复。
缺点:每次备份都需要将整个数据集压缩一次,可能会占用较多时间和存储空间。
差异备份(Differential Backup):
解释:差异备份只备份自上次完全备份以来发生变化的所有数据。
优点:与完全备份相比,备份速度更快,所需存储空间较少。
缺点:恢复数据时需要最新的完全备份和最近一次的差异备份。
增量备份(Incremental Backup):
解释:增量备份只备份自上次备份(无论是完全备份还是增量备份)以来发生变化的数据。
优点:备份速度最快,所需存储空间最少。
缺点:恢复数据时需要最新的完全备份和所有后续的增量备份,管理和恢复过程较为复杂。
(chatgpt说的我润了个色对不起我懒了)