Have you read through available documentation, open Github issues and Github Ideas Discussions?

Yes

System information

Your moosefs version and its origin (moosefs.com, packaged by distro, built from source, ...).

MFS version: 4.57.6-1 ; build: 1944

Operating system (distribution) and kernel version.

Ubuntu 24.04

Hardware / network configuration, and underlying filesystems on master, chunkservers, and clients.

Mixed hosts, all 10g x86/amd64 based

How much data is tracked by moosefs master (order of magnitude)?

• All fs objects: ~15m
• Total space: 2.3pb
• Free space: 2.1pb
• RAM used: master system showing 10GB used
• last metadata save duration:1h, keep last 48
  I also have 2 metaloggers configured

Describe your request:

For the sake of redundancy/safety, I have MooseFS save the last 48 (48h) worth of master server data. I sync this off to 2 servers and cloud storage. The metadata with the hourlys is about 140GB. Presently the way the back ups are saved is it appears, each hour, is to take the .1 file, rename to .2, rinse repeat through the entire set.

What new feature would you like to see implemented in MooseFS?

It would be nice if the hourlys were named by date/time and didn't change/rotate. Just have the last one (49th hour) delete. This would make the syncs/backups much more efficient.

Why this feature? Is it a necessity or a nice to have? Is this feature related to any other features or problems in the open issues?

This effectively makes all 48 files appear to be changed vs just one, meaning each backup copy I create needs to recopy all 140GB vs just the last hours when using something like rsync or rclone.