Cannot Access A San/iscsi Lun Backing This Virtual Disk
And then configure a backup using the Arcserve manager. VMware VCB framework reported the following error Error: Failed to open the disk: Cannot access a SAN/iSCSI LUN backing this virtual disk. (Hint: If you are using vcbMounter you can use I’m using Backup Exec 12.5 and VCB to back up my VMs. I changed the preferred path back to Contoller A and my LUNS were presented in Disk manager as they should be “Healthy (Unkown Partiton)”.
I’m glad this fixed my problem navigate here
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group Return to WDC.com WD Community Contact Us English Product Support My CloudMy BookMy PassportWD Elements & WD TVInternal DrivesWDLabsLegacy & Other Verify that the Disk Management console resembles (Figure 2). (That the SAN LUNs are being presented to the VCB Proxy appropriately). 3. I had a look at Storage Manager and sure enough, all my LUNs were on Controller B. Email Address (Optional) Your feedback has been submitted successfully!
The SAN hardware usedis not supported by VMware. Syncing disks. [[email protected] /]# vmkfstools -V [[email protected] /]# For more information, visit the following site: http://kb.vmware.com/kb/1002281 Attention: If you have several disks with missing VMFS signatures, change all disk signatures at Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview The general difference determine what troubleshooting should be done.
It is also suggested to instead only check the debug checkbox and let the VM's be populated into the Database. Refer to the SAN Transport Mode support operating systems section of the Arkeia vStorage Guide. Powered by Blogger. First, check the output of a failed vcbMounter backup job: [2011-06-30 10:17:24.315 'App' 5664 error] No path to device LVID:2bedb412-a987b654-1234-012a345b6cde/2bedb412-9bc87d6e-abcd-012a345b6cde/1 found. [2011-06-30 10:17:24.315 'BlockList' 5664 error] [2011-06-30 10:17:24.529 'vcbMounter' 5664 error]
ca_vcbpopulatedb return Code is 3, end of ca_vcbpopulatedb Solution: Return Code 3 means 'ESX Server or VirtualCenter Server user authentication error'. What happened? Sorry, we couldn't post your feedback right now, please try again later. https://forums.veeam.com/veeam-backup-replication-f2/san-mode-backups-failing-t2879.html Further review of posts on the web indicated that it may have to do with the LUNs being on Controller B.
Modify the Backup Job Properties and select Settings, VMware Virtual Infrastructure.2. If one of your VM has 300GB which is the biggest of all then you should have at least 325GB disk space available on the Mount Dir location. This agent is readily available to many of our clients and common problems may already be found and corrected. Solution: To change the disk signature back to VMFS, connect to the console of a vSphere host server.
All trademarks, trade names, service marks and logos referenced herein belong to their respective owners. For setting the mount path the following registry value needs to be changed - HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\ClientAgent\Parameters\VMwareAgentBaseMountPath Edit and enter the location where you want the VMs to be dumped. 'arcserve Failure to update could result in poor performance as well as general disconnects. The same can be cleared from the ESX VI client or VC interface. 'vcbMounter' 2692 error] Error: Cannot open disk blklst://snapshot-543[HP EVA SAN] uktrowap15/[email protected]?xxxx/xxxx.
The process of exposing the LUN to your vBackup server will differ depending on if your SAN is FC or iSCSI and the topology used for connectivity. check over here Cause: There are many reasons that this error can occur. I.e. Open Command Prompt (Start->Run->CMD->OK).2.
Additionally, the mount path for the VM operation is set to the Windows client agent folder, set it to a Disk location which has sufficient space to accommodate the biggest VM Solution For setup described in scenario A follow the steps below:1. You may also refer to the English Version of this knowledge base article for up-to-date information.
Article:000035280 Publish: Article URL:http://www.veritas.com/docs/000035280 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in
Incapsula incident ID: 225000820239931143-878021195128177959 Community Forums Veeam products and related data center technologies Skip to content Board index ‹ Products ‹ Veeam Backup & Replication ‹ SAN-mode backups failing Change font Check the account credentials being used on the ESX server. Gostev VP, Product Management Posts: 20152 Liked: 2052 times Joined: Sun Jan 01, 2006 1:01 am Full Name: Anton Gostev Private messageWebsite Top Display posts from previous: All posts1 day7 Gostev VP, Product Management Posts: 20152 Liked: 2052 times Joined: Sun Jan 01, 2006 1:01 am Full Name: Anton Gostev Private messageWebsite Top Re: SAN-mode backups failing by stephaneb »
Solution: IMPORTANT: This article contains information about modifying the registry. Initially everything was fine and then all of a sudden the backups were failing with the error “Failed to open the disk: Cannot access a San/iSCSI LUN backing this virtual disk”. No Yes Did this article save you the trouble of contacting technical support? weblink I can't select the backup root without a drive letter that I can see. 3/20/2012 8:42 PM vBackup Team Joined: 2/25/2011 Posts: 351 Re: Receiving errors trying to backup VM
GMT+00:00 :: Casablanca GMT+00:00 :: Dublin GMT+00:00 :: Edinburgh GMT+00:00 :: Lisbon GMT+00:00 :: London GMT+00:00 :: Monrovia GMT+00:00 :: UTC GMT+01:00 :: Amsterdam GMT+01:00 :: Belgrade GMT+01:00 :: Berlin GMT+01:00