#disasterrecovery — Public Fediverse posts

A restore onto the host that took the backup tests the archive, not the recovery. That host still holds the accounts and keys the dump left out.

My Nextcloud template passed same-host restores for three weeks. On a clean VM: 500 on every request.

47 Compose templates now drill weekly on a machine that never ran the stack. Week one: 47 of 47, 19 s to 396 s.

A same-host number is true on the day nobody needs it.

https://heyvaldemar.com/restore-drill-clean-machine-recovery-time/

#DisasterRecovery #Docker #DevOps

Kinda crazy work day. Helped facilitate a statewide #DisasterRecovery #exercise. My team crushed it, all while our boss is out in bereavement leave. I'm so proud. 12hr day to coordinate how we fix things when they break. But. That's not the story I want to share... 1/

Backups don't guarantee a successful recovery.

A working WordPress disaster recovery plan also needs tested restores, documented procedures, realistic RPO/RTO targets, and a clear process for handling security incidents.

For WooCommerce, it must also account for orders, payments, and inventory changes that occur around an outage.

Our practical guide: https://olvy.io/p7O2k

#WordPress #WooCommerce #DisasterRecovery #DataProtection #WebHosting

I actually managed to recover it this morning! I had today off so that's the perfect time to sit down and focus on the problem.

With the relevant database files, I spun up another mysql container in Kubernetes, copied the database files in, and started it up. Mysql loaded the tables and start up successfully, which allowed me to run a mysqldump command. That's all I needed to get it back to the original instance.

I will now be setting up a cronjob to run mysqldump to a proper backup directory.

#homelab #oops #pebkac #bookstack #kubernetes #disasterrecovery #selfinflicted #rtfm

How to Generate a Full #VPS #Backup Using #rclone (Simple 3-Minute Guide)

This article provides a detailed step-by-step description of how to generate a full VPS backup using rclone.
What is rclone?
Rclone is a powerful ...
Continued 👉 #onedrive #disasterrecovery #googledrive #opensource

How to Generate a Full VPS Bac...

The AWS UAE outage exposed a critical lesson:

Multi-AZ ≠ Multi-Region DR.

Regional disasters require cross-region backups, tested failover, clear RTO/RPO, and reproducible infrastructure.

Your Region shouldn't be your only Plan B.

https://shorturl.at/dMWb4

#AWS #DevOps #CloudArchitecture #DisasterRecovery

How to Generate a Full #VPS #Backup Using #rclone (Simple 3-Minute Guide)

This article provides a detailed step-by-step description of how to generate a full VPS backup using rclone.
What is rclone?
Rclone is a powerful open-source command-line tool for managing files on cloud storage services and local storage. You can think of it as kind of like "rsync" (the popular file-copying tool), but ...
Continued 👉 https://blog.radwebhosting.com/generate-a-full-vps-backup-using-rclone/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #opensource #disasterrecovery #googledrive #onedrive

WooCommerce checkout failure can quickly turn into a serious revenue and data-integrity problem.

Our recovery case study covers backup verification, order reconciliation, database and PHP issues, caching, scheduled tasks, monitoring, and rebuilding the production environment: https://olvy.io/kH78k

#WooCommerce #eCommerce #DisasterRecovery #WebHosting #WebsiteReliability #Backup

https://www.europesays.com/unitedstates/7583/ GAO Report Finds Too Lengthy a Review Process for Hazard Mitigation Projects Across US #DisasterPreparedness #DisasterRecovery #DisasterRelief #DisasterResponse #disasters #FEMA #GAO #PoliticalInvestigations

https://www.europesays.com/unitedstates/5997/ GAO Report Finds Lengthy Review Process for Hazard Mitigation Efforts Across US #DisasterPreparedness #DisasterRecovery #DisasterRelief #DisasterResponse #disasters #FEMA #GAO #PoliticalInvestigations

Australia's Disaster Resilience Plan Threatens Fiscal Burden Shift

The Australian government's Disaster Resilience Plan could significantly shift the financial burden of disaster recovery onto Queensland, the Northern Territory, and Western Australia, adding to the country's already staggering $1.051 trillion federal gross debt forecast for 2026-27. This proposed 50:50 cost-sharing…

https://osintsights.com/australias-disaster-resilience-plan-threatens-fiscal-burden-shift?utm_source=mastodon&utm_medium=social

