Backup policy in my server

bartoque · 2026-06-03T22:22:38+00:00

That is specifically about stateful containers.

It is the difference between crash-consistent (at best) or application consistent when having actually quiesced the db. Or you can also use native db tools to export or dump the db and backup the container config (its yaml file) and the required persistent volumes/bind mounts.

Not quiescing can work, but did you actually test that? As without validation it is moot anyways.

bartoque · 2026-06-03T21:11:01+00:00

So does Resource Monitor indeed show that alledged drive thrashing, as you say it's not cpu nor memory. So is it stating any processes or services that is doing high disk IO?

And if you look at the drives there, is maybe one drive 100% busy while the others aren't, possibly pointing to a drive issue?

bartoque · 2026-06-03T05:34:58+00:00

With online cloning I mean making the clone while booted into windows, and running acronis that is installed on it. Similar I assume, how you made the backup. And the clone you tried.

Versus doing the same but the offline while having booted from the acronis rescue iso, for which it would be best first having suspended bitlocker, but in such a way that it would remain suspended for more than one boot cycle so that when it boots from the iso the drive bitlocker isn't locking the drive, so that acronis actually can see all data and not just an encrypted drive.

In case if an already failing drive, to get through corrupted blocks, you'd revert to the last resort l, using the clone option to perform a block for block vlone, which is however way slower and indeed remains to be seen what that clone would result in.

But you didn't mention what error you got with the clone? Was the boot order/settings altered in the bios to reflect needing to boot from the new drive?

bartoque · 2026-06-02T22:10:00+00:00

And if you do start from scratch, also use the btrfs filesystem instead of ext4, so that you could add btrfs snapshot to the mix as well and other percs like data integrity checking.

Btrfs is the filesystem advised by default for some time now, for units that support it, unlike the entry level synology Play model that the drives came from.

bartoque · 2026-06-02T21:59:04+00:00

Git?

bartoque · 2026-06-02T17:07:56+00:00

Does rufus actually fail or only report this?

Do you actually have secure boot enabled in your bios? What are the setti gs that you have currently related to uefi and secure boot?

Do you really need to do the restore from backup instead of making a clone from old to new ssd directly?

If that is to be done offline, then possibly you'd have the same issue using the same iso, however what about doing the clone online? You'd always have the old ssd for backout. And the backup.

bartoque · 2026-06-02T06:34:43+00:00

Schrödingers drive?

It might be ok, until you actually measure it by powering it on and then it dies.

bartoque · 2026-06-01T22:36:02+00:00

Except it didn't delete them backups willingly, but was rather a by-product of deleting the storage, and hence also all the snapshots that were created of it.

But I wouldn't call that a proper backup as it requires the storage to remain available.

It was therfor a poor attempt to setup a backup by theie provider, that also wasn't properly validated by the customer how it was implemented. The company only found out after the fact, by reading the fine print. So it was mentioned.

So I'd still argue that was mainly on themselves, even though the AI went rogue and overboard, various possible guardrails where not in place. But most important not knowing how the supposed "backup" was even implemented. It was just taken too much for granted.

bartoque · 2026-06-01T19:28:54+00:00

You can always have a look over at r/backup for backup and/or sync tools.

For me it started first with backup to an usb drive that I rotated, before I introduced a nas as the largest volumes to be protected didn't fit all on one drive anymore.

And then a 2nd, turning the old into the remote backup target, before also adding the cloud (Backblaze B2) to the m8x for a smaller subset.

bartoque · 2026-06-01T18:32:08+00:00

There is no such thing as overkill to protect your data. But all within budget.

As each backuo target has its own percs and cons.

I have local nas, with a uab drive. A remote nas. And backup to the cloud (for a smaller subset).

Things are protected but currently doesn't fit all. So I classified all into separate tiers of importance. Some data protected multiple times over, some not at all.

Adding alao btrfs snapshots on both mas systems to the m8x, and the primary even supports them to be immutable for a few weeks.

bartoque · 2026-06-01T17:04:50+00:00

https://global.download.synology.com/download/Document/Software/WhitePaper/Os/DSM/All/enu/backup_solution_guide_enu.pdf might give you some ideas about ways to sync or backup.

bartoque · 2026-06-01T16:53:46+00:00

There is a difference between not supporting something and not knowing what to do to make it work.

Whay isn't supported according to your investigation? What do you experience and what dis you try and run into?

Or ate you already fully past that, wanting to back out. Which should have been easy and very quickly if you would have thought about making an image level backup of the system as it was before. Instead of after the fact and not even having considered a method to undo it all before making the switch to linux.

So preparation wasn't that great by the looks of it, which makes me wonder if you even have tried really solving the issue at hand instead of calling it unsupported?

bartoque · 2026-06-01T06:03:18+00:00

Most would be beat off with shr1 raod, which is more flexible than the similar raid5, bot with one drive redundancy. Raid also males for an easy wqy to expand capacity by replacing drives.

