WSL2 Backup to OneDrive Cloud

WSL2 provides great disk performance, but it requires storing the files separately in a virtual disk that is not accessible by OneDrive. WSL2 can be backed up with wsl –export Debian to a VHD or TGZ, but that is a complete disk backup of 20gb or more – not scalable for hourly backups.

With this approach, we use Windows Task Scheduler to trigger robocopy to incrementally sync directories from WSL2 to Onedrive’s native FS, so incremental copies are fast ( 1 s per 10k files), and OneDrive sync time remains negligible.

Continue Reading ...

IPV6 Migration Guide for Developers using AWS EC2 -- A Primer

With the news that AWS will be now charging about $4 / instance-month for public IPv4 addresses, many developers who procrastinated ipv6 migration are finally updating both ends of their development setup.

It’s a great time to migrate, as all the intermediate infrastructure now supports IPV6 readily. Moreover, you’ll benefit from permanent , global addresses for your development instances.

Pros

• A single, global, stable address for EC2 instances that never changes. No need for dynamic DNS and other hacks
• No need to pay for Elastic IP addresses on dev instances
• Global addressing for mutual duplex services (no more NAT needed)
• Better flexibility and clarity for addressing, including Link Local & local addresses

Cons

• Time needed to migrate infra to IPV6
• Clumsier & less-memorable addresses, with unfamiliar idioms (e.g. no more using 127.0.0.1 or 192.168.1.1 – though there are replacements) inherent
• Bugs in legacy code that assumes 32 bit & string-representations of ipv4 addresses

Concepts & Approach

In theory, IPV6 uses 128bit addresses in place of 32 bit. Most of the intermediate infra (ISP, backbone) is now compatible. The two areas of attention for developers would be the server side with AWS , and the client side with your home/office network.

Continue Reading ...