Installing DPM V2 Beta 2
A Microsoft System Center Data Protection Manager 2007 (DPM) installation involves installing the DPM prerequisite software and the DPM application. The DPM Setup Wizard guides you through the process of specifying the DPM installation settings, and it automatically installs or provides links to install the prerequisite software as part of the integrated DPM installation process. Throughout the installation process, DPM Setup provides status on the installation progress.
Notes and Considerations:
· Microsoft does not allow the distribution of updates when included in other applications. This is a safeguard just in case a regression is identified in a component that was included and installed as part of the application. Requesting certain prerequisites to be met prior to or during the installation by using links to the updates resolves this issue.
· The DPM Setup Wizard is designed to install DPM prerequisite software from the DPM download package. If you want to use retail copies of one or more of the prerequisite products for your DPM installation, install the products manually before you start the DPM Setup Wizard. You can install DPM and its prerequisite software either from the DPM download package or from a network share to which you have copied the contents of the DPM download package. If you want to install from a share, the share must duplicate the exact directory structure of the DPM download package.
· If you choose to install DPM or prerequisite software products from a shared folder, DPM Setup adds the Universal Naming Convention (UNC) path of the shared folder to the Internet Explorer local intranet security zone for the duration of the installation.
· Install from a shared folder only if the share is hosted on a trusted site.
· DPM supports 32-bit and x64-bit operating systems. You can install the DPM 32-bit version only on a 32-bit operating system and the DPM 64-bit version only on an x64-bit operating system.
To install DPMV2 Beta2:
1. Log on to the DPM server using a domain user account that is a member of the local administrators group.
2. On Microsoft Connect, on the “Welcome to the Data Protection Manager Beta Program” page, click the download page for the operating system on which you are installing DPM.
3. Download the DPMV2Beta2 download package, and then double-click Setup.exe.
If you are installing DPM from a network share, navigate to the installation share, and then double-click Setup.exe in the root folder of the share.
Note: DPM requires at least 2-3GB of free space on the volume where the product will be installed. This space is used as a temporary storage location. If DPM is installed over a network all the installation files will be copied to a hidden share located at C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\MTA\MTATempStore$. This is the default location and may vary if DPM is installed in an alternate location. To identify the location of this share you can use “net share” from a command prompt.
The default location for the installation of the binaries used by DPM is C:\Program Files\Microsoft Data Protection Manager\DPM\bin. Most of the files in this location are loaded by the agent service and may be used for specific data sources or all. Additional tools used to manage your DPM environment (e.g. DpmSync.exe, DpmBackup.exe…etc) are also located in this folder.
4. On the “Microsoft System Center Data Protection Manager V2 Beta2” screen, click “Install Data Protection Manager”.
5. On the “Microsoft Software License Terms” page, review the license agreement. If you accept the terms, click “I accept the license terms and conditions” and then click OK.
· You can copy and paste the license agreement into a text editor such as Notepad for printing. After installation is complete, you can access the license agreement from DPM Administrator Console by clicking the product information icon on the navigation bar.
· DPM installs Microsoft .NET Framework 2.0 if it has not already been installed.
6. On the “Welcome” page, click Next. DPM begins a prerequisites check for all required hardware and software.
7. On the “Prerequisites Check” page, wait while DPM Setup checks the system to verify that it meets software and hardware requirements.
· If all required components are present, DPM Setup displays a confirmation. Click Next to continue.
· If one or more required or recommended components are missing or noncompliant, Setup displays a warning or error message.
Warning: Indicates that a recommended component is missing or noncompliant. Review the warning and determine whether to resolve the issue now or continue with the installation. If you choose to continue with the installation, plan to resolve the issue as soon as possible.
Error : Indicates that a required component is missing or noncompliant. You must exit the wizard and resolve the error before you can continue with the installation.
8. On the “Product Registration” page, enter your registration information and then click Next.
9. On the “Installation Settings” page, in the “DPM Program Files” section, accept the default folder or browse to the folder in which you want to install DPM.
· You can install DPM only on a local drive, and you cannot install it in read-only folders, hidden folders, or directly to local Windows folders such as Documents and Settings or Program Files. (DPM can, however, be installed to a subfolder of the Program Files folder.)
· The installation partition must be formatted with the NTFS file system. To simplify recovery in the event of system partition failure, install DPM to a partition that is separate from the system partition.
10. On the “Installation Settings” page, in the “SQL Server settings” section, specify whether you want to install the MS$DPMv2Beta2$ instance of Microsoft SQL Server from the DPM download package or on a local or remote instance of SQL Server that already exists.
· To use an existing instance of SQL Server with the DPM installation, the server running SQL Server and the DPM server must be located in the same domain.
· DPM Setup creates the DPMDBAdministrators$DPM< computer name > and DPMDBReaders$DPM< computer name > local groups on the remote instance of SQL Server. DPM administrators must be added to these groups to use the remote instance of SQL Server.
Note the following:
The remote instance of SQL Server must be running IIS 6.0 and SQL Server 2005 Standard or Enterprise Edition with SP1, including the following components:
· SQL Server Database Engine
· Reporting Services
We recommend you use the following settings on the remote instance of SQL Server:
· Use the default failure audit setting.
· Use the default Windows Authentication mode.
· Assign a strong password to the sa account.
· Enable password policy checking.
· Install only the SQL Server Database Engine and Reporting Services components.
· Run SQL Server by using the least-privileged user account.
11. On the “Installation Settings” page, the “Space requirements” section displays space availability on the specified destination drives. If you choose to change the installation folders, verify that the selected drives have enough space for the installation. Following are the minimum hardware requirements for the DPM server:
· System drive: 2650 MB
Note: This system drive disk space requirement is necessary if you chose to install the instance of SQL Server from the DPM download package. If you are using an existing instance of SQL Server, this disk space requirement is considerably less.
· Program files drive: 620 MB
· Database files drive: 900 MB
A. To change the specified installation locations, click Change.
B. To accept the specified installation locations, click Next.
If you choose to use an existing instance of SQL Server instead of installing it from the DPM download package, the “SQL Settings” page appears where you specify the name of the existing instance of SQL Server and the appropriate administrator credentials.
On the “SQL Settings” page, type the name and password of the existing instance of SQL Server 2005 that you want to use.
If SQL Server Reporting Services is installed on the remote SQL Server, DPM Setup will use that Reporting Service. If SQL Server Reporting Services is not installed on the remote computer running SQL Server, you must install and configure the service on the remote computer running SQL Server before continuing with DPM Setup.
A. Click Next.
12. On the “Security Settings” page, specify and confirm a strong password for the restricted MS$DPMv2Beta2$ and DPMR$DPMDOC local user accounts.
· For security purposes, DPM runs SQL Server and the SQL Server Agent service under the MS$DPMv2Beta2$ account, which DPM Setup creates during DPM installation. To securely generate reports, DPM creates the DPMR$DPMDOC account.
· A strong password is typically defined as a password that is at least six characters long, does not contain all or part of the user’s account name, and contains at least three of the following four categories of characters: uppercase characters, lowercase characters, base 10 digits, and symbols (such as !, @, #).
· The password that you specify for these accounts does not expire.
13. On the “Customer Experience Improvement Program” page, click Next.
14. On the “Summary of Settings” page, review the summary of installation settings. To install DPM using the specified settings, click Install. To change the settings, click Back.
15. If prompted, insert the Windows Server 2003 product CD and then click OK.
Note: Setup prompts for the Windows Server 2003 CD only if IIS 6.0 or SIS are not already installed on the DPM server.
16. When installation is complete, the “Installation” page displays the installation status. Select your startup options, and then click Close. You will need to reboot the DPM 2007 server before launching the DPM Administrator Console for the first time.
In case of Installation Error:
There can be situations during the installation DPM 2007 where you may experience a failure that causes the installation to halt and actions need to be taken to address the problem. When the installation fails it will display a reason (“Error” tab) for the failure and some actionable items that can be performed. To get additional details about what task was being performed just prior to the failure you can leverage the DpmSetup.log file located at C:\Documents and Settings\All Users\DPMLogs folder which is the default location.
The DpmSetup.log contains all the steps being performed during the installation of Data Protection Manager 2007 in sequential order. If the DPM installation does fail the DpmSetup.log will contain the same error that was displayed when the installation halted and all tasks performed just prior to the failure. Always leverage this log for additional details about what may have occurred just prior to the failure if the recommended actions do not resolve the installation issue. To quickly identify the error within the DpmSetup.log file you need to scroll to the end of the log and work up since each step is in chronological order. Additionally, depending on the failure the other logs that reside in this folder and the event logs may be useful in isolating an installation issue.
NOTE: I like to give a special thanks to the Content Team for supplying the detailed DPM documentation which makes these snips easily available for distribution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.