VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
I have a user who is having issue logging in to the VEM Self-Service portal. We have added groups to have access and I have added myself to their group so I can test every now and then.I can login just fine as a member of the group but he keeps getting Invalid username or password error. We are sure that his credentials are good since he is able to use them on other servers and applications so it is only in Self-service portal where he is getting the error. He cleared his browser’s cache and used other browser as well to no avail.I looked at the Veeam.WebApp.log, these are the entries that I see for the userConnecting to [ServerBEM] under [current account]. Selfrestore modeFailed to create user context from authentication data. Data: [Username: domain\user, Invalid username or password (System.Security.Authentication.InvalidCredentialException) When I login as part of their group, this is what I seeConnecting to [ServerBEM] under [domain\myself]. Selfrestore mode:Remote session opened
Unable to delete this folder causing application aware backups to fail.The service is not running and PID 4 (NTOSKernel, system) is locking the file. Reboot resolves the issue but this issue is happening to more than a dozen of production servers.What suggestion do you guys to resolve the issue without any reboot? Thanks.
Running VBR v12.0. Created a backup job. Ran the job and got an error so went back in and try to edit the job. I got the error below. First time, I encountered this error. The backup log just showed the same information. I have a similar job running in our “staging” VBR but not having any error. The backup job is a storage snapshot and does handle SQL transaction logging. I saw in the Veeam’s Forum the same error message but this was for a backup copy job. What do you think is happening here?
I'm seeing this error "Failed to process VM: Failed to create MachineMutex" when doing storage snapshot. The first try fails but the 2nd try succeeds and usually the issue comes and goes. Failed to create snapshots on primary storage: Failed to wait mutex sandiscover7c39d713-bdbb-40f1-ac8d-af87774de299_b72e5bb7-87e2-4802-9043-2d6a76f9052d: timeout 600 sec exceededFailed to create storage snapshot for datastore abcdef: Failed to wait mutex sandiscover7c39d713-bdbb-40f1-ac8d-af87774de299_b72e5bb7-87e2-4802-9043-2d6a76f9052d: timeout 600 sec exceeded Who has seen this issue and cause/resolve info?
How to retain VMs brought up using VDRO longer than 7 days?In order for us to retain the VMs past 7 days, we decided to basically stop Veeam services on our VDRO server. Needless to say, our VDRO is inoperable at this state. We’d like to bring it up and not affect the VMs that were created. So I think, this means that we need to modify entries in the VDRO database to “cleanly” remove this from VDRO but un-touch on the vSphere side. We can rename the objects in vSphere but not sure if this would work since VDRO may be using object IDs in its DB instead of object name. The VM involves is a big DB and just running a DB check took about a week and after this a patch needs to be applied necessitating another check that is why we need it longer than 7 days. Thanks for the ideas and suggestions. I have also opened a low sev ticket with support and will share what they recommend.
I have noticed that if I go to Veeam Backup and Replication and look at our SOBR’s Space Usage Graph under the Summary tab, it shows just one day (e.g. it shows just Sat 9x instead of different days). This happened when we upgraded to version 12. Monthly Summary shows one set of datesWhat setting if any should I change? I have updated to the latest patch and still shows the same. Version 11 did not give me this issue.
vCenter shows disk consolidation requested by Veeam but also displays percentage of completion. What's a good plan to be able to restart the Windows DB VM? See screenshots below.From what I know, it is not a good idea to reboot while consolidation is going on. However, this has been going on for at least 2 days and the DB residing on the server is performing poorly. I have requested the DB folks to try to restart the DB instead of the server but in the event that this would be the only option that is left to do, what is a good way to go about doing a VM reboot. I have disabled the job in Veeam and has cancelled another Veeam request to vCenter to run another consolidation (thoe one showing 0%).
We just moved a couple of servers to a new volume in NetApp using its new large file/volume feature. Nothing has changed on the backup job except the volume that it is backing up. The smaller server around 3TB was able to be backed up using SAN but the other server that is approximately 43 TB is being backed up using NBD. Prior to the move, both servers are doing SAN direct. I would think that since these are both on the same volume is one has been successfully backed up using SAN the other should as well. Both servers are also in the same compute cluster and both are using the same proxies. What is causing this behavior?
We are migrating some of our VMs to Azure (AVS) using vmware HCX. We just migrated a VBR to the AVS environment.So Veeam when Veeam tried to backup a VM in the AVS environment, we get this error: 11/14/2022 10:53:45 PM :: Processing bbbbbbVM Error: Failed to open VDDK disk [[vsanDatastore] c9d37263-be7b-37b8-2875-08c0eb40d47a/bbbbbbVM.vmdk] ( is read-only mode - [true] )Logon attempt with parameters [VC/ESX: [vc.4bc149b43878428757ed53.westus2.avs.azure.com];Port: 443;Login: [userdite@abd.lcl];VMX Spec: [moref=vm-1073];Snapshot mor: [snapshot-1084];Transports: [nbd];Read Only: [true]] failed because of the following errors:Failed to open disk for read.Failed to upload disk. Skipped arguments: [vddkCo Looks like a permission issue with using the CloudAdmin account (which is the account with the highest privilege) that we are allowed to use in AVS.We can do backups using agent based install but looking for other alternatives. Thanks.
We are trying to restore a huge DB which is part of a Always On Availability group to a test server. So the test server is up with the DB. However, the DB shows as Restoring after the restore. What is the work around to make the DB Ready? From what I’ve read, we need to drop the DB on this test server from the Availability Group. How can this be done without affecting the production DB. Our DBA is unable to drop the DB so reaching out to the community for alternative solutions.
We’ve been testing our Orchestration Plan and after failover to our DR site, the certs on our vCenters were replaced and broke the connections between our DRO and vCenters. Had to refresh the connection so the DRO can take in the new certs. However, when we tried to failback to our primary site, we had the login error to vCenter. The issue was fix when we had to go into the built-in VBR and refresh the connection in VBR itself. I would tend to think that DRO itself would be able to restore the connections within its built-in VBR and VeeamOne. Let me know what you think or if I’m missing something here.
Trying to migrate Enterprise Manager to a new Server. I stopped the Veeam services on the old server and disconnected it from the network. I installed the EM on the new server and pointed it to an old DB that was used by the old server. There was a dialogue window confirming that the DB was owned by the old EM server and that it would be transferred to the new EM server.What happened next is that the the service account was getting locked out. So I had to roll back the changes. Good thing, I did not uninstall the EM from the old server per the instruction on https://www.veeam.com/kb1889 . Curious what happened here.
I’m trying to upgrade our VBR to v12.1 but keep getting the message that I should upgrade my Backup Enterprise Manager. I have removed this server from our EM but still the Configuration Check insists that I upgrade the EM first. I have read somewhere that a special MS SQL script should be run in order to be able to successfully remove a VBR server from EM. And the only way to get this script is to open a support ticket. Let me know if I need to do this or if somebody has found a way to work around this.Thanks.
I’m trying to do Instant Recovery of a large server from a VeeamSourceSnapshot to a different volume. There is no option of doing this, what’s the workaround? We are using NetApp and it has a 100TB limitation on the volume size so this is the reason why I would like to restore to a volume that has more free space. Appreciate your input!
Hi! We just recently changed our service account password that we use for Veeam services. So I went into Credentials and Passwords > Datacenter Credentials > Manage Credentials and made the change there after changing the account password in AD. I know Veeam processed the password change because the proxy servers and repo servers went back to online after being offline after the change. However, after a couple of nights, all the backup jobs failed. Long story short, the Veeam services using the service account did not get change so the services had to be restarted.What is Veeam’s behavior after a password change? I would tend to think that Veeam would at least pop a message stating that it is not changing the Veeam services credentials and this has to be done manually. What am I missing here?
SQL restart when doing Instant DB recoveryThe Database went offline and in Recovery Pending state. It is currently doing Instant DB Recovery. Is it safe to restart SQL to bring the Database online without affect transactions already in the cache folder? Would it affect the Instant DB recovery process (I don’t think so but better to ask). What other processes should we consider before doing a restart of the SQL? Thanks.
We restored close to 40TB of SQL Data. It took almost 100 hours to do the restore. The backup base image is on NetApp All Flash array. All the datastores for the VMs are in this array. So I would tend to think that application restore would be a lot faster unless application restores are done through the IP network (as opposed to Direct SAN). I monitored the network interface of the destination VM and saw the traffic coming into this interface.What is really the data flow for a SQL application restore?
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.
I’m wondering if anybody has tried getting a report of all VMs that would be registered in vCenter during failover.Our Plan Type is Storage and some of the VMs in the volume are not required to be recovered at the DR site. The Plan Report shows the VMs but I’m thinking of a DB report, for example, that would enumerate the VMs that would be registered instead of manually retrieving them from the plan. In short, a report showing a VM with “Register VM” in the Recovery Steps. Thanks.
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.
