• EN

Replies posted by Michael Melter

100 Comments

Scott
ScottVeeam Legend
posted in Discussion Boards

Largest VM you backup?

What kind of workload is it for you, that “needs” those monster VMs? For our customers with VMs of ~30TB max. it’s mostly fileservers that have gone nuts during decades of lacking governance… 😉There we usually have the discussion about NAS backup being an alternative with much better parallelity throughout the whole job run. Especially when V12 brings us NAS2tape.Monster VMs tend to be the onces rolling in via a single thread at the end of a VM backup job.Challenge with NAS backup for Windows/Linux servers is, that it gets waaaaaay more expensive. 1VM=1VUL vs. 30TB=60VUL…

52
E
1 year ago
D
DomhoNew Here
asked in VUG Germany

Dateiausschlüsse VM | Veeam Backup & Replication 11

Kleine Ergänzung: Win-Dedup im Gast würde funktionieren, ist aber nicht empfohlen. Ein feiner Unterschied… 😉

4
D
1 year ago
D
DomhoNew Here
asked in VUG Germany

Dateiausschlüsse VM | Veeam Backup & Replication 11

Die “Exclusions” im Guest-Processing sind prinzipiell genau die richtige Stelle.Beachten sollte man dabei, dass es nicht zu viele Exclusions werden sollten, da dies das Backup verlangsamt. Insbesondere der Ausschluss vieler sehr kleiner Dateien lohnt in Hinblick auf die Platzersparnis im Backup eher nicht.Wildcards sind erlaubt (*?). Allerdings glaube ich nicht, dass VBR etwas mit der \/ Kombi anfangen kann.Entweder Du schließt *.XXX komplett aus (was ggf. die Backupzeit deutlich verlängern könnte), oder Du versuchst es mal mit einem relativen Pfad: c:\users\..\*.XXX könnte funktionieren, da ..\users laut Manual auch funktionieren soll. Das habe ich selbst aber nicht getestet.Obacht: Generell funktionieren File-Exclusions nur ab VBR Enterprise Lizenz oder VUL und mit NTFS im Gast. Win-Dedup im Gast ist nicht erlaubt.

4
D
1 year ago
Nico Losschaert
Nico LosschaertVeeam Legend
asked in Discussion Boards

VBO365 - Public folders - Modern authentication and Legacy Protocols

There is an expensive alternative. You could also install a DC and Exchange Server as Cloud VMs or On-Premise machines, do a Exchange Hybrid configuration and migrate the public folder from Exchange Online to the “Exchange Server”. Somehow. I’m not sure if there is a direct migration method.  For me, the shared mailbox solution is currently the easiest and cheapest one. But I understand, it’s not easy for big enterprises with a lot of public folders and business processes around them. That’s currently the way we suggest it to public folder lovers. Need not be to expensive: You get the remaining on-prem Exchange license key for free because you need a remaining one also if you just want to run remaining DCs in your on-prem environment.Exchange hybrid licensing - Microsoft Q&AIf you host only a public folder database the, to my understanding there’s even no need for an additional paid licenses (as these would be user mailbox licenses anyways, which are not there). Correct me, if you

19
Ian Sanderson
1 year ago
M
MckITGuysNot a newbie anymore
asked in Discussion Boards

Restoring all domain controllers in a Windows domain (on vmware)

Wow. Quite a comprehensive thread this has gotten. Very interesting topic.To me the most important part of the question to me in the first place was:All (!) DCs have to be restored at once.If you try that with VBR without further measures it will fail.Not a single one of the DCs will bring up the domain. This is because VBR - even since V2 - is smart enough to always do a non-authoritative-restore. This will bring up the DC in a state which first wants to copy the full domain from another DC still alive. You can take note of the process by the additional reboot a DC always does after being recovered by VBR.Without this full sync of the domain DB your recovered DC will be a useless brick.Problem is: If you recovered all of them, they will all look for a surviving DC - but there is none.You then have to put one of them into an authoritative restore manually afterwards by e.g. setting the “Burflags”. Have that process in your emergency guideline just in case...Veeam btw CAN do an authorit

41
Link State
17 hours ago
T
TimoWITNot a newbie anymore
asked in VUG Germany

Replikation der Backups an zweiten Standort