#DisasterResilience #FiscalPolicy #Australia #GovernmentFunding #DisasterRecovery

A nightly pg_dump cron job is not a DR plan. If your NVMe dies at 4:30 PM, you lose 14 hours of transactions. Production Postgres needs WAL https://www.valtersit.com/guides/databases/stop_using_pg_dump_for_production_backups-the_case_for_wal_archiving/

#postgresql #backups #disasterrecovery

Proteggere i dati significa garantire la continuita' del business. Scopri le soluzioni R-Lay per affrontare le esigenze IT piu' importanti: dal backup e disaster recovery con Arcserve ShadowProtect SPX, al supporto e accesso remoto per professionisti IT, fino alla protezione dei dati in cloud con Impossible...
#secsolutionfoum #R-Lay #IT #backup #disasterrecovery http://dlvr.it/TVhfkw

How to Generate a Full #VPS #Backup Using #rclone (Simple 3-Minute Guide)

This article provides a detailed step-by-step description of how to generate a full VPS backup using rclone.
What is rclone?
Rclone is a powerful open-source command-line tool for managing files on cloud storage services and local storage. You can think of it as kind of like "rsync" (the popular file-copying tool), but ...
Continued 👉 https://blog.radwebhosting.com/generate-a-full-vps-backup-using-rclone/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #onedrive #opensource #googledrive #disasterrecovery

How to Generate a Full #VPS #Backup Using #rclone (Simple 3-Minute Guide)

This article provides a detailed step-by-step description of how to generate a full VPS backup using rclone.
What is rclone?
Rclone is a powerful ...
Continued 👉 #googledrive #disasterrecovery #onedrive #opensource

How to Generate a Full VPS Bac...

Nach einem Ransomware-Angriff reicht es nicht, Systeme zurückzuspielen. Sie müssen ihnen auch vertrauen können. 🔐
Beim Wissensfrühstück in Berlin geht es um Recovery mit Infrastructure as Code, die neue ISO/IEC 27031:2025, die CMDB zwischen BCM und IT-Betrieb und um ITSCM für Cloud-Dienste.
📅 05.11.2026, ab 10:00 Uhr
📍 HiSolutions AG, Berlin | Kostenfrei
https://www.hisolutions.com/knowhow-itscm

#ITSCM #BusinessContinuity #DisasterRecovery #ISO27031

Your Hypervisor Exit Plan Should Be a Recovery Runbook

Most hypervisor exits start as migration programs. Inventory the VMs, pick a target, choose a migration or conversion tool, build waves, and move the workloads. That gets virtual machines from one platform to another. It does not prove the application can run, be protected, or be recovered after the source platform is gone. Please see Veeam Hyper-V Backup Failing with “Incorrect Function” During Checkpoint Creation, and Synology Surveillance365: Cloud-Based Camera Management Without an On-Premises Surveillance Server.

I would plan the exit the same way I plan recovery. Build a runbook around each application or recovery group. Define the source, target, recovery point, dependencies, startup order, network changes, guest changes, validation steps, owners, and rollback conditions. Then test that process while the source environment is still healthy enough to give you options.

Exit criterion: A workload has not really left a hypervisor until it can be recovered, validated, protected, and operated without that hypervisor.

Migration tooling solves movement, not acceptance

Migration products are good at moving data and creating a target VM. Some also handle replication, target sizing, network mapping, guest preparation, and cutover. Those capabilities matter, but the migration job finishing is still an infrastructure event. The application owner cares whether the service works after the move.

Microsoft makes that separation explicit in Azure Migrate. Its VMware migration workflow supports a test migration before final cutover, keeps the source VM running during the test, and recommends validating the application on an isolated target before performing the real migration.[1] Veeam exposes the same basic idea from the recovery side. Current Veeam Backup & Replication 13.1 documentation supports restoring VMware vSphere workloads to other targets, including Microsoft Hyper-V, Nutanix AHV, and Proxmox VE.[2][3][4]

Those products do not make every workload portable. They give the operator mechanisms that can be tested. Firmware, virtual hardware, guest drivers, network identity, application dependencies, licensing, performance, and vendor support still have to be proven for the workload being moved.

The runbook is where that proof belongs.

