One thing I want to warn about using client encryption is that there are
two flavors:
- standard encryption, in which the client prompts for a password
- transparent encryption, in which the client generates the key and then
uses the server as an external key manager

If you decide to implement client encryption, be sure to use standard
encryption because transparently encrypted files are not allowed in backup
sets.  And, in fact, the checks are at the filespace level, so if there
are any files in the filespace that have been transparently encrypted,
then GENERATE BACKUPSET will reject the entire filespace.

Ken Hannigan
Tivoli Storage Management Development

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/01/2009
11:10:09 AM:

> >> On Thu, 30 Apr 2009 21:22:00 +0530, Sachin V Chaudhari1
> <schaudhari AT IN.IBM DOT COM> said:
>
>
> > But if I enable client encryption for taking flat file backup, then
> > how will I restore the backup set data. At the time of backup set
> > restoration will it ask me to put the same passport which I used it
> > for flatfile backup.
>
> > As I know it will prompt us to enter the password for normal restore
> > process, but I am not sure whether it will for backup set
> > restoration if encryption is enable for file system backup.?
>
>
> I suggest you try it. I have expectations about what will happen, but
> have never done it myself.  It should be an easy exercise.
>
> I would be astonished to find that there was no way to restore a
> backupset which held encrypted data.
>
>
> - Allen S. Rout