RIVERBED WHITEWATER QUICK START GUIDE
© 2012 Riverbed Technology. All rights reserved.
31
Maximum number of scratch volumes
can be set to any value allowed by Tivoli Storage Manager. If you wish to limit
the total amount of data stored to the cloud by Tivoli Storage Manager, set a maximum scratch volume limit which will
accomplish this size requirement. For example, if you wish to only use a maximum of 40TB of space in the cloud and
maximum volume capacity is set to 20GB, then the maximum number of scratch volumes value should be set to
40,000GB / 20GB = 2,000.
Number of days before an empty volume is reused
should be set to 0 (default). This will immediately allow a volume
to be reused for holding new backup data.
Figure 38 TSM Storage Pool Identify Duplicates
When creating a Whitewater based storage pool, leave the
Identify the duplicate data in this storage pool
checkbox
unchecked as shown in Figure 5, and click
Next
and
Finish
to complete the wizard.
TSM Storage Pool Setup
There are 3 ways to setup Whitewater appliances with TSM:
1. Setup the Whitewater appliance as a primary sequential storage pool behind the existing disk storage pool. TSM uses the
existing disk storage pool for fast writes for backups, and then migrates the data during the day to the Whitewater appliance. This
method separates the network requirements of backups from the migration operations that move data to the Whitewater
appliance. The Whitewater appliance can also serve as an offsite copy backup, but without having to implement a TSM copy
storage pool configuration, saving time and resources on the TSM server.
2. Setup the Whitewater appliance as a copy storage pool. Similar to method 1, there will be no contention for network resources
between backups and the copy storage pool operations to the Whitewater appliance, but in this setup the Whitewater serves only
as the offsite copy. TSM Administrators will still need to configure a local onsite storage pool behind their primary disk pool.
3. Setup the Whitewater appliance as the primary disk storage pool. This is not recommended for most scenarios as the
Whitewater appliance will likely be unable to keep up with the write requirements for many simulatenous backup streams, and the
TSM server network resources will be in contention for both inbound backup and outbound Whitewater appliance activity.
It is possible to configure the Whitewater gateway to be the primary and copy storage pool target (for example, if combining
methods 1 and 2 above), but note that this will require additional network and cloud resources to perform, as well as reduce the
amount of usable cache space since the Whitewater cache will have to make multiple references for each type of operation.