Also, see Strategic breakdown and step by step guide to upgrading to VBR 13.1, Veeam Oracle RMAN Troubleshooting: Connection Timeout, Broken Pipe and a Stuck RMANPluginManager, and SizeTrend: A Fast Windows Disk Space Analyzer for Storage Analysis.

Build recovery groups, not a spreadsheet of VMs

A VM inventory is useful, but it is the wrong unit for deciding whether an application can leave a platform. A three tier application with a database, middleware server, web nodes, load balancer, DNS records, service accounts, certificates, file shares, and an external API is not seven independent VM moves. It is one service with a dependency chain.

I would group workloads the same way I would group them for disaster recovery. Start with the business service, then identify every component required to bring that service back. The hypervisor objects are part of the list, but so are identity, DNS, time, routes, firewall policy, storage, load balancing, secrets, certificates, monitoring, backup, and application validation.

The table is deliberately broader than VM conversion. If the runbook only records source host, destination host, and maintenance window, most of the hard questions are still waiting for cutover night.

The first real test should happen before cutover

The best time to discover that a guest will not boot on the target is while the production copy is still running. The same is true for a missing route, hard coded IP address, license tied to virtual hardware, old storage driver, firewall dependency, or application check nobody documented.

A test does not have to reproduce the final cutover perfectly. It needs to reproduce enough of the target state to expose the assumptions. Recover or migrate a representative copy to an isolated network, apply the expected guest conversion, bring up the required dependencies, and run the same acceptance tests that will be used during the real move.

Veeam Recovery Orchestrator uses a similar operating model for recovery. Restore plans have defined recovery locations and target RTO and RPO values, and Orchestrator provides readiness checks plus isolated DataLab testing for supported recovery locations.

The tooling is different from a hypervisor exit project, but the discipline is the same: check that the target is ready, execute the plan, verify the workload, capture the result, and fix the runbook before the event that matters.

Operational view: A successful test should create changes to the runbook. If nothing was learned, either the workload is unusually simple or the test did not exercise enough of the real cutover path.

Please see Veeam ONE 13.1.0.7034 Upgrade: Complete Pre-flight and Step-by-Step Guide, Upgrading Veeam Backup Enterprise Manager to v13.1 and Applying System Updates, and In-place upgrade of Veeam Recovery Orchestrator to version 13.1.

Track three clocks during an exit

Migration projects often collapse every timing question into one maintenance window. I prefer to track three different clocks because they fail for different reasons.

Data movement clock

This starts when initial replication, copy, or restore staging begins and ends when the target has enough data to support cutover. Large disks, change rate, repository throughput, WAN capacity, storage performance, and conversion overhead live here. Most migration tooling is very visible at this layer.

Service cutover clock

This starts when the production service is intentionally interrupted or traffic begins moving away from the source. It includes the final sync or recovery point, source shutdown, target startup, dependency sequencing, network changes, DNS or load balancer changes, and any guest conversion that cannot be completed earlier.

Acceptance clock

This starts when the target is technically available and ends when the application owner accepts the service. Authentication, data consistency, background jobs, integrations, scheduled tasks, certificates, monitoring, security agents, performance, and actual user transactions live here.

A fast data copy can still produce a long outage when network and application validation are slow. A VM that boots in five minutes can still spend two hours waiting on DNS, a firewall change, a broken integration, or an owner who does not have a defined acceptance test. Measure the clocks separately so the rehearsal tells you where the cutover is actually spending time.

Cutover should read like a recovery procedure

Once the test path works, the production cutover should be boring. The steps should already have owners, inputs, expected results, and stop conditions. The exact sequence will vary, but a practical runbook usually looks something like this:

1. Confirm target compute, storage, network, credentials, and recovery tooling are ready.
2. Confirm the last successful protection job and the recovery point that will be used if the migration path fails.
3. Freeze application changes or place the service into the planned maintenance state.
4. Complete the final replication, backup, export, or synchronization step.
5. Shut down or isolate the source workload according to the cutover plan.
6. Create or recover the target workload and apply the documented target mappings.
7. Start dependencies and application components in the tested order.
8. Apply DNS, routing, firewall, load balancer, and external integration changes.
9. Complete guest cleanup and install the target platform integration components required for normal operations.
10. Run infrastructure checks, then run the application acceptance test.
11. Enable monitoring, backup, patching, security tooling, and operational ownership on the target.
12. Hold the source state for the defined rollback period, then decommission it only after acceptance and recovery protection are confirmed.

