Blog Marcina Bojko

Linux,Windows,serwer, i tak dalej ;)

Posts Tagged ‘windows

HV-Packer in version 1.0.8

leave a comment »

Written by marcinbojko

Maj 25, 2019 at 17:01

Napisane w work

Tagged with , , , ,

Veeam Instant Recovery – when life is too short to wait for your restore to complete.

leave a comment »

(courtesy of @nixcraft)

„Doing backups is a must- restoring backups is a hell”
So how can we make this ‚unpleasant’ part more civilised? Let’s say – our VM is a couple hundred GB in size, maybe even a couple TB and for some reason, we have to do some magic: restore, migrate, transfer – whatever is desired a the moment.

But in oppositon to our will – physics is quite unforgiving in that matter – restoring takes time. Even if we have bunch of speed-friendly SSD arrays, 10G/40G network at our disposal, still few hours without their favourite data can be ‚no-go’ for our friends from „bussiness side”.
In this particular case, Veeam Instant Recovery comes into rescue.
How does it works?
It uses quite interesting quirk – in reality, the time you need for having your VM ready is to restore small, kb-sized VM configuration, create some sparse files for drives, and mount the drives itself over a network. This way, within 3-5 minutes your machine is up and ready

But, disks, you say, disks! „Where are my data, my precious data?”.
They are still safe, protected in your backup repository, mounted here as ReadOnly volumes.

Phase 1

So, after an initial deploy our VM is ready to serve requests. Also in Veeam B&R Console tasks is waiting for you to choose: begin migration from repositories into real server, or just to power it off.

Phase 1 during restore:

  • IO Read is served from mounted (RO) disk from backup repisotory
  • IO Write from client is server into new Drive snapshot (or written directly into sparse Disk_1 file.
  • In background, data from backup repository are being moved into Disk_1_Sparse file.




Phase 2

Phase 2 to begins when there are no data left to move from backup repository – this initiates merging phase, when ‚snapshot’ (CHANGED DATA) are being merged with originally restored DISK_1.

As with everything, there are few PROS and CONS

PROS:

  • machine is available withing a few minutes, regardles of its size
  • during InstantRecovery restore, VM is alive and can (slowly) process all requests

CONS

  • restoring can take a little longer then real ‚offline’ restore
  • space needed during restore proces can be as much as twice your VM size. If you’ll ran out of space during restore, process will fail and you’ll loose all new data.
  • your data are served with some delay – to read a needed block, VM have to reach it from repository, which means on-the-fly deduplication and decompression
  • if your VM is under heavy use, especially on IO Write, restoring can take much longer then anticipated, as there will be no IO left to serve read and transfer from original disk.
  • if your restore will fail from ANY reason – your data are inconsistent. You’ll have to repeat this process from point 0 – any data changed in previous restore attempt, will be discarded.

So which targets should be ideal for this process?

Any VM which doesn’t change data much but needs to be restored within few minutes:

  • frontend servers

Any VM which offers small-to-medium usage of IO Read , not so many IO Write

  • fileservers

Which targets should we avoid?

  • database servers
  • cluster role members/nodes

Written by marcinbojko

Marzec 24, 2019 at 19:17

Napisane w work

Tagged with , , , , ,

Newest member in Packer’s family – Azure VM images with managed disks.

https://github.com/marcinbojko/az-packer

Written by marcinbojko

Marzec 3, 2019 at 17:29

Napisane w work

Tagged with , , , , ,

Hyper-V Packer Gen2 machines – version 1.0.5

https://github.com/marcinbojko/hv-packer

 

Written by marcinbojko

Październik 3, 2018 at 20:02

Napisane w work

Tagged with , , , ,

Hyper-V Packer Gen2 machines – version 1.0.4

https://github.com/marcinbojko/hv-packer

Written by marcinbojko

Maj 21, 2018 at 19:44

Napisane w work

Tagged with , , , , ,

Simple Foreman Template (with Grafana Dashboard) for Zabbix 3.x

Small project, using trappers instead of zabbix-agent active mode. I wanted to have better control over the pushing layer and intervals.

https://github.com/marcinbojko/foreman-template

Written by marcinbojko

Kwiecień 24, 2018 at 18:15

Hyper-V Packer Gen2 machines – version 1.0.3

The most „bad ass” release so far 🙂

  • * `BREAKING FEATURE` – preparing switching to submodules/subtree for ./scripts and ./files – to share common code with other providers
  • * tree structure in `./scripts` and `./files`, moved to `./extras`
  • * [Windows] adding `phase-3.ps1` script to put less generic stuff there. Just uncomment line with `exit` to get rid of it
  • * [Windows] added support for `Windows Server 1709 Edition (Standard)`
  • * [Windows] remove some clutter from `bootstrap.ps1`
  • * [Windows] added `exit 0` for most of the scripts as some external commands were leaving packer with non-zero exit codes
  • * [CentOS] added `zeroing.sh` script to make compacting more efficient
  • * [CentOS] reworked bug with UEFI – this time after deploying from image you can run script `/usr/local/bin/uefi.sh` which will recheck and readd CentOS UEFI entries. For SCVMM deployments (which separates vhdx from vmcx) use `RunOnce`
  • * [CentOS] removed clutter from `provision.sh`
  • * [CentOS] removed screenfetch, replaced with neofetch
  • * [CentOS] reworked `motd.sh` in `/etc/profile.d` to reflect .Xauthority existence*

https://github.com/marcinbojko/hv-packer

Written by marcinbojko

Luty 23, 2018 at 19:34

Napisane w work

Tagged with , , , , ,

%d blogerów lubi to: