Error: The SR Backend failed to complete the operation

I keep randomly getting this error message when performing almost any operation requiring accessing my shared storage (creating VMs, starting VMs, installing hosts, etc). The SR is set up to connect via iSCSI to a volume on my NexSAN SATABeast. Anyone have any clues how to resolve this?
xe sr-list params=all excerpt:
uuid ( RO)                    : 0262540f-0d05-b31f-595f-a4d72ff19f17
              name-label ( RW): iSCSI virtual disk storage
        name-description ( RW): iSCSI SR [172.16.2.41 (iqn.1999-02.com.nexsan:p0:satabeast:01611238)]
                    host ( RO): <shared>
      allowed-operations (SRO): forget; VDI.create; VDI.snapshot; plug; update; destroy; VDI.destroy; scan; VDI.clone; VDI.resize; unplug
      current-operations (SRO): 
                    VDIs (SRO): ccd8c8cb-0ce5-4307-ab16-cc5922f9dde7; e427cbaf-6e80-414c-bb3f-f9de0fbaf69f; 302b475c-467b-4023-ba49-7c00d4d99463
                    PBDs (SRO): 7c8a0994-98c3-258b-1755-134600124879; 36504d0f-a812-8d05-9d25-53ce76356f0d
      virtual-allocation ( RO): 134502940672
    physical-utilisation ( RO): 343253450752
           physical-size ( RO): 1023988989952
                    type ( RO): lvmoiscsi
            content-type ( RO): 
                  shared ( RW): true
            other-config (MRW): auto-scan: false
               sm-config (MRO): allocation: thick; use_vhd: true; multipathable: true; devserial: scsi-36000402001fc12386369373200000000
                   blobs ( RO):

Open in new window

LVL 6
rpasseroAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rpasseroAuthor Commented:
The problem was related to DNS/routing settings on one of my hosts...which is why the error only appeared sometimes, when that particular server was attempting to do the provisioning.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.