The recovery point in step 2 matters even when the primary move uses a migration product. It gives the team an independent way to recover when the migration workflow fails after the source has already been changed, shut down, or partially decommissioned.

Veeam documents Instant Recovery to Hyper-V as a recovery mechanism that can also be used to migrate infrastructure between environments. Workloads run from backup with limited I/O performance until they are moved to production storage.[7] I would treat that kind of capability as a fallback path inside the exit runbook, not as a reason to skip a controlled migration when the normal path is healthy.

Guest conversion is part of the recovery test

Cross platform recovery proves quickly that a VM is more than its virtual disks. The guest may need a different virtual storage controller, network adapter, firmware mode, platform tools, drivers, or boot configuration. Appliances and workloads with passthrough devices, shared disks, virtual TPM requirements, hardware bound licensing, or vendor support restrictions may need a different path entirely.

The point is not to build one giant universal conversion checklist. Record what each recovery group actually needs and prove it. If a Windows server needs old platform tools removed after the target boots, script it and put the script in the runbook. If a vendor appliance is only supported on a specific platform, treat that as a workload constraint instead of discovering it after the project has already committed to the destination.

Architecture point: Portability is a tested property of a workload. It is not a property you can assign to the whole VM estate because the backup product has a cross platform restore button.

Rollback becomes a data problem as soon as the target starts taking writes

Rollback is often written as “power the old VM back on.” That is only safe if the source is still authoritative and nothing important changed on the target. Once users, jobs, or integrations write new data to the destination, a return to the source can lose or split data.

The runbook needs a rollback boundary. Define the point after which rollback requires data reconciliation, database recovery, reverse replication, transaction replay, or an application specific recovery step. Decide who can call the rollback, how long the source is preserved, and what evidence is required before the target becomes authoritative.

This is one of the reasons I prefer a recovery mindset for exit work. Recovery teams already think in terms of known points, data authority, dependency order, validation, and controlled return to service. Those are exactly the questions that appear when a migration fails halfway through a cutover.

A migration wave should end with recovery ownership on the new platform

Moving the VM is only the middle of the wave. The application should leave the old platform with its operational dependencies moved too. Backup jobs must protect the target. Monitoring must know the new object. Security agents and vulnerability tooling need to report. Patch and configuration management must still work. The CMDB and support team need the new location and owner.

I would also run a recovery test from the new platform before declaring a critical workload complete. The project has already proved movement from source to target. The second test proves the organization can protect the workload on the destination and recover it again without using the platform it just left.

That test catches a different class of problems. A backup integration may not be configured for the target cluster. Recovery networks may still reference old port groups. An operations script may call the old management API. A monitoring check may use the retired hostname of a management server. None of those problems stop the migration job, but they can make the new environment unrecoverable the day after the old one is removed.

Know when the old platform is actually out of the path

A hypervisor exit is complete when the source platform is no longer required for normal service or for recovery. That is a higher bar than “all VMs moved.”

Before the last host is decommissioned, I would want evidence that critical recovery groups can start on the new platform, application owners have accepted them, backups are succeeding, restores have been tested, monitoring and security are active, and the recovery documentation points only to infrastructure that will still exist after the project closes.

Keep the source platform as long as it is serving a deliberate rollback purpose. Do not keep it indefinitely because nobody knows whether an old script, recovery workflow, or operational dependency still needs it. The runbook should tell you exactly when that dependency ends.

Key Takeaways

• Plan hypervisor exits around application recovery groups, not individual VM moves.
• Use migration tooling for movement, but require isolated testing and application acceptance before production cutover.
• Track data movement, service cutover, and application acceptance as separate clocks.
• Give every wave a tested recovery point and an executable rollback rule before the source is shut down.
• A workload is not finished until backup, recovery, monitoring, security, and operational ownership work on the destination without the old hypervisor.

Source Notes

Product behavior changes. These sources were checked against public vendor documentation available on September 13, 2026.

1. Microsoft Learn: Migrate VMware vSphere VMs with the Migration and modernization tool.
https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-vmware-agent?view=migrate

2. Veeam Backup & Replication User Guide: Data Recovery for VMware vSphere.
https://helpcenter.veeam.com/docs/vbr/userguide/data_recovery.html

