veeam errors

[aacable]

I am using Veeam B&R to backup few esxi vm guests. At one guest (which was converted P2V & worked with veeam for long without issue) is now making trouble with following errors. I tried the veeam knowledge base, tried changing disk size and recalculate, but still getting errors. Any advise would be appreicable.

.

Code: Select all

7/18/2022 5:04:43 PM :: Queued for processing at 7/18/2022 5:04:43 PM  
7/18/2022 5:04:47 PM :: Required backup infrastructure resources have been assigned  
7/18/2022 5:06:09 PM :: VM processing started at 7/18/2022 5:06:09 PM  
7/18/2022 5:06:09 PM :: VM size: 1.9 TB  
7/18/2022 5:06:10 PM :: Getting VM info from vSphere  
7/18/2022 5:06:17 PM :: Using guest interaction proxy VEEAM_Plant3.OFFICE (Same subnet)  
7/18/2022 5:06:21 PM :: Inventorying guest system  
7/18/2022 5:06:33 PM :: Preparing guest for hot backup  
7/18/2022 5:06:58 PM :: Releasing guest  
7/18/2022 5:06:58 PM :: Creating VM snapshot  
7/18/2022 5:07:04 PM :: Indexing guest file system  
7/18/2022 5:07:06 PM :: Potential data sovereignty violation: target 2TB Local Folder _Veeam_office location (Plant-3) does not match source MYSRV.LOCAL location (No location tag).  
7/18/2022 5:07:09 PM :: Saving [11.7_6TB_SSD] MYSRV.LOCAL/MYSRV.LOCAL.vmx  
7/18/2022 5:07:10 PM :: Saving [11.7_6TB_SSD] MYSRV.LOCAL/MYSRV.LOCAL.vmxf  
7/18/2022 5:07:10 PM :: Saving [11.7_6TB_SSD] MYSRV.LOCAL/MYSRV.LOCAL.nvram  
7/18/2022 5:07:19 PM :: Saving R3P.ora  
7/18/2022 5:07:25 PM :: Saving R3P_sqlnet.ora  
7/18/2022 5:07:29 PM :: Saving R3P_listener.ora  
7/18/2022 5:07:33 PM :: Saving R3P_tnsnames.ora  
7/18/2022 5:07:37 PM :: Using backup proxy VMware Backup Proxy for disk Hard disk 1 [hotadd]  
7/18/2022 5:08:06 PM :: Hard disk 1 (280.0 GB) 31.7 GB read at 213 MB/s [CBT] 
7/18/2022 5:09:43 PM :: Using backup proxy VMware Backup Proxy for disk Hard disk 2 [hotadd]  
7/18/2022 5:10:09 PM :: Hard disk 2 (0.0 B) 0.0 B read at 0 KB/s [CBT] 
7/18/2022 5:11:14 PM :: Removing VM snapshot  
********************************************************************************************
7/18/2022 5:11:33 PM :: Error: Virtual disk size is not a multiple of 1KB.
********************************************************************************************  
7/18/2022 5:11:33 PM :: Busy: Source 6% > Proxy 46% > Network 31% > Target 73%  
7/18/2022 5:11:33 PM :: Primary bottleneck: Target  
7/18/2022 5:11:33 PM :: Network traffic verification detected no corrupted blocks  
7/18/2022 5:11:33 PM :: Processing finished with errors at 7/18/2022 5:11:33 PM  
********************************************************************************************
7/18/2022 5:11:36 PM :: Failed to obtain guest file system local users: VSSControl: GetGuestGroupMembers failed, groupSid 'S-1-5-32-544' Details: Cannot invoke 'BlobCall' : there is no message transport.  
********************************************************************************************

Regard's

[Mildur]

Hello,

Please do not upload logs to this forum (forum rule). Logs snippets are for our support engineers.
I assume, you have tried this kb article?
https://www.veeam.com/kb1848

Either way, that sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic. Without case number, the topic will eventually be deleted by moderators.

Best regards,
Fabian

PS: support can only help if you upload logs https://www.veeam.com/kb1832

[aacable]

I dont have support id because i dont have active subscription.
When I exclude disk2 , the backup works fine with OS disk only. So how can I further troubleshoot the 2nd disk? any advise would be appreicable.

[Mildur]

As documented in our forum rules, a case can also be opened with the community edition. So please create the case.

If Disk 2 is the issue, and you have tried the resizing, then we cannot help you in the forum. Logs needs to be analyzed, which cannot be done over the forum. And guessing the issue is not the right way to solve a problem.

Thanks for understanding
Fabian

[aacable]

I tried all solutions but couldn't figured out. As a last resort I did following. I know this workaround is not the proper solution, but since I failed to sort it by all means, & taking backup was crucial, therefore following steps worked for me. Luckily I had enough resources to cater the workaround. 6 drivers SSD in Raid-5 made the transition really fast

- Stopped all running services related to Oracle/SAP or any un necessary apps
- Added new disk (drive3 / H: ) on the effected VM with same size as existing DB drive (disk2 G: )
- Cloned the partition from old (disk2 G: ) to this new (disk3 H: )
- Using Disk Management, I changed the drive letter & marked the old (disk2 G: ) OFFLINE.
- Changed the new disk (disk3 H: ) partition drive letter same as older one that is G:
- Rebooted the server, & this time all backups went smoothly & SAP ORACLE synching/services are working fine as well
- Afterwards I removed the OLD faulty partition from the VM.

Thank you for the tips.

[Mildur]

Hi Syed

Thanks for sharing your solution with us.
I'm glad you found a way to solve this issue.

Thanks
Fabian