Hallo Timo.Willkommen im Forum. 😀VBR (auch Essentials) kann zunächst mal “nur” VMs, NAS Daten und physische Workloads sichern. Für M365 Tenants bräuchtest Du ein weiteres Produkt: VBM, also Veeam Backup für Microsoft 365.Wenn wir mal nur VBR betrachten, gibt es für die Kopie an an weiteren Standort mehrere Möglichkeiten. Teilweise benötigen diese ein VPN. Hier mal ein knapper Überblick:Backup Copy in ein Repo (Windows/Linux/NAS mit dort lokalem Gateway Server) - braucht zwingend ein VPN zum 2. Standort. Eine zus. Veeam Lizenz braucht man nicht. Der primäre Hyper-V ist ja sicher schon lizensiert. Die Einbindung geschieht durch die remote Installation (via VPN) des Repo-Servers aus der Veeam Konsole heraus. Backup Copy zu einem VCSP (Veeam Cloud Service Provider). Den müsstet Ihr Euch suchen: https://www.veeam.com/de/find-partner.html?country=DEU&type%5B%5D=VCSP&page=1 Hier braucht man auch keine zus. Lizenz. Lediglich zur Verwendung des WAN Accelerators müsste es bei Euch minde

10
JMeixner
1 year ago
M
mathschutNew Here
asked in VUG Germany

Veeam Windows Repo SSD Cache

Hallo @mathschut.Prinzipiell sollte SAS ja 6G oder 12G liefern. Also ~600MB/s oder ~1.200MB/s. Immer noch ein Bottleneck, bei 40 Spindeln, aber mehr als 100MB/s.Einen SSD Cache für ein Repo kennt VBR selbst nicht. Manche RAID-Controller können das. Aus meiner Sicht aber der falsche Weg. Spätestens wenn beim Schreiben der Cache voll ist, ist wieder alles langsam.Welchen RAID-Level verwendest Du? R6 hat ja durch doppelte Parity eine Schreibhemmung. Ich verwende daher für Repos eher mal auch ein R5 (natürlich dann nicht mit so vielen Disks auf einmal) mit Hot-Spare. Versuch doch mal die 40 Disks in ein paar R5 mit max. 6-7 Spindeln und eine gemeinsame Hot-Spare aufzuteilen. Das ganze in Veeam dann als ein großes SOBR sichtbar machen. Das sollte zumindest aus Sicht des RAID die Sache optimieren. 

16
MarkusH
1 year ago
Michael Melter
Michael MelterVeeam Legend
posted in Blogs and Podcasts

Veeam Storage Plugin for DataCore - Define a role to access DataCore with least privilege

Hello Michael, thank your for sharing. Just a quick question here with regards to Veeam Backup Server placement in order to leverage the Veeam Storage Plugin for DataCore. In most of the DataCore deployments, we use two DataCore Servers connected to each other over DAC cables and iSCSI transport protocol (Hyperconverged Virtual SAN scenario). In such scenario, does it make sense to deploy the Veeam backup server in a VM in order for its virtual NIC adapters to be able to reach the DataCore front-end ports ? Thanks! Massimiliano Hi Massimiliano.We deploy the VBR server as a VM most of the times. So this at least makes total sense to me.Regarding the network you have to be in: I would count DataCore to the inner circle of the management layer. So either you have to have firewall rules to be able to reach it through Rest-API calls from your VBR server or you have to place the VBR server in the same security ring of your netzwork to be able to gain access to the functionality.Same is true

4
Michael Melter
2 years ago
Michael Melter
Michael MelterVeeam Legend
posted in Discussion Boards

VBR DataCore Plugin V1.2.0 explained

I love it because of the flexibility and the investment protection possible.They have storage virtualization for 20+ years now. It didn’t even have the name by then.HCI is possible, but I’m still a big fan of the industry standard server hardware boxes with DataCore on. Then you just throw all the storage systems you have behind. No matter what vendor or feature set. You end up with synchronous mirrors, snapshots, CDP as mentioned and more. Even full Veeam support for your zoo of systems. And you don’t have to buy all those features over and over again for your new storage boxes. Just buy the fancy new AF box without any bells and whistles and merge it into your stack without even touching VMware. Also decomissioning old boxes becomes as easy as it can get.Just my 2ct…

2
Michael Melter
2 years ago
Chris.Childerhose
Chris.ChilderhoseVeeam Legend, Veeam Vanguard
posted in Discussion Boards

DataCore Plug-In for Veeam Backup & Replication

There’s some more things to mention regarding the plugin: It brings a new functionality I’ve been waiting for for years now: DataCore CDP Support.This ist not to be confused with Veeam’s CDP feature. DataCore CDP acts on a volume (LUN) level. In fact once activated it generates a redo log within the storage layer for the full datastore and e.g. all its VMs. Can be just 4h of retention or even a full week - if you alllow for enough buffer. The good point it: We do not need any snapshots beforehand now to minimize our RPO to almost zero.With DataCore CDP you can generate a so called rollback point on demand. E.g. right after a ransomware was detected. And you can create this rollback to seconds before it struck.It was somehow usable with the initial plugin but with some extra steps and overhead. Find my deep-dive of the plugin here: https://www.elasticsky.de/en/2020/06/veeam-storage-plugin-for-datacore-deepdive/With the new plugin Veeam will now immediately detect the rollback point as i

