Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
Modify Protection Group - List Available Members on Primary DPM Server taking VERY long time

Answered Modify Protection Group - List Available Members on Primary DPM Server taking VERY long time

  • Thursday, May 10, 2012 3:52 AM
     
     
    Sign In to Vote
    0

    Hi All,

    we have a DPM Setup with Primary and Secondary Servers.

    Usually the Primary and Secondary Servers are located on separate subnets and physical locations, connected via a 100Mb connection.

    When we go to modify or create a Protection Group on the Secondary DPM Server, and we expand the Primary server to list the Available members, this list takes a very long time to populate - at least 15mins.

    Once the list is populated and we expand any of the member servers, this then takes equally as long to list the items available to select.

    DPM was working flawlessly and has since stopped working so well in the previous months.

    First I noticed that all the Group Members in the Protection Tab would show "Agent not reachable" -  although it would say this for one item from a server but then there were other items from the same server that were "OK".

    I have disabled IPv6 on both DPM servers, removed the primary server from the secondary and re-added it.

    At first I thought this was a networking issue, but as I removed the different components of networking equipment ending up with just a router and two servers the problem still persists.

    SQL Issues??

    Cheers

     

All Replies

  • Thursday, May 10, 2012 10:13 PM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    Yes, it is possible that the SQL DB Indexes are fragmented.  To see if that is a problem this Script will list all indexes that are fragmented > 30%

    NOTE: Some indexes are not defragable, so may not show improvement after defragging.

    USE [DPMDB]
    SELECT OBJECT_NAME(object_id),index_id, avg_fragmentation_in_percent, fragment_count, page_count, avg_fragment_size_in_pages, index_type_desc
    FROM sys.dm_db_index_physical_stats(DB_ID(), Null,Null,Null,Null)
    WHERE avg_fragmentation_in_percent > 30
    AND index_type_desc IN('CLUSTERED INDEX', 'NONCLUSTERED INDEX')
    order by avg_fragmentation_in_percent desc

    The below script will defrag the offending indexes.  You MUST stop and disable the MSDPM service.

    -- Stop and disable msdpm service before using the REBUILD clause

    USE [DPMDB]
    EXEC sp_MSforeachtable @command1="print '?'", @command2="ALTER INDEX ALL ON ? REBUILD WITH (ONLINE=OFF)"

    Let me know if that improved things.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.