Join discussions around Veeam community projects, Veeam events, industry and technology news
- 872 Topics
- 8,820 Comments
Hey All, Our Synology no longer supports NTLMv1 which is causing the Veeam SMB Repo to disconnect. Anyone know of a way to set the SMB level in Veeam to 2 or higher minimum? Thanks. User [veeam] from [IP address] failed to log in via [SMB] due to [NTLMv1 not permitted].
Good day, I am new to veeam and just installed veeam backup and replication 220.127.116.111. when i connect to the server i am getting the error which reads “Failed to connect to Veeam Backup & Replication server: Remoting Channel Sink UriNotPublished. RequestUri is ‘/VeeamClientUpdateService’” Can you advise what could cause this problem Kind regardsSibusiso
Because of the new v11-feature of immutable backups on XFS filesystem, I am looking for real-world experiences with XFS as Repository.I just read through this forum entry:https://forums.veeam.com/veeam-backup-replication-f2/v10-xfs-all-there-is-to-know-t65222-30.htmland the closing experience of user ferrus:https://forums.veeam.com/veeam-backup-replication-f2/v10-xfs-all-there-is-to-know-t65222-30.html#p388579 Sounds very good to me so far. I can remember first implementations of ReFS Block Cloning. Lets say, it does not work that fine at the beginning.Would you share some of your experiences with XFS as Veeam Repository? I would be interested in:stability performance (over time) needs for troubleshooting administrative effortThanks!
Hello, We have a Veeam Backup O365 18.104.22.168 with a new backup job created two weeks ago, only for Mail and Archive. I think that the performance is too slow, the processing rate is 5.4MB/s, bottleneck: source, read rate 3.9MB/s and write rate 5.8MB/s. Is that normal? Our bandwidth to Internet is 280Mbps (35MB/s), download and upload,how can I troubleshooting this problem? Thanks in advance, Omar De Souza.
I know there is a related topic with the same problem but that one is for version 5.0.0 There is a known problem with Windows 11 and the installation of Microsoft SQL Server where the engine will not install unless it is installed on a different drive or VHD.I understand Veeam Agent for Windows uses SQL Server technology which is probably why it fails to install.Question 1: Is Veeam working on a solution independent of Microsoft?Question 2: I installed SQL Server 2019 Express with support for local DB but Veeam Agent for Windows still fails. Is there any way to have Veeam use the existing (operational) engine instead of attempting to install its own SQL engine? I read somewhere that they are using SQL 2012 but I haven’t tried preinstalling that version.Question 3: Is there any way to trick Veeam into installing on a different drive?I use Veeam at work and have been pretty happy with this product for home use. I already temporarily installed another backup solution but would love to go
Hello All,I have a VM on standalone Hyper-v 2019 with a backup checkpoint that I can not delete.The checkpoint was created by veeam during backup.There is no opting in the GUI to manually delete the checkpoint.I ran the backup again and it was succesfull however it did not delete the checkpoint.What can I do? the checkpoint is growing quite rapidlly.Version: Veeam Backup 10a Build: 10.0.1.4854 P20201202
Today I’ve discovered an interesting blog article about the VMware vCenter Converter. Apparently VMware has removed it from the Downloads, so it’s no longer available for the public. The reasons for this is, that there hasn’t been any development in the last years and it already went end of support in Decemter 2019 (!), which I didn’t know.VMware is working on a new release of the Converter and it will be exciting to see how the next release will look like and what it’s capable of.Here’s the blog post for reference: https://blogs.vmware.com/vsphere/2022/02/vcenter-converter-unavailable-for-download.htmlWhile the vCenter Converter was a great piece of software which I’ve used many times in my IT career, I haven’t used it since some time. The last times I had to convert physical systems or VMs to a different Hypervisor, I’ve had the luck that those customers were using Veeam. So instead of relying on the Converter or a different 3rd party tool, I restored the system with Veeam. This work
I am currently trying to upgrade to version 11 . The first upgrade failed with an error as it could not start the services. I followed this fixhttps://community.veeam.com/blogs-and-podcasts-57/failed-to-connect-to-veeam-backup-and-replication-server-how-to-fix-remote-channel-sink-urinotpublished-remote-connection-refused-and-failed-to-start-the-service-1263 I am now having to repair the installation as the fixes did not work and the services would not start. I have just tried to run the repair and I am receiving a different error "veeam configuration database is in use by the backup server " I have no idea how to proceed.
A bad bug was found in VMware vSphere 7 U3. A ESXi host may crashes with a PSOD when running thin-provisioned VMDKs. Currently there is not solution available. There are a few workarounds but no easy ones:Downgrade to older version, Convert all VMs (VMDKs) to Thick-provisioned, Disable TRIM/UNMAP in Guest OS.For more information see official VMware KB: https://firstname.lastname@example.org already posed about the issue: https://jorgedelacruz.uk/2021/10/22/vmware-psod-after-updating-to-vsphere-esxi-7-0-update-3-panic-requested-by-another-pcpu-thin-provisioned-vms/Maybe good news: U3a is already announced: https://blogs.vmware.com/vsphere/2021/10/vsphere-update-3a.html
I have just discovered on Twitter that there’s currently a problem with Teams Backup in Veeam Backup for Office 365 which could affect many installations.It looks like Microsoft did change something on their side and so Teams backup is failing with the following error: “Object reference not set to an instance of an object”If you are affected by this problem, you can request the hotfix from Veeam Support.Here is the corresponding R&D forums topic: https://forums.veeam.com/veeam-backup-for-office-365-f47/teams-backup-failing-with-object-reference-not-set-to-an-instance-of-an-object-t76162.html
For those who don’t go to the VMware forums (another ‘communities’ based vendor website) often, there was finally a VMware employee who somewhat unofficially acknowledged the issue of running ESXi on SD cards, specifically with vSphere 7U2. I say U2 because v7 and v7U1c, of which I both have run on DELL IDSDMs, runs flawlessly; and has for the past year.To read a little more on the issue, you can review the VMware Communities post here. The issue, it seems, has to do with their newly formatted boot partitions. But honestly, I think the mishap (Hosts disconnecting/hanging) is mostly due to a new vmkusb driver. VMW is currently working on a fix, though they’re really recommending orgs to start using ‘high-performance’ storage (i.e. disks) for the boot device moving forward. All that to say is, if you haven’t upgrade to 7U2, I recommend not to. If you’re running your boot on disk, I think you’ll be fine. Otherwise, hold off. One of the Veeam Vanguards, Luciano Patrao, did a nice little p
Hi,I’d be interested in getting feedback from people that are already using HPE Apollo’s or other high density servers with local storage as repository server. It seems that a lot of people are currently planning to use them.what is you setup? Number of servers? Number of disks? Which type and size of RAID? Number of VM’s / source data how is your performance? do you use them only as backup target or as copy source as well? which filesystem ReFS/XFS with blockcloning/reflink
Hi Veeam Community, Now it’s time to have a serious conversation, as they are BACKKK!VeeamON 2021 Update is your chance to step up your modern data protection AND your sneaker game. We’re giving away custom Veeam sneakers and YOU have a chance to win!Follow these simple rules: Register for VeeamON 2021 Update Share photo of you wearing your current kicks in the comments of this post Let us know WHY you need a veeamazing upgrade The nastiest sneakers you got the better. We need a SERIOUS reason for upgrade. Let us laugh together!Make sure to join us on Oct. 13 or Oct. 14 where we’ll announce the eight winners.The contest is open now through October 6th. For more details, visit: https://bddy.me/3D1wrVT
VMware vSphere 7.0 U3c is released today, this version can resolve some critical issues. Please check the followings.For Log4j issue on vCenter 7.0, vCenter 7.0 U3c can resolve this issue.https://www.vmware.com/security/advisories/VMSA-2021-0028.html vSphere 7.0 Update 3 Critical Known Issueshttps://kb.vmware.com/s/article/86287
Hello, I have been asked by one of Veeam partners about my take if it comes to Veeam support for VMware Horizon VDI platform, despite the choice of taking the POC option I also chose to take your input on this. Considering that VMware Horizon VDI is based on ESXi, do we still consider the desktops(Instances) or sockets as unit of licensing? If so, is there any operational implication or/and limitation if it comes to operations and protection of the VMware Horizon components? Just to mention I was able to get this old article (posted 2011) but with many Veeam versions since then I decided not to fully reference ithttps://forums.veeam.com/vmware-vsphere-f24/vmware-view-best-practices-backing-up-vdi-server-clients-t6517.html
Just a quick info:It looks like there’s currently an issue with the mailbox backup in Veeam Backup for Office 365, which could randomly happen for a small amount of mailboxes.Processing mailbox XYZ failed with error: Failed to synchronize item changes in folder: TeamsMessagesData.. An internal server error occurred. The operation failed., ICS synchronization failed.The backup for most of the mailboxes is successful, but some can fail with the error message above.Veeam is aware of this problem; they’re already working on it and are also in contact with Microsoft. For further information you can also monitor this R&D forums post: https://forums.veeam.com/veeam-backup-for-office-365-f47/failed-to-synchronize-item-changes-in-folder-teamsmessagesdata-t77925.htmlI will update this post as soon as there’s something new.Update:Veeam has implemented a workaround for this issue with the following patch: https://www.veeam.com/kb4235
Hi Folks, Just wanted to share my opinion on this. I was around when Cloud Connect was introduced and remember the struggle with customers when explaining backup copy job copy intervals. Often I would hear.. “can we not just have our legacy, backup job done then offsite?”. Veeam brought in the immediate copy not to long ago and I have already noticed some issues. When you leveraged periodic BC jobs you could set the copy interval differently for tenants with different quality bandwidth. I could be wrong but with Immediate copy if it gets behind it will copy one day, then right away try the next in order to catch up. If you have many backup copy jobs and only so many concurrent connections available this then becomes an issue. I prefer periodic copy, I can say to the tenant, yes we will get your backup copy jobs over the wire but with your current bandwidth we need 3 days… then it is up to them to increase bandwidth.
Morning all, For anyone that missed the news story, Kaseya have been the latest victim in the increasingly dangerous threat of supply chain attacks.Who are Kaseya? Kaseya offer a remote management system primarily aimed at Managed Service Providers (MSPs). MSPs use tools like this to automate patching and monitoring of systems and can automate deployments via reusable scripts that can be targeted at one or more devices.By the very nature of this software it is designed to run with elevated privileges.Cyber Criminals found a vulnerability with the Kaseya VSA platform and have used it to deploy ransomware to systems.Full details can be found here: https://helpdesk.kaseya.com/hc/en-gb/articles/4403440684689The ransomware used is a variant of REvil and has been known to target backup systemsWith this background information out the way, many in the infosec community have been debating the best defence against these kinds of threats and one suggestion posed had me interested. These platforms
I’m currently running the 30-day trial version of Office 365 backup (22.214.171.124) and everything has been running well for the last 10 days or so. I have the software set up to run every 8 hours for a whole organization backup. Out of the blue, last night, the backups started failing with “Access denied. The remote server returned an error: (403) Forbidden”The admin password is the same and Azure AD shows the login for the Veeam account as successful. I’ve checked our Office 365 Health panel and see nothing new that might impact the backups. I’m running a backup to a local repository and have rebooted the backup server and the proxy server. I have plenty (4.8+ TB’s) of storage available on the repository. I went into the Organization setup and reentered the credential info and all of the checkboxes came back as successful. Has anybody else encountered this issue or does anybody have any hints for how to alleviate it?
VMware just release vCenter 7.0 U3d this week. Just list out some key resolved issues for reference:Deploying a virtual machine by using an OVF template might fail on a cluster with VMware NSX-T Data Center Incremental patches of vCenter Server 7.x fail with Exception occured in postInstallHook error When you try to log in to the vSphere Client, you get an error that you cannot connect to the vCenter Single Sign-On server https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3d-release-notes.html
Hello, We have Veeam O365 5b (126.96.36.199). By mistake we enabled the backup job for the entire organization, so that means it includes Sharepoint, OneDrive, Teams, etc. and now our Repository disk is full.We need to do a clean-up of the repository disk, in order to leave just emails (users, groups, shared mailboxes, archives, etc.) and delete all data of Sharepoint, OneDrive, Teams, etc. Finally create a job only for emails (users, groups, shared mailboxes, archives, etc.)How can I do that?Thanks for your help, Omar De Souza.
hi all,anybody know is it possible converted physical server to virtual VM using Veeam just like veritas backup exce. I am going to physical to virtual migration using vmware conversion tool. But when I converted my Linux server it showing booting error. if you have any other good solutions please suggest. Thanks in advanced
This week I was investigating some imbalance in size on two (scale out) repositories. Every repository gets the backup of a subset of all VMs and copy these to the second repository. And vice versa. So in theory, both repositories should be very similarly utilized. But when you look at volume properties, this is not the case. We see quite a large difference. So I used PowerShell to query VBR and sum all data of each VM on both repositories (I will post some code snippets next week). And I found out, VBR does not know about a notable amount of data (VBR-query showed much less used data than volume properties did).So there seems to be backup data, VBR is not aware of. I call these files orphaned files. What are your experiences with orphaned files? Do your see them very often or not at all? Or are you not aware of their existence? Please let us know.[Update] See my new blog post on how to find orphaned backup fileshttps://vnote42.net/2021/11/30/query-backup-job-space-on-veeam-repositorie
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.