-L] TSM for VE sizing vs standard incremental forever
Hi All
I've been asked to do some ballpark sizing for a major rework of a TSM
environment. Clients are linux and Windows under Vmware
This customer has been using standard BA client backups up until now, ie
incremental forever, and the new
You noted that your back end will be all tape; be sure you read the
requirements for tape section in the VE book. The metadata has to be
split out and stay on disk.
This is probably worth highlighting. TSM for VE writes control data to the
Management Class defined by the Vmctlmc client
Hi All
I've been asked to do some ballpark sizing for a major rework of a TSM
environment. Clients are linux and Windows under Vmware
This customer has been using standard BA client backups up until now, ie
incremental forever, and the new env will be TSM for VE with the backend
being tape
-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven
Harris
Sent: Wednesday, May 15, 2013 11:20 AM
To: ADSM-L@VM.MARIST.EDU
Subject: TSM for VE sizing vs standard incremental forever
Hi All
I've been asked to do some ballpark sizing for a major rework of a TSM
%. The average is around
8-10%.
Ray Storer
NIBCO INC.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven
Harris
Sent: Wednesday, May 15, 2013 5:20 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM for VE sizing vs standard incremental forever
Hi
-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven
Harris
Sent: Wednesday, May 15, 2013 5:20 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM for VE sizing vs standard incremental forever
Hi All
I've been asked to do some ballpark sizing for a major rework of a TSM