3. Veeam Backup & Replication User Guide: Nutanix AHV.
https://helpcenter.veeam.com/docs/vbr/userguide/nutanix_ahv.html

4. Veeam Backup & Replication User Guide: Proxmox Virtual Environment.
https://helpcenter.veeam.com/docs/vbr/userguide/proxmox_ve.html

5. Veeam Recovery Orchestrator User Guide: Restore Plans.
https://helpcenter.veeam.com/docs/vro/userguide/restore_plans_overview.html

6. Veeam Recovery Orchestrator User Guide: Running Plan Readiness Check.
https://helpcenter.veeam.com/docs/vro/userguide/running_readiness_check.html?ver=13

7. Veeam Backup & Replication User Guide: Instant Recovery to Microsoft Hyper-V.
https://helpcenter.veeam.com/docs/vbr/userguide/instant_recovery_to_hv.html

I hope you found the following article on “Your Hypervisor Exit Plan Should Be a Recovery Runbook” very useful. Please feel free to leave a comment below.

Kyushu Shinkansen Restores Full Service 52 Days After Kumamoto Earthquake

The Kyushu Shinkansen (bullet train), which had been partially suspended following the magnitude 6.8 earthquake that struck Kumamoto…
#EuropeSays #Japan #JP #bullettrain #disasterrecovery #earthquake #earthquakes #kumamotoearthquake #kyushushinkansen #naturaldisasters #Shinkansen #trains
https://www.europesays.com/japan/94605/

Your backups are not real until you restore them. A production Postgres died at 2:47 AM and the untested restore failed. Learn WAL https://www.valtersit.com/guides/databases/database-backup-strategies-wal-pitr-and-restore-testing/

#PostgreSQL #Backup #DisasterRecovery

Discover the unprecedented Amazon AWS data loss in Bahrain and the UAE. Drone strikes destroyed redundant availability zones, leaving cloud data irrecoverable.

#AmazonAWS #DataLoss #CloudSecurity #DisasterRecovery #MiddleEast

https://securityexpress.info/amazon-aws-data-loss-middle-east/?utm_source=mastodon&utm_medium=jetpack_social

Train staff on DR procedures annually. Well-trained teams respond faster and more effectively during emergencies. Ensure compliance and security best practices #BCDR #DisasterRecovery #CloudResilience.

How long should you keep daily backups?

Our guide explains how to choose a retention window based on recovery needs, business impact, security, storage costs, and restore requirements.

Read the full guide: https://olvy.io/uTeJf

#Backups #WordPress #DisasterRecovery #DataProtection

How to Generate a Full #VPS #Backup Using #rclone (Simple 3-Minute Guide)

This article provides a detailed step-by-step description of how to generate a full VPS backup using rclone.
What is rclone?
Rclone is a powerful open-source command-line tool for managing files on cloud storage services and local storage. You can think of it as kind of like "rsync" (the popular file-copying tool), but ...
Continued 👉 https://blog.radwebhosting.com/generate-a-full-vps-backup-using-rclone/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #googledrive #disasterrecovery #opensource #onedrive

2 homes, different traumas: Japan quake leaves scars seen and unseen

For thousands of survivors — especially those living near the epicenter in places like Yatsushiro — psychological and financial scars will endure long after the initial disaster

https://justpaste.in/news/kumamoto-earthquake-aftermath-updates-july-30-2026/

#DisasterRecovery #disasters #Earthquake #Japan #AsiaPacific

Japan quake survivors battle thirst, heat as death toll rises to 25

Many of the port city’s roughly 58,000 households are still without running water or power

https://justpaste.in/news/kumamoto-japan-earthquake-updates-july-30-2026/

#DisasterRecovery #Earthquake #Japan #AsiaPacific #EditorsPick

هجوم مركز البيانات الوطني الإندونيسي

https://cybercases8.wordpress.com/2026/09/11/%d9%87%d8%ac%d9%88%d9%85-%d9%85%d8%b1%d9%83%d8%b2-%d8%a7%d9%84%d8%a8%d9%8a%d8%a7%d9%86%d8%a7%d8%aa-%d8%a7%d9%84%d9%88%d8%b7%d9%86%d9%8a-%d8%a7%d9%84%d8%a5%d9%86%d8%af%d9%88%d9%86%d9%8a%d8%b3%d9%8a/

