Well, TSM does support encryption and works well as its own key manager.
However, this does not encrypt the TSM database. For this, you will need
an external key manager to encrypt database tapes. Of course, this
starts the whole discussion of then how do you backup the key manager
that's
Scratch mount does not have to equal the # of the tapes in the library.
It's main purpose is to control the # of tapes a storage pool can
consume.
- Chris
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Ramiro Ruiz
Sent: Monday, November 24, 2008
Since there isn't a perfect solution for backing up VMs, you can choose
from one of several options.
a) Treat your VMs as physical servers, TSM client per server.
b) VCB incremental backup integration with TSM. The major drawback here
is it doesn't grab Windows System State.
c) VCB full image
First make sure your device class has FORMAT specified as DRIVE. If the
drive is enabled for compression (check via your library's web GUI),
then you can expect anywhere from 800GB to 1.6TB of utilization. With
mixed data types I typically see ~1.2TB.
One other option to set is the
You will have to decide which one of the instances will keep the
original copypool. For the other instance(s), blow away the offsite
copypool and generate a new one with BACKUP STGPOOL Primary Pools New
Copypool Name.
I would suggest assigning the current copypool to the instance which
owns the
