Solved

Intellisnap Backup Copy kills Virtual Disk Service on Server 2016 Media Agent



Show first post

39 replies

Userlevel 2
Badge +4

@dude : true CV Cloud can be a target library (but source?)

@Neil Cooper : where do you migrate your source data? (from dell to »?)

What do you mean by lowering the detail required in the subclient ??

 

Userlevel 7
Badge +23

@Neil Cooper , are you now resolved on this issue as per your most recent update?  Want to be sure we don’t have any dangling threads :sunglasses:

Userlevel 2
Badge +4

Sorry @Mike Struening 

 

I was late marking correct answer but I did it tonight!

 

Cheers

 

Neil

Userlevel 7
Badge +23

No problem, @Neil Cooper !!!  Thanks!!

Userlevel 2
Badge +4

@HenkR lets not get off track here. My hope as a CV customer is to be able to manage everything as a Service so I don’t have to spend so much time looking after it. 

Here is the screen shot. Clear out all the options. My snap / backup copes went from 30 minutes each on an incremental to 5 minutes each:. Also I set the proxy at the subclient level as well to manually balance snapshot work load:

 

 

Userlevel 2
Badge +4

It was some kind of rhetorical question ;-)

Ah, that is different. Hitachi has not that much options ;-(

I am on the same level by the way ..11.22.27 (coincidence?)
 

 

I did some cleanup of hidden disk and reboot the MA several times no luck there.

Although the VDS notices were lowered but not gone.

Seems that I have to address this to Hitachi/CV support.

Userlevel 2
Badge +4

Yeah its tough to narrow down and as much as I like CV Support the Tech’s chaulked it up to Windows or the SAN and tapped out. Also WRT to the version my problem was worse on V11. Right now I only see the issue 1 a week or every 2 weeks versus walking up to a sea of failed backup copes so I’m living with it at the moment. If you figure it out let me know.

 

Userlevel 2
Badge +4

So setting the proxies at the instance level did not work on the second night. The troubled MA was allocated most of the load and froze up the VDS and the backup copies failed. Back to square one.

Thanks

Userlevel 2
Badge +4

Hi

I have read all the replies. Thank you. I was in the DC yestarday and did not reply but will do my best once I have had a chance to try some more things with Ben from CV support. Currently spreading out the schedules has helped. I’m seeing error about Mutiple LUNS causing issues during the snapshot mount on the Compellent. The cleanup tool mentioned that needs to be installed on the MA might be important here as we are still on V11 SP 16. I can see the dead LUNS in VMWare and when I do a rescan of storage they go away:

OS mount failed : [VMWare Mount snapshot failed [0xEC02ECC3:{VMwareSnapOSUtil::MountSnap(1841)/MM.60611-Error mounting the snapshot LUNs because there are multiple copies present.}] (MM.60611)]

Badge +15

Hi, to me the fact that you see multiple LUNs and dead paths has a lot to do with the MPIO software and the Dell Compellent Software I mentioned above. Check it out and let us know when you have a chance. Enjoy your weekend. 

Userlevel 7
Badge +23

@Neil Cooper , following up on this thread.  I can see in your case notes that you had some green backup activity and were investigating an Unkown Device issue in Device Manager, also that removing detailed snap option has significantly cut down our snap and backup copy down to literally minutes.

Is this issue now resolved?  If so, I’d like to srt one of the many helpful replies as the Best Answer.

Thanks!!

Userlevel 2
Badge +4

@s3narasi Output from the DevNodeClean

 

Userlevel 2
Badge +4

@s3narasi 

 

Userlevel 7
Badge +23

That’s awesome, @Neil Cooper !  Once you feel safe in the issue being resolved, feel free to mark one of the many helpful replies as the Best Answer!

Reply