Discussion Boards

Hi All,I have a question about completing replication jobs if the replication windows exceeds.  For the initial replication, Veeam will transfer the base full size of the replicated VM. Let's suppose it's a huge size VM and initial replication did not finish in the repli action window.When the next schedule run, will Veeam start transferring from the beginning for the initial full or incremental replica that does not finish, or it will continue from the stopped point abd replication does not take another time and size? I have read about (resume disconnect) but need to make sure from the experts? https://helpcenter.veeam.com/docs/backup/vsphere/replica_resume_disconnect.html?ver=110Let's suppose the replication window from(17:00-23:30) only. Thanks

We’re using Veeam as a backup to Office365.  Our old-school owner wants to backup on-prem and periodically take a snapshot of the DB and bring it home.  We also are a small shop and don’t have a dedicated NAS.  What we do have is a compact i7 with plenty of RAM and a USB 3.0 port.We put a 1T PNY flash drive on it and it worked for about a month.  Then we started getting JetDB errors.  We put in a ticket and have been going back-and-forth with support (they have been responding nicely and it’s appreciated.)We’ve tried several solutions, seemed to be making progress but after the last iteration, they think it’s the drive.  I asked for a recommendation for a good set of specs but they couldn’t give me one.Is anyone out there using a Flash drive as their primary repo store?  If so, can you tell me what brand/model you’re using? Thanks in advance!  Scott.

Hi everyone!@MicoolPaul ask me to post his fun Friday question this week, while he enjoys his holidays 😎 VeeamON 2022 has just wrapped up, and Veeam have announced VeeamON 2023 is in Miami next year. So how do you plan to attend? Happy Friday to all Detective Mildur

I had to remove 2 virtual disks from a VM running in vSphere 6.7.The operation was ok, and also the replica Job didn’t complain about that.The problem is that the replica VM has still the old disks attached, while the source VM doesn’t.So the modification in the source VM configurant was not reflected to the replica VM.Question: - is it safe to remove the un-wanted vHDs from the replica VM using vCenter, - or else we need also to re-create the replica job? 

I set up a Replication Job from the Main to the DR site for a VM running in vSphere and everything is fine.Now I have to move the replica VM to another datastore located at the same DR site.I could perform a storage vMotion on the replica VM, but I have some doubt: - would a storage vMotion on the replica VM harm the Veeam Replication Job? - should I need to modify the replication job in order to point it to the new datastore? - would I need to delete the replica job, perform the storage vMotion, and then re-create the replica job, seeding it with the existing replica VM (would like to avoid that...)?How to do that in the most secure / efficient way? Thank you

Hello Team,Greetings!I am working on a DR project for one of my customer. The Production and DR Site is both VMware infrastructure. Currently the Veeam Backup & Replication instance is running in Production Site and all the VMs are replicated over to DR site. We have Re-IP features in DR plan, so when failover happens the VMs get IPs for DR site subnet. Question is, in case of the Production site completely goes down, no access to anything:Will the Re-IP feature work? Cause my Veeam instance is also in production site? My only option is to power on the replica VMs in DR Site manually and change the IP within OS manually?  Is there a way we can setup a High Available/Secondary instance of Veeam Backup & Replication in DR site? (with same configuration as per production site?). So if the production site is completely down, we can still manage the backup & replication portion from DR Veeam instance? If question 3 is possible, do we need additional Veeam license or anything els

Hi,I am trying to deploy Veeam Backup for Nutanix AHV, followed all the instructions of the documentation. Although I have selected a NAS while configuring for the backup, in the console of Proxy, it shows repositories as 0 and Backup server status as Unavailable. Also, in the manage backup server [Import Backups] is greyed out. Only PD snapshots are being created as seen in VBR.Please help.Thanks.

Hi Everyone,I need help with a trip down memory lane. When was the linux helper host introduced. If I am not completely confused I remember that you used to have to use a helper appliance that Veeam would install on Esx but then later introduced the Helper Host where you could simply use a Veeam host in your managed servers to help mount the linux file system. It has been a while and I could be off target with this  Was it one of the V11 updates? I will dig and see maybe between 10 and 11.

