none
DPM2010 takes long time to first startup. RRS feed

  • Question

  • DPM2010 installation on a HP DL380 G6, 6GB memory, HP MSL6030 tapelibary with 2x LTO3 tapedrives, HP MSA2312 diskcabinet sata attached for DPM diskbackup of 3TB.
    I reinstalled the server with W2008R2 x64 and restored the DPM2010 database, about 5Gb. HP Proliant Support Pack 8.60 installed. No other software installed, no anti-virus software.
    With this installation and the former installation of this DPM2010 server, it takes more than a minute to start DPM2010.
    When I start the program, the topmenu in the grey screen is visible and the action pane on the right. After 2minutes and 5 seconds (see it with the Windows Problem Step Recorder) appears the DPM2010 logo. Quickly after that the program is started.

    What can done about it to make it starting much faster?

    Fred 

    Friday, November 12, 2010 10:07 AM

Answers

  • Today both starting up and the powershell command "Get-ProductionServers" are fast. Don't know what the difference is.

    Still want to delete the obsolete server in the list from "Get-ProductionServers".

    • Marked as answer by Fred Ebben Wednesday, November 17, 2010 7:17 AM
    Wednesday, November 17, 2010 7:17 AM
  • Hi Fred,

    you cannot delete these servers. DPM keeps knowledge on those around in case they return, likewise on volumes that are or were part of storage pool. These don't bother you, also do no show-up in UI, forget about these.

    It seems you had a temporary network/resolving related issue but still could have been many things. Nothing we can do at the moment. If it returns I recommend to open a service request as this type of issue is hard to resolve in a forum setting.


    \R2 This posting is provided "AS IS" with no warranties, and confers no rights
    • Proposed as answer by Ruud Baars [MSFT] Wednesday, November 17, 2010 10:44 AM
    • Marked as answer by Fred Ebben Thursday, November 18, 2010 6:39 AM
    Wednesday, November 17, 2010 10:43 AM

All replies

  • Hi,

    I take it you have existing protection groups, hence restored DPMDB to get that back, good.
    Did you perform a "DPMSYNC -sync" that needs to be done after each good DPMDB restore?
    Just want to be sure restored DPMDB and existing storage pool volumes (+shadow copies) are in sync which could cause delays.


    \R2 This posting is provided "AS IS" with no warranties, and confers no rights
    Sunday, November 14, 2010 10:43 AM
  • Hi,

    I did perform a DPMSYNC -sync.
    Could it maby something to do with DNS?
    The server is a datacentre, the servers are in a office. There's a 100Mb link between them.

    Fred

    Monday, November 15, 2010 6:58 AM
  • Could be, as a quick test time how long "Get-ProductionServers" takes to complete.

     


    \R2 This posting is provided "AS IS" with no warranties, and confers no rights
    Monday, November 15, 2010 7:10 AM
  • That takes indeed also a long time. It displays 35 servers, 18 servers are marked as deleted. How can I delete the deleted servers in this list?

    On a other DPM2010 server, similar setup/hardware/tapelibary, it's displayed immediatley, but are only 10 servers, no deleted servers in this list.

    Server Name         Cluster Name        Domain              Protection State
    -----------         ------------        ------              ----------------
    SERVER01                                domainname.local     HasDatasourcesPr...
    SERVER02                                domainname.local     HasDatasourcesPr...
    SERVER03                                domainname.local     HasDatasourcesPr...
    SERVER04                                domainname.local     Deleted
    SERVER05                                domainname.local     HasDatasourcesPr...
    SERVER06                                domainname.local     Deleted
    SERVER07                                domainname.local     HasDatasourcesPr...
    SERVER08                                domainname.local     HasDatasourcesPr...
    SERVER09                                domainname.local     Deleted
    SERVER10                                domainname.local     HasDatasourcesPr...
    SERVER11                                domainname.local     Deleted
    SERVER12                                domainname.local     Deleted
    SERVER13                                domainname.local     Deleted
    SERVER14                                domainname.local     HasDatasourcesPr...
    SERVER15                                domainname.local     Deleted
    SERVER16                                domainname.local     Deleted
    SERVER17                                domainname.local     HasDatasourcesPr...
    SERVER18                                domainname.local     HasDatasourcesPr...
    SERVER19                                domainname.local     Deleted
    SERVER20                                domainname.local     Deleted
    SERVER21                                domainname.local     Deleted
    SERVER22                                domainname.local     HasDatasourcesPr...
    SERVER23                                domainname.local     Deleted
    SERVER24                                domainname.local     Deleted
    SERVER25                                domainname.local     HasDatasourcesPr...
    SERVER26                                domainname.local     Deleted
    SERVER27                                domainname.local     Deleted
    SERVER28                                domainname.local     HasDatasourcesPr...
    SERVER29                                domainname.local     Deleted
    SERVER30                                domainname.local     HasDatasourcesPr...
    SERVER31                                domainname.local     HasDatasourcesPr...
    SERVER32                                domainname.local     Deleted
    SERVER33                                domainname.local     Deleted
    SERVER34                                domainname.local     Deleted
    SERVER35                                domainname.local     NoDatasourcesPro...


    PS C:\>

    PS C:\> Remove-ProductionServer.ps1
    DPMServer:: BACKUP
    PSName:: SERVER02

    There is failure while removing production server
    C:\Program Files\Microsoft DPM\DPM\bin\Remove-ProductionServer.ps1 : DPM was un
    able to remove the protected computer SERVER02.
    At line:1 char:28
    + Remove-ProductionServer.ps1 <<<<
        + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep
       tion
        + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
       n,Remove-ProductionServer.ps1

    Make sure that the protected computer is attached to the DPM server. If the prot
    ected computer is in the Active directory domain, make sure that you have provid
    ed the correct fully qualified domain name (FQDN) of the protected computer. If
    WWFS2 is a workgroup computer configured to use NETBIOS, specify the NETBIOS nam
    e. Otherwise specify the DNS name of the workgroup computer.
    PS C:\> Remove-ProductionServer.ps1\
    The term 'Remove-ProductionServer.ps1\' is not recognized as the name of a cmdl
    et, function, script file, or operable program. Check the spelling of the name,
     or if a path was included, verify that the path is correct and try again.
    At line:1 char:29
    + Remove-ProductionServer.ps1\ <<<<
        + CategoryInfo          : ObjectNotFound: (Remove-ProductionServer.ps1\:St
       ring) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException

    PS C:\>

    Monday, November 15, 2010 11:36 AM
  • Today both starting up and the powershell command "Get-ProductionServers" are fast. Don't know what the difference is.

    Still want to delete the obsolete server in the list from "Get-ProductionServers".

    • Marked as answer by Fred Ebben Wednesday, November 17, 2010 7:17 AM
    Wednesday, November 17, 2010 7:17 AM
  • Hi Fred,

    you cannot delete these servers. DPM keeps knowledge on those around in case they return, likewise on volumes that are or were part of storage pool. These don't bother you, also do no show-up in UI, forget about these.

    It seems you had a temporary network/resolving related issue but still could have been many things. Nothing we can do at the moment. If it returns I recommend to open a service request as this type of issue is hard to resolve in a forum setting.


    \R2 This posting is provided "AS IS" with no warranties, and confers no rights
    • Proposed as answer by Ruud Baars [MSFT] Wednesday, November 17, 2010 10:44 AM
    • Marked as answer by Fred Ebben Thursday, November 18, 2010 6:39 AM
    Wednesday, November 17, 2010 10:43 AM