"Mental Health of 9/11 Response and Recovery Workers"
https://www.psychologytoday.com/us/blog/disaster-by-choice/202609/mental-health-of-911-response-and-recovery-workers
 
#Health #MentalHealth #MHFA #FirstAid #MentalHealthAwareness #GlobalHealth #DisasterResponse #DisasterRecovery #EmergencyResponse #FirstResponse #FirstResponders #EmergencyResponders #Terrorism #Remember911 #RememberTheSky #NeverForget911

How to Generate a Full #VPS #Backup Using #rclone (Simple 3-Minute Guide)

This article provides a detailed step-by-step description of how to generate a full VPS backup using rclone.
What is rclone?
Rclone is a powerful ...
Continued 👉 #disasterrecovery #onedrive #googledrive #opensource

How to Generate a Full VPS Bac...

(holding comments about the business model and pay of this org's execs, but this is a huge issue when your state/county is overwhelmed with disasters, particularly for Hawaii with no nearby places to draw from, and everything is an airplane flight away --- they are short volunteers, because all the local volunteers clearly have been impacted themselves and no one is going to pay for a plane ticket to volunteer on another island)

https://www.hawaiinewsnow.com/2026/09/09/red-cross-asks-volunteers-help-with-hurricane-lowell-recovery-efforts/

#disasters #disasterrecovery

Choosing a WordPress backup plugin isn't just about features.

We compare 7 popular options and look at remote storage, incremental backups, WooCommerce requirements, retention, recovery objectives, and restore testing: https://olvy.io/65ZPr

#WordPress #Backups #WooCommerce #DisasterRecovery #WordPressSecurity

https://www.europesays.com/britain/119418/ PeaSoup & Vawlt forge UK sovereign multi-cloud tie-up #ApplicationInfrastructure #BusinessContinuity #CarbonFootprint #Cloud #CloudMarketplace #CloudSecurity #CloudStorage #CyberResilience #DataCenters(DC) #DataGovernance #DataProtection #DataResidency #DataSecurity #DataSovereignty #DigitalTransformation #DisasterRecovery(DR) #EnergyEfficient #GreenIT #HybridCloud #ITDepartment #MultiCloud #Orchestration #sustainability #UK #UnitedKingdom #UnitedKingdom(UK) #Vawlt

Six evidence checks for CRM cutovers: identity, relationships, automation, access, reporting, and recovery. Includes a worked reconciliation example. https://hackernoon.com/a-green-import-report-is-not-a-crm-cutover-test #disasterrecovery

https://www.europesays.com/ie/676281/ Synology expands ActiveProtect with cloud recovery ##virtualisation #AmazonS3 #AmazonWebServices(AWS) #Antivirus(AV) #Bitdefender #BusinessContinuity #CrossPlatform #Cybersecurity #DataProtection #DataSecurity #DisasterRecovery(DR) #Éire #ESET #GoogleWorkspace #HybridCloud #IE #Ireland #ITDepartment #ITInfrastructure #MachineLearning(ML) #MicrosoftAzure #MultiCloud #NetworkAttachedStorage(NAS) #Synology #Technology #virtualization

#DisasterRecovery company to shutter #Portland facility, lay off 55 workers - oregonlive.com

https://www.oregonlive.com/business/2026/08/disaster-restoration-company-to-shutter-portland-facility-lay-off-55-workers.html?outputType=amp

Next Saturday at #EuroBSDCon 2026, I'll tell the story of one of the longest nights of my career.

On 10 March 2021, I had just fallen asleep when the alerts started arriving. One server down. Then another. And another.
Different servers, different workloads, one thing in common: the OVHcloud Strasbourg data centre.

Then came the news: SBG2 was on fire.

I had 142 servers there.

The mission for the night was simple to state: bring the critical services back before 8, then recover everything else as quickly as possible.

This talk is about what happened next. The things that worked, the architectural choices that saved us, and especially the ones that failed when we needed them most.

And it's also the story of why that night changed the way I design infrastructure, and why BSD systems became such an important part of it.

The night 142 of my servers went up in the clouds. Physically.

📅 Saturday 12 September, 11:15
📍 EuroBSDCon 2026, D.0.02

#BSD #FreeBSD #EuroBSDCon #Sysadmin #Infrastructure #RunBSD #NetBSD #OwnYourData #Linux #DisasterRecovery

Another save for the #Synology #ActiveBackupForBusiness.

After a corrupted windows OS partition due to boot loop caused by a faulty PSU, the machine was recovered in 30 min (250GB partition) following a PSU replacement.

It's always easy when you have an up to date and working backup. 😎

#selfhosting #selfhosted #homelab #disasterrecovery #backup #abb #activeprotect

How to Generate a Full #VPS #Backup Using #rclone (Simple 3-Minute Guide)

This article provides a detailed step-by-step description of how to generate a full VPS backup using rclone.
What is rclone?
Rclone is a powerful open-source command-line tool for managing files on cloud storage services and local storage. You can think of it as kind of like "rsync" (the popular file-copying tool), but ...
Continued 👉 https://blog.radwebhosting.com/generate-a-full-vps-backup-using-rclone/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #opensource #disasterrecovery #onedrive #googledrive

Every IT environment has at least one system where the disaster recovery plan is basically:

"Call the person who knows how it works."

Bonus points if that person left three years ago.

What's the most optimistic disaster recovery plan you've encountered ?

#IT #Technology #SysAdmin #DisasterRecovery

Backup/restore from and to #Proxmox works like a charm (ZorinOS18 machine).

#APM2 #Synology #ActiveProtectManager #backup #ransomware #selfhosting #selfhosted #homelab #disasterrecovery

It's upgrade time! #APM2
#Synology #ActiveProtectManager #backup #ransomware #selfhosting #selfhosted #homelab #disasterrecovery

New #Synology #ActiveProtectManager 2.0 has been released with close to 30 new features, and over 40 fixes compared to the 1.2 version.

https://www.synology.com/en-eu/releaseNote/APM?os=APM&version=2.0

#backup #ransomware #selfhosting #selfhosted #homelab #disasterrecovery

On Tuesday 8th Sept, I'll be speaking at 🇬🇧 @postgresuk about rebuilding a major piece of #PostgreSQL #backup infrastructure from scratch! Don't miss this great event in #London, use discount code JIMMY20 at https://2026.pgday.uk, CU there! 🐘🔥

#Postgres #Conference #OpenSource #DisasterRecovery

Backup Verification Exposes Hidden Recovery Risks

Relying solely on data backup isn't enough - you need to verify that your applications can actually be recovered and restored to working order in the event of a disaster. Simply copying data to storage doesn't guarantee a smooth recovery, and that's a risk many IT professionals are unknowingly taking.

https://osintsights.com/backup-verification-exposes-hidden-recovery-risks?utm_source=mastodon&utm_medium=social

#BackupVerification #CyberResilience #DataRecovery #DisasterRecovery #EmergingThreats

University of South Florida: New hurricane recovery technology being tested on Florida roads during peak season. “Working with transportation professionals across Florida, including those at the Florida Department of Transportation and Sarasota County, [Professor Hao] Zhou is developing AI tools to help transportation officials assess storm damage more efficiently, improve traffic signal […]

Infinito.Nexus 13.0: A Sovereign Cloud on Clearnet or Tor

https://blog.infinito.nexus/blog/2026/08/26/infinito-nexus-13-0-a-sovereign-cloud-on-clearnet-or-tor/

Big Island Now: Frustration grows as 10,000 plus Hawaiian Electric customers reach a week without power, answers

Currently, about 11,290 Hawaiian Electric customers without power, including 9,300 in Puna and 1,300 in Kaʻū, the areas likely to be impacted the most in the state by approaching Tropical Storm Moke.

https://bigislandnow.com/2026/08/22/frustration-grows-as-10000-plus-hawaiian-electric-customers-reach-a-week-without-power-answers/

#poweroutages #HurricaneLala #HIwx #disasters #disasterrecovery

"...HOUSTON, Texas -- When Lily Dubose was eight years old, she made it her mission to spread joy to children impacted by Hurricane Harvey. Fast forward nine years, and her vision has expanded into a non-profit, Lily's Toy Box, and a massive warehouse filled with over 20,000 toys.

"I started giving away my Legos and dolls to kids who flooded, and it just went off from there," said Lily, who is now going into her senior year of high school..."

https://abc7.com/videoClip/19698498/

#disasterrecovery #hurricanes