Hi all,Recently, my ESXi home lab host died, taking with it the main data store that contained all my working VMs including a Veeam Replication and Backup Community Edition VM. This VM was backed up several of the VMs on the ESXi host to an alternate location, so perhaps there is light at the end of the tunnel.In the first instance, I will need to create a new VM for Veeam, then reinstall Replication and Backup and re-attach the backup store. However, when looking at https://helpcenter.veeam.com/docs/backup/vsphere/importing_backups.html?ver=110, there is a pre-requisite requirement that states:The server from which you plan to import backups must be added to the backup infrastructure. Otherwise you will not be able to access backup files. Does this mean I need to re-create to lost VMs in ESXi first, before I can import any backups? Do then need to be specific configurations that match the original VM (such as vHDDs)? Do they even need be fully recreated with OS? Of is it simply that I

Just wondering if any of you encountered this issue.We have been using Virtual labs for more than a year now. However, when our team tried to upgrade our NSX-T environment. They found out that the IP (Gateway IP) configured on the isolated side of the router is responding. This segment is connected to a NSX-T logical segment that was configured to be isolated.I think there is an issue with the NSX-T logical segment not configured properly but would like to see if there is some unknow issue with the Veeam’s virtual router.Thanks.

Got caught back up on community recaps last night (I was a couple weeks behind) but over the course of the past 8ish months, I’ve noticed that @Rick Vanover mentions breaking the rule, or not breaking the rule, or sorta breaking the rule but it’s okay. My question is, for those of us who haven’t been around since the community inception…What is “the rule”?

Hello everyone! I am building brand new VEEAM environment. The plan is to have Management Server as virtual machine as well as proxy servers. Physical components are: Immutable repository, Tape Server+Tape library, SANs. I got stack with the point of restoring environment in case of main management server is not available (ransomware attack, whole virtual environment is down, including SANs). I still have backups on tapes. Maybe on Immutable repository. I was going to backup Management server configuration to repository on Tape Server . And Tape server itself periodically to external hard drive. So as a starting point  we have healthy Tape server + backup of the configuration can be used.What will the the steps to recover the environment? Cheers,

Just a quick post; the latest Windows Server updates for 2012R2, 2019 and 2022 (haven’t seen 2016) can cause ReFS issues. After the installation, ReFS volumes are shown as RAW and are no longer accessible; so if you’re using ReFS for your repositories, then take be aware of this when installating the update. Besides that, those updates can also cause bootloops for domain controllers and break Hyper-V.Depending on your Windows Server version one of the following updates could have caused the issue: KB5009624, KB5009557, KB5009555 If you’re affected then removing the mentioned update should solve the issue. Don’t (!) try to repair the ReFS volume, because this could cause a dataloss.This should remind everyone why 3-2-1 for Backups is so important. Further information:https://www.bleepingcomputer.com/news/microsoft/new-windows-server-updates-cause-dc-boot-loops-break-hyper-v/https://forums.veeam.com/veeam-backup-replication-f2/beware-possible-raw-refs-volumes-after-installing-january-upd

Hi guys, i know that in v11 is not recommended use the dedup repo as primary backup storage, is there any news in v12 ? The customer wanna buy 2 x Quantum DXI dedup hw appliance (each site one dedup appliance) and i3 scalar tape library. From my point of view, the best pracices is - backup to ntfs/refs/xfs repo as primary backup and after create a 2 backup copy jobs to each dxi appliance and after create a tape backup job. BUT.The customer wants a send the primary backups to DXi and after to tape. its possible or its bad plan ? Thx.Tom. 

Hello to all,I have backup chains stored on XFS volumes with reflink that were created with FastCLONE.How can I move these strings to another volume while preserving this? Thanks

Hi, We have a Dell Power Protect appliance with 7.5TB of space, when I check the used space on the Veeam console, I found that it's only shows me the pre-compression value as used space (8 Tb). The console also shows me the free value (7 Tb) and I think it's correct after data compression. So I still have other servers to add on veeam with 5TB of data and I want to know if our Dell Power Protect will support this extra space or not. Thank you.  

