VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Hello,not all job types are supported on a scale-out repository.Please see here which types are not supported:https://helpcenter.veeam.com/docs/backup/vsphere/sobr_limitations.html?ver=120 Sorry, ich hätte auch in Deutsch antworten können. Macht der Gewohnheit hier in der Community… 😎
Thanks from Joe to Joe 😂You have shown some of this to us in Prague. Fine that the blueprints are open for all now.
Great 😎 this makes testing of some special functions much easier. 👍🏼
😂 my testing list gets longer and longer.Thank you Jonah, this looks very interesting and useful. 👍🏼
It will improve performance, but not much. I don't think that you will see a significat effect. I did not in the one environment I have tried it. So it can’t hurt, but it may not revolutionize my life. LOL I have jumbo frames enabled all through my environment, so I might as well turn it on. Thanks! Exactly 😎It doesn't hurt, but I won't save the day either.
It will improve performance, but not much.I don't think that you will see a significat effect. I did not in the one environment I have tried it.
Please try it and tell us the results. 😎👍🏼
In my environments each VM can be handled by another drive, but not backup files from one VM.It is possible that there is a change in behavior with V12.1, I am on V12.0 with my tape environments at the moment….And ok, LTO-7 has a transfer speed of 300MB/sec, but LTO-9 is still 50% faster 😎 BTW, I would interpret the statement from support the same way I said it.
This is the reason why I asked if you have per VM backup files activated 😎Ok, when you have one VM in this job only, then one tape drive will be utilized.And to include a second, unrelated VM into this job will not help, because the amount of data for your actual VM will not decrease and this will be handled by one tape drive even if you add several VMs.The only solution I see for this is to use a newer and more powerful tape drive. Fir example a LTO-6 drive has atransfer speed of 150MB/sec, a LTO-9 drive has a transfer speed of 400MB/sec.
You are welcome, @s.wagner. 😎If this has answered your question, you can close this topic with selecting a best answer.
Raspberry Pi has an ARM processor and is not supported.This is another processor architecture.
Your backup will not contain the snapshot. Veeam just saves the state of your VM files and the VM configuration files.
Fine. 😎I do not claim to possess the sole absolute wisdom. There are many valid solutions, I try to demonstrate some best practices I build up in over two decades in data ürotection business with this series.I enjoy to discuss about scenarios and solution. So, thank you for this, Shane. 👍🏼
I see your point, Shane. And I described your scenario in my article → Mixed approach – Snapshots and Replication.My main point of criticism with this is, that the storage system where the data is replicated on is in most cases t the system is designed to take over production if the main system fails. This scenario is completely valid to have a possible way to restore production very fast.But it must not be the only protection of your data. In addition to this you need a backup with the backup data on a completely separate system. From this restore of the data is slower, but the data is much more save.This is what I call tiered strategy - snapshots, replication AND backup (with 3-2-1 rule or better) together to protect your most valuable asset - your data. And yes, call me paranoid 😎, but most of my customers want exactly this, at least after the first attack or disaster….
The connection to vSphere 8 and vCenter 8 is not supported with VBR 9.5vSphere 8 is approximately 6 years newer than VBR 9.5The handling of certificates is very ddifferent in vSphere 5.1 and 8, there are 9 - 10 years development between them. It's not a problem of Win10 (Win10 is from 2015, so it is 8 years old, too).
Hello @metrobg,you mean updsted for V12.1?As far as I knoe there is no new ISO up to now.
And please be aware that Veeam Backup & Replication V9.5 is out of support for several years now.What do you want to achieve? A migration from an environment with vCenter 5.1 to a new environment?
I meant that it should work in a similar way via the Veeam Backup & Replication REST API, too - instead of the Veeam Service Provider Console REST API.
Fine solution @keironbell 👍🏼This should work in a similar way with server managed agents via the VBR Rest API, too.I haven’t scripted it myself up to now, but the functionality should be there….
Die Anbindung der QNAP per iSCSI ist auf jeden Fall sinnvoll, das ist deutlich stabiler und zuverlässiger als SMB.“Boot from Backup” kannst du mit Veeam auch machen, nennt sich dann Instant Recovery.
Very interesting, Steve. 👍🏼I hope this will be integrated in VBR in one of the next versions.
Worauf läuft dein jetziges Backup System jetzt? Auf einer VM auf dem System, dass gesichert wird?Best Practices Empfehlung ist, das Backup System vom Produktivsystem zu trennen. Dann könntest du einen physischen Server als Veeam Server und als iSCSI Host für das NAS verwenden.
Thank you @BertrandFR, I keep explaining this to customers and management, so I thought that I can write some articles about these topics for everyone. 😎
400 TB sind ein wenig hoch gegriffen.Du brauchst für einen Monat GFS mit wöchentlichen Fulls ingesamt 4 Fulls - ein active Full und drei synthetic Fulls. Die Fulls unterscheiden sich nur durch ihre Aufbewahrungszeit. Normalerweise wirst du heutzutage ein Filesystem mit Block Cloning Fähigkeiten benutzen wie z.B. ReFS oder XFS, auch Object Storage hat diese Fähigkeiten. Das heißt, dass die drei synthetic Full nicht mehr Platz auf der Platte brauchen als ein Incremental. Siehe auch https://helpcenter.veeam.com/docs/backup/hyperv/synthetic_full_hiw.html?ver=120Bei deinem Beispiel ist leider keine angenommene Änderungsrate angegeben. - nehmen wir mal 5% pro Tag an. Dann hast du 35TB active Full + 27 Incrementals (24 Incrementals und 3 synthetic Fulls) * 5% von 35TB (1,75TB) = 47,25TB. Insgesamt also ohne Deduplication und Compression ca. 82,25TB. Die Menge der Ersparnis hängt von den Daten ab, daher lasse ich das jetzt mal weg.Das Repository muss aber größer als der errechnete Wert sein:Ve
Thanks Rick, I will try this on Monday 😎👍🏼
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