4
I
2 years ago
Steve.Jaynes
Steve.JaynesNew Here
posted in Discussion Boards

Multiple Tape Servers Managing Single Multi-Drive Library

  I like your approach with a tapeserver per repository server. I think this brings good performance. The disadvantage is that you have to partition your tape library and have to assign the number of drives and tape slots hard to the logical libraries. So, it is not possible to give more or less ressources to one tape server automatically when it needs them. A management instance which assigns tape drives dynamically to a tape server would solve this. Call it library manager/client or something else. 😎 Correct. That’s a weak point. But with per-VM-chains VBR more or less equalizes the amount of data being driven to a single library. Good point is, you still have the drive parallelity available for your jobs. Once you reach 3 drives there is no other option anyways. Despite you have >10G at the tape server.

10
JMeixner
2 years ago
Steve.Jaynes
Steve.JaynesNew Here
posted in Discussion Boards

Multiple Tape Servers Managing Single Multi-Drive Library

Just stumbled upon this.We regulary do connect the individual drives of a single library to different tape servers. Reason is - as stated - to circumvent a bandwidth bottleneck at the tape server. LTO8 wants to have up to 360MB/s. So four drives would be too much for 10G already.The only thing to keep in mind is: you have to partition the library. So to VBR they look as if they are individual single drive libraries. Most libraries with multiple drives offer that option.We don’t use virtual tape servers though - as it would only work with iSCSI anyways. I like to combine the tape server role with a Windows repository. So e.g. each extent of a SOBR can become a tape server as well. This ensures maximum speed during tape out. We use SAS or FC for the drives.

10
JMeixner
2 years ago
vNote42
vNote42On the path to Greatness
posted in Discussion Boards

[Heads up] Do not update to vSphere 7 U3 when running thin-provisioned VMDKs

Another reason why I love Veeam. QA is so much better. I would even run a beta productively with Veeam…

12
vNote42
2 years ago
vNote42
vNote42On the path to Greatness
posted in Discussion Boards

[Heads up] Do not update to vSphere 7 U3 when running thin-provisioned VMDKs

All these issues with U3 paired with now dropping our most widely used boot method in our customer environments (µSD-RAID1) is really giving me some headache. Reminds me of those times where they were destroying CBT several times within a single year...

12
vNote42
2 years ago
bp4JC
bp4JCInfluencer
asked in Discussion Boards

Backup logic/functionality question

Regarding the original question @bp4JC was asking: doesn’t a backup copy job always only copy the latest backup state in the very first run and this will thus always be an active full? A single new VBK is produced.https://helpcenter.veeam.com/docs/backup/vsphere/backup_copying_process.html?ver=110From my knowledge it’s the other way around: it’s not easy to have it copy the full chain with all the history… Here we would need some folder operations... 

18
Mildur
2 years ago
B
bhinx
asked in Discussion Boards

Virtual Machine restoration is very slow

What’s the current status of your recovery, @bhinx ?I would bet the beer I’m just about to consume that the slow rate is mainly due to the virtualized USB stack. This is by no means a performant scenario and I always would try to avoid it.Better option: connect your USB drive to your PC - ideally in the same network as the VBR server - and mount the folder on the USB drive containing the backup as an SMB repo to your VBR inside the VM.This will deliver way better performance. Or even push a “real” repo service to your PC.Next optimization step would be the type of proxy used. With the backup server inside a VM try to make it a hot-add proxy (=virtual appliance mode). This will also speed up the process as you won’t suffer from the ~40% throttle on the management interface of the ESX.

23
G
4 months ago
Michael Melter
Michael MelterVeeam Legend
posted in Discussion Boards

Potential crash by log-shipping databases

Thanks @Mildur for your comprehensive answer. You’re referring to the vanilla way.But my question was slighty different:When using log-shipping via Hyper-V with PS direct (here no network connection from DB to log-shipping server or repo is involved) your Hyper-V always has to be part of the path and stores the logs intermittently. Thats by design here. One of the rare cases where Hyper-V as something in advantage to VMware with VBR… See second method here: https://helpcenter.veeam.com/docs/backup/hyperv/sql_backup_log_shipping.html?ver=110 Your logs always get pre-handled on the SQL/Oracle itself. Also there a disk might fill up as VBR doesn’t check beforehand if the logs fit. OS disk e.g. might crash, if C: is used. Even a true log-shipping server might fill up. Here VBR uses the %temp% variable which can be adjusted of course.One might well take care to point those directories to a large enough drive. Those logs can be hundreds of GB in certain cases… Also no checks seem to be done

