Configuring DPM V2 Beta 2
To start protecting data after you install Microsoft System Center Data Protection Manager V2 Beta 2 (DPM), you must perform a series of required configuration tasks. You can also configure optional DPM features at this time, or you can wait and configure optional features at any time after you deploy DPM. Below are a few of the required tasks (Adding Disks to the Storage Pool and Configuring Tape Libraries). Agent deployments will be covered next week.
Getting Started with Configuring DPM
To configure Microsoft System Center Data Protection Manager V2 Beta 2 (DPM), you use DPM Administrator Console.
To open DPM Administrator Console
1. Log on to the DPM server under a domain user account that is a member of the local administrators group.
2. On the Start menu, point to All Programs, point to Microsoft System Center Data Protection Manager V2 Beta2, and then click Microsoft System Center Data Protection Manager V2 Beta2.
If it is available, double-click the Microsoft System Center Data Protection Manager V2 Beta2 icon on the desktop.
Required Configuration Tasks
Before you can start protecting data using Microsoft System Center Data Protection Manager V2 Beta 2 (DPM), you must complete the following configuration tasks:
· Add one or more disks to the storage pool.
Note: If you are using a single disk server you can create “Custom” volumes using the unallocated space on the disk. (Covered In Future Snips)
· Configure tape libraries and stand-alone tape drives if you want to protect data on tape.
· Install a protection agent on each of the servers that you want to protect. (Covered In Future Snips)
· Start and configure the Microsoft Windows SharePoint Services VSS Writer service (WSS Writer service), and provide farm administration credentials for the protection agent. (Covered In Future Snips)
Note: Perform this task only if you are protecting server farms on servers running Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007.
· Create one or more protection groups. (Covered In Future Snips)
Adding Disks to the Storage Pool
The storage pool is a set of disks on which the Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) server stores replicas and recovery points for protected data. Before you can start protecting data, you must add at least one disk to the storage pool. After configuration, you can add more disks to the storage pool. If you have a single drive system with a large amount of unallocated space, you can utilize the unallocated space to create custom volumes for your replica and recovery points. Additional details regarding custom volumes will be covered in future snips.
Note: DPM does not support USB/1394 disks.
DPM requires a disk that is dedicated to the storage pool for storing protected data and snapshots. DPM also requires some free space for the following as part of the initial installation of DPM:
· System files
· DPM installation files
· DPM prerequisite software
· DPM database files
v You can install DPM on the same volume that the operating system is installed on or on a different volume that does not include the operating system. However, you cannot install DPM on the disk that is dedicated to the storage pool.
v When you add a disk to the storage pool, DPM reformats the disk, which erases any data that the disk contains.
To add disks to the storage pool
1. In DPM Administrator Console, on the navigation bar, click Management, and then click the Disks tab.
2. In the Actions pane, click Add. The Add Disks to Storage Pool dialog box appears. The Available disks section lists the disks that you can add to the storage pool.
3. Select one or more disks, click Add, and then click OK.
Configuring Tape Libraries
You can add tape libraries and stand-alone tape drives to Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) to enable short-term and long-term data protection on tape. The tape libraries and stand-alone tape drives must be physically attached to the DPM server. The tape library can be direct SCSI attached or fiber channel attached (i.e. SAN). After you attach a new tape library or stand-alone tape drive to your DPM server, you must perform a Rescan operation before the DPM server can identify them. When you perform a Rescan operation, DPM examines the tape libraries or stand-alone tape drives that are attached to the DPM server and updates the information that is displayed on the Libraries tab in DPM Administrator Console. The Libraries tab displays each stand-alone tape drive, and each tape library and its drives.
You use the Rescan operation on the Libraries tab to check for and refresh the state of all new tape libraries and stand-alone tape drives when you make changes to your hardware.
Note: If the stand-alone tape drives listed on the Libraries tab in DPM Administrator Console do not match the physical state of your stand-alone tape drives. For example, if drives from a tape library are listed as stand-alone tape drives, or if a stand-alone tape drive displays incorrectly as a drive in a tape library, you need to remap the tape drive information.
Refer to "Remapping Tape Drives" in the Tape Library Modules for this training or in the "Library Maintenance" topic of the DPM Operations Guide.
To configure tape libraries
1. In DPM Administrator Console, on the navigation bar click Management, and then click the Libraries tab.
2. In the Actions pane, click Rescan. Rescan might take several minutes to complete. DPM will add any library jobs that begin during rescan to the queue until the Rescan operation is complete. If a library job is already in progress when the Rescan operation begins, the Rescan operation will fail.
Once the tape library (or standalone tape drive) is detected and configured by DPM, it is then available to be used when creating protection groups and recovery points.
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.
- Tom O'Malley
You wrote that it is possible to create "custom" volumes on a single-disk server.
Are there any How-Tos or ReadMEs covering this administrative task?
Or can you provide same information, please?
I've got the same question as Oliver. How to create a custom volume on a single disk server.
Can youpoint me in the right direction?