RIVERBED WHITEWATER QUICK START GUIDE
© 2012 Riverbed Technology. All rights reserved.
36
Where the parameters are provided as shown in the following Table 1
Parameter
Description
num-days <number of days>
Filters the data retrieved by number of last-modified days.
pattern <pattern>
Filters the data retrieved by the pattern you specify.
Recursive
Enables the data to be prepopulated in subdirectories under a
given
directory.
Table 1 Datastore Prepop Command Parameters
Refer to the
Whitewater Users Guide
for further details on this command.
Note
: If the Whitewater gateway storage capacity is less than the space used in the cloud, you can still initiate the recovery
process. However, in this case the Whitewater gateway will only recover as much actual data as the size of its storage. If the
recovery process attempts to bring back more data than the disaster recovery Whitewater can handle, then the recovery process
might fail. Virtual Whitewater for example can store up to 2 TB of cloud data. For more details on Whitewater gateway sizes, see
the
Whitewater Installation Guide
.
At this point the Whitewater Recovery procedure is complete, now you need to recover the TSM server.
TSM Server Recovery
After the Whitewater gateway has been recovered you need to install and configure the TSM server. The below procedures
assume that you are using TSM Disaster Recovery Manager (DRM), and have taken appropriate TSM server database backups.
Refer to the TSM Disaster Recovery redbook available at redbooks.ibm.com for further details.
1. Install TSM server to a new host system at the DR site. Make sure that the installation and configuration of the TSM server db,
log, and disk volumes is the same as in the previous production site, and that the DRM files are split up in preparation for disaster
recovery. Several of the DRM files can help you identify the paths for each of the above items.
2. Edit the DRM file
DEVICE.CONFIGURATION.FILE
using a text editor and adjust the Whitewater device class name to reflect
the new IP addressing of the Whitewater interfaces available at the DR site, as shown in Figure 43.
Figure 43 Device Configuration File
3. If the Whitewater appliance at the production site was used as a primary storage pool with TSM, edit the DRM file
PRIMARY.VOLUMES.DESTROYED.MAC
(Figure 44) and remove lines that refer to the Whitewater based volumes. Since the
Whitewater appliance at the DR site will have recovered the data from the cloud provider, there will be no destroyed volumes that
DRM will have to report to TSM, and they will be available when TSM is brought up.