VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Just read a post about Apple Time Capsule. According to a german data-rescue company there seems to be a design-fault of used HDDs. This fault may lead to mass extinction because of hardware damage. Affected devices Time Capsule devices of the 5th generation:2TB ME177Z / A with Seagate Grenada ST2000Dm001 3TB ME182Z / A with Seagate Grenada ST3000DM001Recommendation: Safe your Time Capsule data Maybe switch to Veeam Mac Agent Here is the translated article:https://translate.google.com/translate?hl=en&sl=de&tl=en&u=https%3A%2F%2Fwww.030-datenrettung.de%2Fapple-airport-time-capsule-aufall-droht.htmlHere is the original (in german) article. Here you also see good pictures for illustrating the possible damage:https://www.030-datenrettung.de/apple-airport-time-capsule-aufall-droht.html Hope this helps to avoid backup data loss!
I spent some time in testing a new great feature in v11: Hardened Repository. Read here about:What is immutability is about Requirements Setup How it works What is immutability is aboutImmutability in this context means, a backup file cannot be changed or deleted without having root access within hosing Linux OS. So, even the backup administrator is not able to delete backups on such a repository.Why is this important? Think about ransomware. This software is that smart these days, it is able to recognize backup systems. It can trigger tasks like deletion of backup files. But when they are immutable, this cannot be done! RequirementsWhat is needed to get immutable backups? First of all: Veeam Backup&Replication v11. This is the first version supporting hardened repositories. Secondly a Linux server hosting repository volumes.What about the filesystem? Veeam is using immutable flag. So every filesystem supporting this flag can be used. These are pretty much all. Veeam supports refli
Some time ago I posted a new feature in v10 PowerShell Plugin. With it it is possible to set - next to others - higher timeouts for boot and application initialization for SureBackup application groups. Here I want to show how to implement:Set your preferred option, see example here:$Startup = New-VBRSureBackupStartupOptions -AllocatedMemory 100 -EnableVMHeartbeatCheck:$true -EnableVMPingCheck:$false -MaximumBootTime 1000 -ApplicationInitializationTimeout 1000Select the job(s) you want add VM to SureBackup from. Sure this can be in one line, but this is to show each step:$VBRJob = Get-VBRJob -Name "Backup Job"$VBRVMs = Get-VBRJobObject -Job $VBRJobNow, build an array of backup-VM with the correct object-type (CObjectInJob):$VSBVMs = @()$VBRVMs | foreach {$VSBVMs += New-VBRSureBackupVM -VM $_ -StartupOptions $Startup}Note: Backup job must have run at least once. Otherwise you the the error:New-VBRSureBackupVM : Object reference not set to an instance of an object. Finally, create your a
Veeam released Cumulative Patch for VBR v11!https://www.veeam.com/kb4126
Veeam just released a comix book! Download it here:https://go.veeam.com/wp-choose-your-cloud-adventure-aws
Just read the news and thought it would be interesting in the community: HPE to acquire cloud disaster recovery startup Zerto What do you think about it?
Hallo Veeam Gemeinschaft!Willkommen zum österreichischen VeeamON Tour Diskussionsforum! Dieses Forum ist für alles da, was Ihr über die VeeamON Tour mitteilen wollt!Welche Sessions sind Eure Favoriten? Wo habt Ihr am meisten gelernt? Was ist/war das absolute Highlight? Wurden Eure Erwartungen erfüllt? …Einfach Comment erfassen und Send !
Backups of VMware vSphere VMs can be done with one of three transport modes. Each of these modes also provide the possibility to restore data. This post is about 3 reasons why direct SAN restore failover to NBD. Incorrect VMDK typeVeeam can only perform direct SAN restore with thick provisioned VMDKs. If any disk of a VM is thin provisioned, restore will not leverage SAN directly. Both, thick eager and lazy zeroed are supported. In my experience, eager zeroed is much faster from a restore point of view! So I recommend, to use this format.Note: you should not rely on the provisioning type you chose at VMDK creation: Thick provisioned disk can become thin if it is expanded.Fortunately, Veeam provides the possibility to change disk type in restore wizard. So you can be sure to use thick VMDKs when you enter this within the wizard. See here in Full VM Restore wizard:And in Virtual Disk Restore wizard: Disk is logically locked in Veeam proxyIf your Veeam proxy server is Windows based, it
Hallo zusammen!Am nächsten Donnerstag findet die Mini-VeeamON in unserer DACH-Region statt. Dazu ein paar Details:Das Event läuft von 10 bis 15 Uhr und ist damit zeitlich sehr überschaubar. Interessante Agenda: https://go.veeam.com/veeamon-tour-online-de#agenda Es wird etwas Action in unserer VUG AT Gruppe geben: Stay tuned!Meldet euch an:https://go.veeam.com/veeamon-tour-online-de
Hallo!Wir freuen uns sehr, Euch zum ersten VUG AT&DE „german-speaking“ Event einladen zu dürfen! Ironischer-weise wird gerade dabei englisch gesprochen werden . Grund dafür ist die Teilnahme des Mr. VMCE Rasmus Haslund @haslund . Wie unschwer zu erraten, steht die VMCE Zertifizierung im Fokus dieser Session.Links:Event-Beschreibung von @falkob: Umfrage zum persönlichen Trainingsstatus. Soll Rasmus dabei helfen, die Session optimal vorzubereiten.Info: Anmeldung ist auch möglich, ohne Miglieder der VUG Germany zu sein.Wir freuen uns auf eine interessante, interaktive und spannende Veranstaltung!
For this post I planed to share some time and bandwidth comparison for backups in my lab. But it is some kind of difficult to get representative data in a fully virtualized demo environment.So I am very happy @Gostev pointed out this topic in his last Words from Gostev (Veeam R&D Forums Digest) from 8.2.2021. If you are not subscribed to this newsletter: do so! https://forums.veeam.com/I want to summarize important facts here:Backup performance per appliance (all-in-one box) doubles in v11. Revise and optimize basics: How are backup files written to disk. Shared memory transport engine, when source- and target-datamover on same box. Implemented full NUMA awareness Enhance the data movers placement logic to ensure they never end up on different CPUs. All this, and I assume much more, leads to an incredible performance. Veeam tested with an HPE Apollo 4510 Gen 10 Server – which is really a perfect backup target – as a all-in-one appliance. Veeam was able to peak at 11.4 GB/s (!) b
If you do no know much about Hardened Repository in Veeam VBR v11, read here to learn more about:I was asked, if a hardened repository can be a extent of a Scale Out Repository (SOBR). Good news: yes it can! But you have to take some facts into account.Hardened repositories can be Performance Tiers of SOBR. A SOBR can contain a mix of repositories: ReFS, XFS, Immutable and mutable. Even in mixed SOBR, Performance Placement Policy can be set. That leads to, for example, immutable increments and mutable fulls. When you mix, for example, ReFS with immutable extents, you can use Evacuate backups to free an extent. I would not recommend any points 1 - 3!In my opinion the point 4 is the most important. With evacuating an extent you can easily migrate from ReFS to XFS with immutability.Notice: If you evacuate an immutable repository, Veeam performs a copy, not a move operation! Which makes perfect sense! When backups are evacuated to a hardened repository, files will be immutable as long as
I want to share a blog post by John Nicholson (VMware - not the guy from Shining !) which is about VMware Backup Myths. If you are in a backup related job, it could be funny to read. I did not know some of them!https://thenicholson.com/backup-myths/My favorites are:Virtual machine backups are not useful for file, or app level recovery. Agent-based backups are “lighter-weight” than hypervisor-assisted backups. Network based backups will bottleneck on the vCenter. Snapshots Suck. Here you have to read details in post! Enjoy reading!
@Gostev mentioned some data loss issues in conjunction with VMware Tools quiescence in his current “the word from Gostev”. This method is used, when Veeam application-aware processing is not enabled ...… but “VMware Tools quiescence” is.Also because of such issues, Veeam recommends using their application-aware backup.So I want to ask the community, which backup method for application awareness do you use for Windows vSphere-VMs:Veeam application-aware processing VMware Tools quiescence.I personally try to implement Veeam processing whenever possible (security, network,...). At least for AD, SQL-based applications, Exchange, ...
The following post is not directly related to backup. I hope it is helpful anyway.At a customers backup server a very strange behavior was observed. After a few days without problems, scheduled tasks never seem to get finished. So a current running – never ending – task prevents the next run from starting. A reboot of the server resolved the problem – for a few days.SolutionAfter a research I found out, scheduled tasks get started with a lower priority than interactively started tasks. See my scheduled PowerShell script in screenshot here.Normally this is not a big deal. It does not matter when tasks like reports last longer than manually started. Nevertheless they should at least finish.The solution is to rise the priority of scheduled tasks. Unfortunately this cannot simply be set in the GUI. It can be done in a few steps, I list here.Start Windows Task Scheduler, right-click your task and select Export… and save XML file to a temporary location. Edit XML file with an editor of your
It is not uncommon to reset root password in VMware VCSA (vCenter Service Appliance). This can be necessary when account is locked or password is expired. Normally, you have to shut it down, enter GRUB and edit start parameter to boot into bash. There you can reset root password. Afterwards you boot VM again. Here is the link to this procedere: https://kb.vmware.com/s/article/2147144With vCenter 6.7 U1 it us much easier! Since then it is possible to use a Single-Sign On (SSO) administrator account (for example: administrator@vsphere.local) to login to Appliance Interface (Port 5480) and shell. And exactly this can be used to reset the root password. In short it goes like this: Take a snapshot/backup of VCSA - it is always a good idea to start with a backup Login as a SSO-administrator using a SSH client or console. Enable and start shell: shell.set --enable true shell Change root password sudo passwd root DoneHere is the link to the more detailed VMware KB-article: https:/
See here how it works in a step by step guide.To start in Instant SQL Recovery wizard, select your server and choose Restore application items.Here you choose if you want to restore to the latest available restore point, or select a listed one. At the end of wizard press Browse. Veeam Explorer for Microsoft SQL Server starts.Choose the database you want instantly recovered and select to do so. You have these options to choose from: Latest restore point. Point-in-time state. Recover to another server. This you can used to recover DB using a different name while original DB is still in place. In this demo, I selected point-in-time state to show additional options.Select point-in-time state you want recover to.Notice:First option recovers to date and time, recovery point was created. Second option lets you choose the exact date and time to restore to. As noted, transaction log backup is required here. Checking option to restore to a specific transaction, lets you choose a marked tran
Hallo!Wie haben nun einen Termin für das nächste Veeam Group User Meeting – Sorry für die Verspätung! Bitte reserviert euch den: Dienstag, 11.5.2021 von 15 – 17 Uhrin eurem Kalender! Wir erarbeiten noch die Agenda. Es gibt also noch für jede/jeden die Chance, vortragend am Meeting teilzunehmen. Falls Interesse dazu besteht, bitte hier posten, oder mit Nachricht direkt an mich oder @Fred_vBrain. Würde uns freuen, wenn sich tatsächliche User zu Wort melden.
Probably the following is widely known. But I did not know up to now and found out today. Maybe it is new for others too.After the Upgrade to v10, suddenly Linux VMs are not getting backed up any more, because defined guest interaction user was domain-based and could therefore not login into Linux VM. So solution would simply be to disable guest processing for this VM. Problem was, VMs were selected by vSphere Tags for this job. Fortunately solution is quite simple:Edit the job and got to Guest Processing and click Application Here you can see the selected vSphere Tag. When you edit this line, options are set for all VMs this Tag was assigned to. Press Add → VMs and Tags → expand Tag of choice → select exception VM Select new line and press Edit Set option as desired for this/these VM(s) That's it! This also works for custom Guest OS Credentials: BTW: If you suffer from the same behavior after upgrading to v10 (and probably to v11 as well): Curiously this is not a bug, it is a bu
This is the second part of my SQL Instant Recovery posts. First part:I would like to list some of the software’s behaviors here.Veeam Explorer for Microsoft SQL Server is closed. One could gain the impression from the documentation Veeam Explorer does the whole work. This is not the case, if Explorer gets closed, just start it again. Mount Server, proxy or repository Server is offline. This is a problem, because these components are necessary for keeping your Instant Recovery database alive. Fortunately Veeam took this into account. So the system checks periodically (every 5 minutes) if needed components are online again and re-establish all connections. If you fixed the problem before next scheduled retry, you can trigger the retry manually by pressing the Retry button.Restoring to original locating with original database still in place. The Explorer wants to have your decision confirmed. Veeam VBR Server uses older SQL Server version than source Server. This is generally not a proble
Wieder ein Hinweis auf eine Veeam Veranstaltung, die auch für euch interessant sein könnte.Es handelt sich um einen Gruppen-Chat. Das Event wurde von Veeam UK and Irland organisiert. Podiumsteilnehmer sind ua.: Michael Cade (Veeam, @michaelcade ) , Jorge de la Cruz (Veeam, @jorge.delacruz ), Michael Paul (Veeam Legend, @MicoolPaul ) und meine Wenigkeit. Die Veranstaltung ist heute um 15 Uhr und mit diesem Link erreichbar:https://www.crowdchat.net/veeamv11 Würde mich freuen, den Einen oder Anderen dort zu „sehen“!
As you probably have already noticed:VMware released vSphere 7.0 U2 recently This is currently not supported by Veeam. I want to share some important news for this new version that is relevant to backup. See this link for the complete list of core storage improvements:https://blogs.vmware.com/virtualblocks/2021/03/09/vsphere-7-u2-core-storage VMFS SESparse Snapshot Improvements Read performance will be improved by redirecting reads to where data is located (chain or base-disk). Up to now, reads go through the whole snapshot chain and the base-disk. So when you read not-changed data, systems reads from base-disk directly, instead of checking snapshot chain as well. Performance Improvements on VMFSImproved write performance on thin provisioned disks. This is about first writes. It should reduce the potential effects of first writes when using thin-provisioned disks. NFS Improvements I am not very experienced with NFS in vSphere, so this is the improvement:With the release of vSphere 7.0
As we discussed here earlier, there are 3 transport modes to get data from vSphere for backup.These modes are also available for restore. By default, first mode (order: SAN, Hotadd, NBD) that meet requirements, is selected for restore. For SAN direct mode, a requirement is thick provisioned disk type. You can select each available type (thin, thick eager and lazy zeroed) in restore wizard.My recommendation: If you want to leverage SAN direct mode, choose Thick eager zeroed! This option is much faster than lazy zeroed!I tested these settings in different environments. For example, I saw differences of67 % (150MB/sec for eager vs. 100MB/sec for lazy), 93 % (226MB/sec for eager vs. 16MB/sec for lazy). See here different wizardsVM restore VM Disk restore Interesting LinksIn documentation of version 9.0, you see a hint, for lazy zeroed, vCenter is needed for zeroing.https://helpcenter.veeam.com/backup/vsphere/direct_san_access_writing.html Since v9.5 no difference is made anymore bet
It is new in v11, but I do not have much detailed information about it.When you create or edit a backup job, you can enable High priority.The idea is to use this option to make clear this is an important job. So it can be started before less important jobs are started. It is not about job performance, it is about start time. Makes perfect sense to me! Under certain circumstances this feature will make job scheduling easier.At first this seems to be available for Backup and Replication jobs.
Hallo! Zugegeben wieder sehr knapp, aber heute findet ein österreichisches VMware User Group Meeting statt! Die Sprecher sind quasi die Pop-Stars der VMware Community!Frank Denneman Ducan Epping Cormac HoganWenn Interesse besteht, bitte kurz melden, ich leite gerne die Anmeldedaten weiter!
Already have an account? Login
Enter your username or 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.
