AdminSky.org

1.Verify the CHAP authentication username and password are correct on both Dell iSCSI SAN PS series and Windows iSCSI initiator.

2. Uncheck Authenticate using CHAP user name on Dell Dell iSCSI SAN PS series and only select Limit access by IP Address and specify the range of IP address to which it can authenticate.

The volume shadow service provider vetoed an operation. The provider logged the error in the event log.

Error 12507

The volume shadow service provider is unable to find an object that has been selected. This could be a volume, a Writer or a Component.

Module:

VSS Error Messages

Reason:

The selected volume, Writer, or Component is not available to the Volume Shadow Service Provider.

Action:

Check the Activity Log and the Windows Event Log for additional information.

Check the Windows server, at the exact backup time, the Windows system logged “Event ID 10, iSCSIPrt,  Login request failed. The Login response packet is given in the dump data.”  The Windows server iSCSI volume tempararily lost the connection to iSCSI target, so CA Brightstor ”Agent for Open File” couldn’t take the snapshot for this volume, therefore CA logged Error 12507 within backup log. 

Check Volume Shadow Copy Error – provider veto for troubleshooting VSS error.

When using the VSS or SYNC driver within a virtual machine, the tools attempt to quiesce all I/O (storage, memory, etc) within the virtual machine. Because the virtual machine has a MS iSCSI initiator LUN attached within it, the VSS or SYNC is unable to quiesce the guest operating system in the time allocated for the quiesce operation.

Disabling VSS

Disabling SYNC

1. Open Device Manager, click View, and select Show hidden devices.
2. Expand Non-Plug and Play Drivers.
3. Right-click Sync Driver and select Disable.
4. Click Yes twice to disable the SYNC driver and restart the virtual machine.

Environment: ESX 5.5, Virtual Center 2.5, vRanger 3.2.4.2, VCB 1.0, Microsofte iSCSI initiator 2.0.8, Equallogic PS5000 Series iSCSI SAN

It’s kind a general error code for vRanger VCB backup. Most time, it won’t give the detailed information for your troubleshooting. From the previous experience, we figured out that a couple of typical setup can caused the problem.

1. The backup data LUN or the ESX datastore LUN won’t be able to be accessed by both ESX host or the VCB Proxy server (vRanger Server), so the snapshot won’t be able to be transfered.

Solution:

a. Rescan the ESX host to make sure the vRanger backup data LUN can be seen from ESX host. 

b. Rescan iSCSI initiator from vRanger server to make sure that the vRanger server can see all of ESX host datastore LUN.

2. vRanger backup data LUN has not enough space to backup. Even the vRanger backup compressed the data during the backup, it still needs the initial available space is bigger then the source VM drive.

Solution: Incresed the target backup data LUN to make sure that the available space is bigger then any source VM drives.

In general, HW HBA has 30% more performance than SW HBA overall throughput and IOPS.

When you use HW HBA for your ESX server, you shouldn’t use SW Initiator within your guest OS any more, because for the guest OS, when it sees the software initiator, it will bypass the HW HBA function, and only use the basic networking function of this HBA. It will waste the money.

The same true for the NIC card with TCP/IP Offload Engine, there is no need to use TOE in ESX host when your guest OS is using software initiator, it will bypass TOE as well.