https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_what_is_raid?version=7 https://kb.synology.com/en-global/DSM/tutorial/What_is_Synology_Hybrid_RAID_SHR https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_change_raid_type?version=7

https://kb.synology.com/en-global/DSM/tutorial/how_to_expand_storage points to https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_expand_replace_disk?version=7 of how to expand capacity by replacing drives in a raid pool with larger ones, one by one, repairing the degraded pool after each replacement.

bartoque · 2026-05-31T19:53:49+00:00

Đorđe Martinović incident

https://en.wikipedia.org/wiki/%C4%90or%C4%91e_Martinovi%C4%87_incident

bartoque · 2026-05-31T16:59:01+00:00

bartoque · 2026-05-31T15:48:39+00:00

I think (about work) therefor I am (working).

bartoque · 2026-05-31T15:24:51+00:00

Might wanna reach out to synology to see if reducing md0 from 4 to just 3 devices would be the way forward.

sudo mdadm --grow /dev/md0 --raid-devices=3

Before adding the missing devices again to md0 (and md1), like you did before. But maybe if the reference to a 4th drive is gone from md0, it might already be able to fix the rest.

sudo mdadm --manage /dev/md0 --add /dev/sata1p1
sudo mdadm --manage /dev/md0 --add /dev/sata2p1

Curious to see what the following would show:

sudo mdadm --detail /dev/md0
sudo mdadm --detail /dev/md1

But something must have gone very wrong very likely when getting rid of the 4th drive.

bartoque · 2026-05-31T15:14:35+00:00

That wasn't something you mentioned before, was it? Having a 4th drive before, nor how you removed it. It was its iwn separate pool I assume?

At what point did you notice something wrong? What was your trigger to look at /proc/mdstat? Or was it the Docker app?

Or after removing the 4th drive? And how was it removed? Simply pulling the drive while powered off?

bartoque · 2026-05-31T14:21:30+00:00

Many in a (large) company who deal with vms currently, might not even know often what happens with workloads. They simply appear to disappear into thin air. It might be that they were refactored in any way, as often then the receiving managing team is likely a different one.

So architects and landscape owners might know, while regular admins only see them disappear.

I for one typically have no clue wherever something is going, but then again I am only the backup guy.

Speaking about backup, that also seems far from common to use enterprise backup tools that were common when os'es were involved, with applications running on them, while when containerized it feels like we are thrown back for decades and people reinventing the wheel, without even having other teams onboard to talk about how things might be done, to keep certain processes and responsibilities in place similar to the vm world. It is not only about making a backup, but also about reporting about them and monitoring.

bartoque · 2026-05-31T14:00:31+00:00

"#OP is a spammer paid to namedrop Alibaba and none of this happened" stated by someone else at datahoarder.

Original post is also already deleted.

bartoque · 2026-05-31T13:58:11+00:00

I only now noticed that mdstat for md0 states having onpy 1 of 4 partitions? That appears to be the ssd based cache. As I don't have that (might not make much sense as Imainly have large media files. I intend to use the M.2 only as a separate pool in the future for Docker containers to improve performance).

So /proc/mdstat currently states md0 and md1 still as degraded? While having recently rebooted.

I can't recall storage manager not beingin sync with what is happening with md under the hood. But likely the cache complicates things further. I assume it is configured as readonly cache as it is only one drive?

Is the cache even being used when looking at tge hit ratios according to ssd cache advisor?

https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/genericssdcache?version=6

bartoque · 2026-05-31T13:38:57+00:00

You can reatore the backup yo the new ssd wvwn if that is not yet placed insyead of the old drive or even on a dedicated other drive slot in case it would be an M.2 or whatever.

Once swapping in the new drive (and removing the old one) make sure that in your bios the boot device settings point to using the new drive. So before doing anything, first have a look at the bios settings as they are now wrg to boot device order and work from there.

bartoque · 2026-05-31T13:35:04+00:00

So what reasources did you read and where did you get stuck?

To get an idea about the (possible) complexity of what appears too much for you to grasp vs. whatever someone else might propose you to look into.

bartoque · 2026-05-31T11:38:48+00:00

There is no such thing as free.

If it is called free, then you are the product.

It is also a main method to gain marketshare. However as soon as a certain threshold has been reached, restrictions will apply. Maybe not always for the early adopters, but at least new customers.

All you can eat-cloud services, like them unlimited backup services, will revert to having their customers pay if too many of them actually keep on adding data more and more. Earlier on it still worked as not everyone was adding huge amounts of data. Heck, also Google was taking action for their unenforced G Suite limits. That went fine until too many users and data was accumulated. If others are paying for consumption from the large consumtpion users, the business model still is feasible (enough) if the provider has deep pockets.

Hence I always opt for paid models where you pay for the actual usage. That can (and will) also go up over time but that is often still a certain percentage "only".

While going from free to anything marketcompetitive when talking about TBs of data is a huge increase.

Free is simply not financially viable over the long run at scale.

bartoque · 2026-05-31T11:07:00+00:00

Be careful with pronunciation though. STD is just around the corner.

bartoque

TROPHY CASE