Forum Discussion

RichST71's avatar
RichST71
Level 2
13 years ago

Database Management job brings disk folders offline

I have just upgraded from Backup Exec from 2010 to 2012 and have been finding my backup to disk folders have been going offline for no apparent reason.  On investigation, I am seeing that there are event logs that show the Virtual Disk service restarting at 4AM, which coincides with time the disks go offline.

It looks like the Backup Exec Database Maintenance routine runs at 4AM - I am guessing that this is somehow causing the problem.  I cannot see how to modify the Maintenance routine, or why it would stop the Virtual Disk service.

Has anyone come across this before and if so, is there a resolution to it?

 

Thanks

Richard

2012
Backup and Recovery
Backup Exec
Backup Exec (media server only)
  • Cullen's avatar
    Cullen
    12 years ago

    It turns out it is not the database management job after all. Running the database job at any other time does not cause the drives to go offline, but the drives still go offline at 4AM. It took me about 5 hours to figure this one out. First, some info about my setup:

    2 identical Dell 2950 servers, Server 2008R2 (64-Bit), Backup Exec 2012 SP1a, 2 Identical Dell MD300 arrays, directly attached. The drives go offline on one server, but not the other

    The drives go offline 5 seconds after the database job ends at 4AM (04:00:11). It is usually the same drive that fails.

    The log files in C:\Program Files\Symantec\Backup Exec\Logs that are created when the management job runs or the services restart have a time stamp that matches the failure. The only OFFLINE error message is in the InitVDS log file, so it is the Virtual Disk Service Initialization job that causes the failure.

    The only difference between the two arrays I have is that the "Access" Virtual disk that gives access to the host group was using LUN 0, and not LUN 31 as specified by Dell, and was using the same LUN as one of the virtual disks. The backup servers are not live yet so I removed all of the virtual disks, hosts and host groups from the array and configured it again using the correct LUN for the "Access" disk. The drive no longer goes offline when the services are restarted. I believe the InitVDS job saw the access disk at LUN 0 and tried to initialize it. Now that it is not the first LUN, the job does not cause an error.

    Symantec needs to patch that discovery procedure to deal with the possibility that the access partition will be scanned and not crash if it is.

    I hope this helps you all and that this truly is the answer. It worked for me. I have a Case open with Symantec and I will pass this info on to them and hopefully they will put out a KB article on it.

    Maybe they will send me a check for the time I spent troubleshooting their product. Now they don't have to spend the time doing it! :)

    We will see if it goes offline at 4AM tomorrow morning. Cross your fingers....

    Good Luck!

18 Replies

Sort By
Show More
  • U645893's avatar
    U645893
    Level 3
    13 years ago

    Symantec did get back to me today, and told me that my issue is unrelated to Case 418-444-078, as my disk based storage goes off-line randomly, and is not associated with database maintenance activity.  Back to square one.

  • Nicolas_d2b's avatar
    Nicolas_d2b
    Level 4
    13 years ago

    Dear All

    I have te same issue on SAN disk with 2 storage device, one with deduplication and one with classic backup disk , and tape library on Fiber Channel...

    and another custumer with 2 NAS have the same issue.

    The auto discovery is checked, but on deduplication disk you don't have this check box

    So the solution, disable the database management, but it's not safe....

    I hope we gonna have a fix because it's very embarrasing.

    Regards

  • Justin2_0's avatar
    Justin2_0
    Level 2
    13 years ago

    Please see the following: http://www.symantec.com/docs/TECH189831

     

    If you are experienceing this issue please log a case with support and ask them to investigate your case using:

    Source ETrack
    Value 2800050
    Description

    CORE: B2D folders created on SAN drives (SAN with MultiPath) go offline when Backup Exec DB maintenance runs or if the Backup Exec services are restarted.

    Please note that disabling DB maintenance won't correct the situation, but changing the time of when it occurs will allow you to controll when goes offline.

  • U645893's avatar
    U645893
    Level 3
    12 years ago

    My issue is different.  My B2D folder goes off line randomly, at any time, once or twice a day, completely unrelated to DB maintenance jobs, backup jobs, or anything else.

  • Nicolas_d2b's avatar
    Nicolas_d2b
    Level 4
    12 years ago

    Some news....

    DB Mainetance scheduled to 8 PM. but Db maintenance disable, the disk gone off line a the time scheduled too...

    Magic....

    I Open a call now....

    Regards

     

  • Nicolas_d2b's avatar
    Nicolas_d2b
    Level 4
    12 years ago

    Thanks Justin 2.0

    So the resume about discussion with the support is :

    Disable the checkbox "db maintenance" doesn't works (In fack the maintenance still alive), it's gonna be fixed soon by patch.

    The Script you send works fine...but i don't know why I could not mark your post as solution ;o(

    But Not for Déduplication disk......

    Thanks a lot.

    Best Regards.

  • Cullen's avatar
    Cullen
    12 years ago

    It turns out it is not the database management job after all. Running the database job at any other time does not cause the drives to go offline, but the drives still go offline at 4AM. It took me about 5 hours to figure this one out. First, some info about my setup:

    2 identical Dell 2950 servers, Server 2008R2 (64-Bit), Backup Exec 2012 SP1a, 2 Identical Dell MD300 arrays, directly attached. The drives go offline on one server, but not the other

    The drives go offline 5 seconds after the database job ends at 4AM (04:00:11). It is usually the same drive that fails.

    The log files in C:\Program Files\Symantec\Backup Exec\Logs that are created when the management job runs or the services restart have a time stamp that matches the failure. The only OFFLINE error message is in the InitVDS log file, so it is the Virtual Disk Service Initialization job that causes the failure.

    The only difference between the two arrays I have is that the "Access" Virtual disk that gives access to the host group was using LUN 0, and not LUN 31 as specified by Dell, and was using the same LUN as one of the virtual disks. The backup servers are not live yet so I removed all of the virtual disks, hosts and host groups from the array and configured it again using the correct LUN for the "Access" disk. The drive no longer goes offline when the services are restarted. I believe the InitVDS job saw the access disk at LUN 0 and tried to initialize it. Now that it is not the first LUN, the job does not cause an error.

    Symantec needs to patch that discovery procedure to deal with the possibility that the access partition will be scanned and not crash if it is.

    I hope this helps you all and that this truly is the answer. It worked for me. I have a Case open with Symantec and I will pass this info on to them and hopefully they will put out a KB article on it.

    Maybe they will send me a check for the time I spent troubleshooting their product. Now they don't have to spend the time doing it! :)

    We will see if it goes offline at 4AM tomorrow morning. Cross your fingers....

    Good Luck!

  • strger2012's avatar
    strger2012
    Level 3
    12 years ago

    I too have the problem with offline disks at 4AM.

    Any patches from Symantec available?