So, the doc suggests that you shouldn't use this for FILE devclasses.
Anybody know anything about why?
Similarly, it talks about that feature being good for VTL applications,
but is quiet about TSM virtual volumes. Seems odd; the dedupe
optimization would seem to be relatively generic, if it's no
jk bericht -
Van: Allen S. Rout
Verzonden: dinsdag 4 juni 2013 20:53
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] DB backups in v6 land. And, BACK DB dedupdev=yes... ?
So, the doc suggests that you shouldn't use this for FILE devclasses.
Anybody know anything about why?
Similarly, it t
On 06/05/2013 02:10 AM, Karel Bos wrote:
> Hi,
>
> I think doc stated not to use dev=file shared=yes for TSM db backups.
This, I totally get. And I also totally get why you wouldn't want to
use TSM dedupe on a FILE devclass from which you expect to do a DB restore.
They fall into the same class
rds,
Karel
- Oorspronkelijk bericht -
Van: Allen S. Rout
Verzonden: dinsdag 4 juni 2013 20:53
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] DB backups in v6 land. And, BACK DB dedupdev=yes... ?
So, the doc suggests that you shouldn't use this for FILE devclasses.
Anybody know any
Karel,
>And I also totally get why you wouldn't want to use TSM dedupe on a FILE
devclass from which you expect to do a DB restore.
You don't enable dedupe on the deviceclass level but on the storagepool
level so a DB backup to a device class that is also used for a deduded
storagepool is no prob