Greetings. I have an on-prem Windows Server 2019 Datacenter with the Hyper-V Role enabled running about 10 VMs. I was applying an update to one of the VMs, a Windows Server 2016 running Exchange 2016. The update, CU23, failed, forcing me to restore the machine. Prior to the attempted update I had VeeamZipped it from the B&R 11A CE panel, and so I  launched the restore from there. After restoration I had quite a bit of troubleshooting to do to get mail flow back but I was completely successful.The remaining issue is this: Upon VM startup, there is a long pause, 3 full minutes, during which I see the expected black screen with “Hyper-V” logo smack in the middle, but it sits there doing absolutely nothing I can see. No circle of dots, just the Hyper-V text. After 3 minutes the circling dots begin and I have desktop in about 30 seconds. and everything runs normally. The disk layout is the usual Recovery, EFI and OS partitions.Has anyone run into anything similar? Thanks for any thought

Good day all, hoping to find someone who has either seen this or may know where I could start to troubleshoot (I'll open a ticket with support as well, just hedging my bets here). We've used Veeam for server/VM backups for a few years and it's awesome.For workstation backups, we've used Carbonite (don't ask, we've tried to get rid of it in the past but got shot down by higher ups/non administrators) but it has been decided that we're not going to renew this year (got about a month left on our annual term).Over the last year, I implemented OneDrive KFM so that our desktop and documents folders are resilient and more "portable", which has made our hardware swaps much smoother and reduced the need for Carbonite.But I digress...while nobody actually said to go find a replacement for Carbonite (it seems to be the thought that OneDrive KFM is a replacement for backups,.which I know it's not), I am looking into alternatives, and Veeam would seem like the logical choice. So I've been doing som

Hi Everyone, I just found this. It seems to have been around since June but I missed it. If any of you are trying to up the anti on your Github skills take a peak! To think I shelled out $14 on the Udemy Black Friday sale for the Git bootcamp. Oh well more is better than less :) https://skills.github.com/ cheers  

I’m a user of Veeam B&R Community Build 11.0.1.1261, and I’ve just started experiencing a problem a second time that I thought was fixed.Some time ago (a couple of weeks to a month), I started experiencing an issue with Veeam backups. When it would try backing up, it would quickly error out with the following error:Warning    Failed to synchronize [Backup Repository] Details: Failed to call RPC function 'NfsIsExist': Failed to reset previous connection exception: Permission denied. The first time that happened, I assumed it was because I was disabling Veeam services that I thought were unnecessary. Despite re-enabling them, the error persisted. I eventually realized my installation of B&R was out of date, so I installed an updated version and that seemed to fix the issue for the time being.Fast forward to today, and I’m seeing the aforementioned error again when trying to run backups. The repository is a Synology DiskStation, and I can verify that the share is accessible from a

Private message 

k10toolsTried to use cephfs provisioner: rook-ceph.cephfs.csi.ceph.com by the “k10tools” command and portal. Both the result is failed to create snapshot and backup with PVC and data. May I know if there is any method to use cephfs provisioner with Kasten to backup? And, Since the PVC has to set AccessMode as ReadWriteMany, the rook-ceph.cephfs.csi.ceph.com provisioner can’t be insteaded with rook-ceph.rbd.csi.ceph.com

The restore point was created at 10/4, but the VIB file was remove from the disk already, on the resotre point portal, it still show normal status for this resotre point, so i cannot remove it.  Also try to rescan bakcup repo, it say below:added 0 unencrypted, added 0 encrypted, updated 0, removed 0, skipped 1, failed 0

Hi Folks, This is a good time of year to look back and be grateful for things that we have. I think everyone will agree here that the Veeam Community Hub is a stellar success! I wanted to thank the Veeam folks, past and present who have made this place what it is. @Rick Vanover @Madi.Cristil @NikolaPejkova @Kseniya @safiya work/worked very hard to not only keep this place running but to proactively improve it. Even with such success they remain humble and approachable people.As everyone in IT knows, when things are working well people take it for granted (I had a non IT boss once who rather foolishly 😆 claimed to upper management during a meeting that “these systems just run themselves”) but we know they don’t.  In contrast, when things go badly the blame game gets targeted squarely on the humans behind the machines or systems. The same is very true about the Community Hub, “It Just Works” in Marketing jargon, but translated into human dialect “It Just Works because of the efforts of

Hope you got my present everyone ?