Blogs and podcasts
Bring your knowledge and expertise while creating blogs and podcasts
- 817 Topics
- 6,788 Comments
As promised part 2 of a 2-part topic regarding rotating USB disks 😉.But after writing this topic I had to devide it 2 separate parts because of the limitation of 50.000 characters 🤣😏 You can read the first part in OFFLINE backup copy using rotating USB disks – part 1 | Veeam Community Resource Hub As already mentioned in part 1, using rotated USB disks is a possible and affordable way to have an offline or airgapped backup copy. If you keep them offsite, the two times 1 of the golden 3-2-1-1-0 has been completed!In this part I will go a bit deeper in this topic.I will split it into 4 sections : LimitationsWhen using a repository with the rotating drive option, you have some limitations you have to keep in mind. Those are :On one managed server, you must create only one repository with rotated drives It is NOT possible to store archive full backups (GFS) with backup or backup copy jobs It is NOT possible to use per-VM backup files It is NOT possible to rescan the backup repository NF
During troubleshooting a backup environment, it’s common the necessity of test ports responsivity of our backup servers, like Veeam backup server, mount server, proxy or repositories.We normally do that with telnet. However, by default telnet client is not installed during Windows Server and the Veeam Backup Server often is our principal component our backup infrastructure.So, if you want to test some communication port without install telnet client, you can use PowerShell for it.Use the sintax below:Test-NetConnection -ComputerName <IP> -Port <port>Here is an example for the command:An interesting point is that if the communication port is not well succeeded, the utility make an aditional ping test:
Today I received a great surprise in my email from Madalina Cristil (@MadiCristil), the manager of the Veeam Community Legends program, and Rick Vanover (@rickvanover) that I was renewed into the 2022 second intake.You can find out about the Veeam Legends program on the Community Hub here - Veeam Community Hub.It has been a great first year in the Legends program, and I was happy to contribute to helping the community. I look forward to another year and meeting many of the Legends in person at the #Veeam100 event in October.There are some great benefits to being a Legend -As a part of Veeam Legends, you’ll be eligible for unique content, NFR licenses, private betas, prelaunch briefings, Veeam R&D insights and, of course, awesome Veeam Legends swag!But one of the most significant benefits is being part of a community to share knowledge, experience, tips, tricks, etc. I know this from already being in the Veeam Vanguard program for the past five years.So if you are interested, check
One of the things that we have in all our projects and backup environments are Backups Jobs.After deploying all components and servers on our Veeam infrastructure, the first thing that we do is the creation of our backup jobs.Thinking of that, I write this post telling you what is the main nomenclatures that I’ve been used on my Veeam Backup & Replication. B2D - Backup to DiskBackup jobs that we use to send data to any disk repository. B2T - Backup to TapeBackup jobs that we use to send data to tape libraries. B2C - Backup to CloudBackup jobs that we use to send data to cloud. On V11 we need a SOBR to send data to public cloud like AWS, Azure and GCP. However, if we have a Veeam Cloud Connect repository, we can send data to this kind of 'cloud' and use B2C name on backup job. BC - Backup CopyBackup copy jobs we often use to make one or more copies of data between repositories or sites. LTR - Longe Term RetentionBackup copy jobs we can have to attend a long-term retention on data ar
Scenario:Very recently a customer asked me if Veeam could leverage Data Domain mtree replica for DR purposes.Of course, the answer is YES! While this idea is not new, I thought it would be a good reminder of Veeam’s backup import capabilities. Steps:You must use Data Domain repository on the source site. It most likely will be declared as a DDboost share. The mtree should be replicated to the DR site. Note that the mtree replica will be Read Only! The mtree replica needs to be exposed as a share over your protocol of choice (CIFS, DDboost), so it can be defined in the DR VBR server. In this example, I chose DDboost.Note again that this DDboost share is Read Only! The last step is to declare that DR DDboost share and import backups You should now be able to access these backups from the “Disk (Imported)” section. Remember that you will have to manually rescan that repository in order to refresh new “mtree replicated” restore points.
As a system consultant I often implement solutions for customers in the SMB market.Working for the SMB market is often more challenging than working for the enterprise market because of the limited financial budget/investment. I always try to deliver a solution that is as good and secure as for customers of the enterprise market but of course with other and cheaper solutions 😉. Of course VEEAM is always being used as the software defined backup solution 😊. For me personally the golden 3-2-1-1-0 rule is one of the most important things to keep in mind when creating a good backup solution for the customer.More info about that you can read in one of my first posts : 3-2-1-1-0 Golden Backup Rule | Veeam Community Resource Hub In this post (part 1 of 2 parts) I explain a bit more about implementing the second 1 in the rule – offline backup.One of the solutions is using rotating USB disks.This is specifically for backups of VMs and/or backups using agents of physical/cloud objects.In part
Just two weeks after the release of Veeam 365 version 6a, Veeam has released the first cumulative patch P20220825 (build 188.8.131.52). This patch fixes two issues which have been discovered in the 6a GA release. While, according to Veeam, those issues only affect less then 1% of the v6a users, it’s still recommended to install the patch. A backup of Security groups, Distribution groups, M365 groups, and specific users may complete with the warning: Nothing to process When this occurs no restore point is created for such objects.Note: Depending on the job configuration, the job may complete with a Success status, and the problem may occur unseen Under certain conditions, a backup job that includes SharePoint, OneDrive, or Microsoft Teams objects may run longer than expected, and the processing of lists may complete with the warning: Failed to analyze list changes. Value does not fall within the expected range. For more information and to download the patch, visit the following KB: https:
Hello guys 😄Hope everyone are well ! In my side I'm in vacation 🤙. I wanted to share with you some tests done with the beta of Veeam v12 (build 184.108.40.2067) and the incredible new feature backup directly to Object Storage.Object StorageFor my test I used Wasabi as cloud object storage. You can find really great posts about Wasabi:Wasabi is now available in the list of providers when you want to add an object storage repositoryWe have less information to enter, it's appreciable You will find your repository with Wasabi Cloud Storage Type. Backup JobThe advantages of this kind of backup are multiple:Financial: you can use on-prem object storage, object storage can be cheaper than SAN Built-in durability & reliability Reduce hardware to manageLet's take a look at the setup, because there are technical side effects.As usual you select your repository, the GFS part still available and you could configure a backup copy job if necessaryIn the advanced options, it’s simplified ! Bye backu
Recently I needed to restore a SAP Oracle Database and I received this error below: After open a ticket with Veeam support I discover that this error has relation with SAP Oracle Databases specifically. The solution was a fix on Veeam Explorer for Oracle. After applying it my restore ran successfully.However, it doesn't have a public KB about this error and only support Veeam has access for this fix.So, if any of you get this kind of error, I recommend open a ticket with Veeam to solve your problem as soon as possible.
Protecting DB2 servers with Veeam Backup and Replication is pretty straightforward. The IBM DB2 can be protected with the following Veeam jobs:Classic VM backup jobs Veeam Agent for Linux (VAL) jobs Enhanced NAS backup jobsTo ensure that the DB2 DBs are in a consistent state, IBM DB2 commands will need to be called to either create a native DB2 database backup or to put database(s) in a quiesced state so that a clean application backup of the database can be made. DB2 has several ways to perform backups from the CLI that make backups of the database reasonably simple.Native flat file backup can be performed against an offline or online DB. The options include using full, incremental, and differential backups A simple pause and resume of the DB2 writer that can be used to store (and VMware) snapshots that Veeam Backup and Replication can leverage. The ability to leverage storage array snapshots as restore points through a component called IBM DB2 ACS. I will not discuss this process as
I case you haven’t seen. There are currently two ongoing surveys from Veeam; one about the Help Center and the documentations, the other one about the livestreams (Industry Insights, TechBytes). So in case you want to share some feedback on those topics, here’s your chance:Veeam Help Center: https://www.surveymonkey.com/r/JFBXD2HVeeam Livestreams: https://www.surveymonkey.com/r/VeeamStream22A Sources:https://forums.veeam.com/post461204.html#p461204
So part one of the Veeam Backup for Microsoft 365 discusses the shared responsibility model and outlines both Microsoft and Customer responsibilities. I also took at why you need to backup briefly but will dive more into this for part two. You can find resource links and part one here - Part 1 When it comes to backing up your Microsoft 365 data, there are seven reasons why you NEED to back it up -Accidental deletion: This is actually the most common cause of data loss in Microsoft 65. If you delete a user, whether you meant to or not, that deletion will then be replicated across the netw rk. A backup could restore that user, either to on-premises Exchange or Microsoft 365. Retention policy gaps and confusion: Retention policies in Microsoft 365 are designed to help organizations comply with regulations, laws and internal policies that require that they retain or delete content; they are not back ps. But even if you do rely on your retention policy in place of a backup, these retention
Some of you may have noticed a certificate validation error when using the Automatic Update function in the Veeam Backup for Microsoft 365 console. The error is due to a certificate expiring (which is needed to validate server updates). There is no cause for concern; the certificate was not compromised, and the option to manually patch the server was not interrupted. This certificate has since been updated, but a manual patch is needed to get the new certificate for validation. For those who want the quick fix, head over to KB4341. The rest of this article will cover some good-to-know information about certificates and some lessons learned.What is PKIWe commonly hear the term “certificates” with applications or websites and understand this is generally associated with security but may not understand what role certificates play. To start, let's talk about what a certificate is. A digital certificate is used to initiate an information exchange in two major parts; first, by saying, “ you
For this blog series, I will look at M365, which many people use daily, and why it is necessary to have backups using the Veeam Backup for Microsoft 365. Now my approach will be coming not from a typical user perspective but from an MSP (Managed Service Provider) perspective. I will start part one of this series by going through the shared responsibility model for Microsoft 365 and how Veeam plays a key role there. As we progress through the series, I will talk more about the installation of Veeam for Microsoft 365 and other best practices. Shared Responsibility ModelThe shared responsibility model regarding your data relates to what Microsoft is responsible for and what you as the end-user are responsible for in protecting your data. Many thought that Microsoft did backups for your data, and that assumption could not be farther from the truth. When your data resides in Microsoft 365 as the end-user, you are responsible for backing up your data.What is explicitly each party respo
Veeam have today released the long-awaited update to Veeam Backup for Microsoft 365 (VB365), v6a.This release has been overshadowed by Microsoft’s controversial changes being made to the Teams backup process, forcing vendors such as Veeam to cease using EWS as a mechanism to backup Teams data, instead insisting on the use of the Teams Graph API. Why is this controversial? Because the Teams Graph API is billable per query. You can read more about this in my full blog post here.There are two key notes I’d like to highlight on this v6a release: Permissions Changelog Veeam are now including a permissions changelog for the Azure AD Application, vs the v6 release. This contains any newly required permissions, changed permissions or removed permissions, as well as describing the usage of these permissions. This is available within the v6a release notes, available here. Alt Text: Image displaying the permissions tables within the release notes Microsoft Teams API will NOT be enabled by default
When auditors come knocking—or worse, when bad actors strike—not having accurate and complete event logs can make all the difference in how your organization survives the encounter.However, users are often understandably more focused on day-to-day operations and only think to look for this information once it’s needed (and when time is of the essence).The good news is that all the information you need—including where to find changes in Veeam server user access permissions, failed login attempts, and failed RDP connections—is available in several different locations, including:Windows Event Viewer Veeam Backup and Replication Audit logs for performed restores Veeam One Audit log The individual application log(s) Windows Event ViewerMany Veeam activities (success, warning, and failures) get logged to the Windows Event viewer by default. To see these events from within the Veeam Backup and Replication (VBR) server, open the Windows Event Viewer console and Migrate to the Veeam Backup node
You might or might not know this, but Wasabi does have a minimum storage duration policy in place.What's that?Depending on your pricing model, each uploaded object will be billed for a minimum amount of time.Pay-as-you-go customers have 90 days, reserved capacity customers (pre-paid) will have 30 days.If you delete an object before this minimum duration is over, the remaining time will still be charged.You can find more information on this website:https://wasabi-support.zendesk.com/hc/en-us/articles/360058734492-How-does-Wasabi-s-minimum-storage-duration-policy-work-ExampleYou upload 1TB of objects to Wasabi and have the 90 days minimum storage duration policy in place. After a week you decide to delete the whole 1TB.This means you pay for:7 days timed active storage 83 days timed deleted storageCan I recover deleted objects?You might think, that as you pay for deleted objects, you may be able to recover those. Unfortunately this is not the case, so you can’t use this as a recycle bin.
SureBackup is a really great feature to verify your backup data. Up to now the selection of VMs to verify within a single job was limited. For example it was not possible to mix physical with virtual machines. There seems to be something new in v12 beta! With beta it is possible to add agent backup machines to virtual machines into the same Application Group and as Linked Jobs too.
Quite a cool new feature is the ability to enable Multi-factor authentication (MFA) for the VBR console login. With this a user has to enter username, password and an additional confirmation code that comes from a Authenticator app like Google Authenticator.At first login, User can add VBR to his Authenticator app.It is really simple to use.BUT: 2FA works only for VBR console, NOT for PowerShell!Another security improvement is the option for Automatic Session logoff:
After watching last week’s Community Recap, I realized that I missed a great blog posting from @regnor about setting up Wasabi Immutable Storage for VBR. After reading this information, I realized that I, as a smaller service provider and MSP, require a more complex configuration to host multiple tenants in Wasabi and was inspired to share my configuration for setting up Wasabi when you have multiple tenants under one account that you don’t have to have accessing each others buckets.The magic lies in some S3 IAM policy work in place to prevent buckets from being visible and accessible to the wrong tenants. When I was setting this up, there wasn’t much information for doing exactly and S3 policies were completely new to me. Using Wasabi’s and Veeam’s instructions in the links and the end of this post didn’t work for me out of the box, so after asking around in the Veeam Community, R&D Forums and Veeam Subreddit and some experimentation, I was lead to the answers I needed. I hope
VMware has announced on August 3rd that vSphere ESXi 7.x is the last version supporting Apple Mac platform.https://kb.vmware.com/s/article/88698Reasom is that Apple is moving away from the x86 processor platform.With 7.0 the MacOS platform will be supported until EOL. Guest OS support for Mac is discontinued, too. macOS guest operating system may only be operated in VMs on vSphere ESXi hosts installed on Apple Mac hardwarehttps://kb.vmware.com/s/article/2015161
With v12 it will be supported to use group Managed Service Account (gMSA) for user credentials.For my understanding of gMSA it will be necessary to have VBR server in a domain. Because it will still not be recommended to join this server the production domain, a special resource or management domain could be needed. For more details we will have to wait for general availability to get the user guide.If you have more ideas about gMSA implementation, let us know 😀
Inspired by @Geoff Burke‘s post about immutability for Kasten with Wasabi, I decided to post the same for Veeam Backup & Replication. If you want to check out Geoff’s post, then follow this link:What/who is Wasabi?Probably Wasabi doesn’t need to be introduced. But if you can only think about the paste you get with Sushi, then you should check out their cloud object storage. Besides AWS and Microsoft, Wasabi is one of the Vendors, who often gets recommended for usage with Veeam Backup. The reason for that is their really competitive pricing, combined with great functionality/quality and low complexity.How to create an immutable bucketAfter registering an account with Wasabi, the creation of an immutable bucket isn’t complicated at all.Just make sure that you select the right region for your location, and also enable bucket versioning and object locking.Afterwards you need to create an access key. For testing purposes you can use the root account key, but for production you should cr
Login to the community
Log in with your Veeam account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.