3
Mildur
2 years ago
Kseniya
Kseniya✨
published in News

Second intake of Veeam Legends 2021 is here!

Thanks for this great opportunity and for the “legendary” welcome provided here.

154923
falkob
2 years ago
falkob
falkobVeeam Vanguard
posted in VUG Germany

23rd of July - Veeam Usergroup Germany Meeting

I’ll be on! :)

4
regnor
2 years ago
Michael Melter
Michael MelterVeeam Legend
posted in Discussion Boards

Veeam Storage Plugin for DataCore

Even in HCI you might want to leverage snapshot only jobs or even CDP by hooking it onto the integration from your HCI VMs. Also the mode is IMHO smoother than hot-add. Many of the legends here will be aware that hot-add used to be called the “least robust” even by Veeam itself. ;)It’s more robust today, but I always prefer direct storage access.vSAN is different in that you don’t have the option to access the blocks directly. So hot-add is your only way to go so far.Personally I don’t prefer to limit the proxy to read-only. We often use the mode for restoring as well as we let thin provisioning be up to the storage and not the VM. Some customers though want to have read-only for security reasons as @vNote42 mentioned already. 

9
I
2 years ago
Falk
FalkComes here often
posted in VUG Germany

Veeam User Group Meeting Juni

@Falk Immutable Linux Repos sind ein gutes Thema. Da kann man sicher immer noch was mitnehmen.Ich könnte was zur Immutability mit ExaGrid beistellen. Dazu gerne noch was zu DataCore und deren CDP Funktion. Hier kann man Ransomware ggf. auch zusammen mit Veeam mit RPOs von wenigen Minuten begegnen. Bei Interesse bitte einfach Bescheid geben, dann bereite ich was vor.Mich würde noch Multitenancy mit Veeam in größeren Umgebungen interessieren. Man stelle sich vor, ein Kunde besteht aus vielen Tenants, deren Netze isoliert sind. Jetzt möchte man idealerweise ohne LAN Einzelobjekte recovern. VBEM scheidet so leider größtenteils aus. Waschen ohne sich Nass zu machen, sozusagen. :)Welche tollen Ideen gab es hier schon?Viele Grüße,Michael 

4
Falk
2 years ago
Michael Melter
Michael MelterVeeam Legend
posted in Discussion Boards

Veeam Storage Plugin for DataCore

Hi @vNote42. The config is fully supported as is the official plugin. Even the DataCore CDP integration I discussed in the blog is supported as it ends up to be a regular snapshot.I used to do a DeepDive video together with DataCore in German (shouldn’t be a problem for you ).https://www.datacore.com/de/event/deep-dive-das-optimale-backup-mit-sansymphony-und-veeam-br/Cheers,Mike

9
I
2 years ago
Michael Melter
Michael MelterVeeam Legend
posted in Discussion Boards

SOBR placement policy not adhered to - solution included

Thanks @Rick Vanover for sharing the KB article. Just to get it straight: the “new” method mentioned there (in 2017 already) is not the overhaul Anton kind of announced for V11. He was merely referencing the method to generate GFS points in backup copy chains I understood.Testing those large repos would be great I fully agree. We already did so multiple times in production and I know “it just works”. Besides those minor issues mentioned here, those constructs run just great in many of our customer environments we designed during our projects. I’m a big fan of the “hyper converged backup storage” I usually call it: 1-n industry standard servers all acting as DAS-ReFS-repos and maybe even as direct storage access proxies as well. Scalable LAN free backups - only limited by the speed of the HBA.

6
Rick Vanover
3 years ago
Michael Melter
Michael MelterVeeam Legend
posted in Discussion Boards

SOBR placement policy not adhered to - solution included

Hi @vNote42. Actually they exist since V9 or even earlier already. To my knowledge they are still valid. Some time ago I was taking part in a forum thread were Anton talked about plans to change the placement strategy in SOBRs from ground up in V11: https://forums.veeam.com/veeam-backup-replication-f2/sobr-placement-policy-disregarded-for-gfs-t68404.htmlWe’ll find out in a week or so…

6
Rick Vanover
3 years ago
vNote42
vNote42On the path to Greatness
posted in Discussion Boards

Experiences with orphaned backup files

Which exact version of 9.5 caused this issue? Did you delete the orphans manually or did VBR delete them after the update. I assume the first though… The only other reason I might have thought of is some sort of “immutability” function in your repo. I assume we will face things like this with the new V11 XFS repos as the underlying OS will prevent early deletes not in sync with the time-lock. Cheers,Mike

11
vNote42
2 years ago

Badge winners

Show all badges
Terms & Conditions