Bad news Steven, if you are using VMWare virtualization
According to wikipedia http://en.wikipedia.org/wiki/VMware_ESX ESX V3
service console runs linux based on Red Hat EL3. TSM 5.5 clients are
supported on RHEL4 and 5. 5.4 supports RHEL3 using the 5.3 special
client extension. VMWare ESXi
Running TSM 5.5 on z/OS.
Run nightly backups to disk storage pools, then migrate those to tape
the next day.
Last night, one of our disk storage pools filled up due to a mass dump
of data on one of the clients being backed up to that pool
The high and low migration limits on this pool were se
5.4.1 is the version that came with TSM 5.5 Extended Edition media
packs.
See Ya'
Howard
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
> Of David E Ehresman
> Sent: Wednesday, September 30, 2009 12:27 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject
>
> See answers below.
>
>
> My questions:
>
> 1) Since this is an auto migration process kicked off by the thresholds,
> does it have to complete before any new migration processes can start?
>
Yes (for the same pool)
> Is there any way to change/override that if that is the case?
You can try
You will probably see that only one node's data resides in the disk pool
still... I've noticed TSM only firing off a single migration process per
node for any given storage pool so even if you set migpr=10 and high=1 low=0
you'll still only see a single migration process if you have data from only
Correction:
> 3) Will this auto migration session complete when it gets to the lower
> threshold (60%) or will it keep going until the pool is empty?
>
It will complete when it gets to the low threshold, or when it has migrated
all the data from the largest client.
On Thu, Oct 1, 2009 at 9:52
That last migration process is probably working on the data for a
single nodename, where there can be no more than one migration process
for one nodename.
It may be that there is still a lot of new data entering that disk
pool such that migration is still going on; or, the tape/drive has
issues w
Richard, Wanda and Dwight,
Thanks for your responses and info. That clarifies the situation for me.
Much appreciated!
Kevin Kinder
State of WV
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Dwight Cook
Sent: Thursday, October
You may run into a problem if there is a vm migration occuring and at the same
time the migrating node is backing up to the first proxy server. The second
proxy could attach to the new vm and try backing it up as well. Not sure what
would happen then.
Johnny Lea CNE
Disaster Recovery Anal
Hi list,
When trying to restore a mailbox using the TDP for Exchange GUI I am getting
the following error:
"ACN5798E MS Exchange API HRESERESTOREOPEN() failed with HRESULT: 0xc7ff0bbd
-The path provided for restore log files is invalid."
I´ve searched the IBM Support pages for this particular
Mario,
Trying setting the
TEMPLOGRestorepath
configuration option to a valid location with enough room to hold all of
the restored logs.
Example:
TDPEXCC SET TEMPLOGRestorepath=F:\TEMP
Thanks,
Del
"ADSM: Dist Stor Manager"
If I have a exclude.fs statement in a clientoptset, can I nullify its effect in
a client's inclexcl file. If so, how?
David
David,
You will need to update the client option in your clientoptset with
FORCE=NO to allow the client to override the value.
BERTAUT TCHUISE
TSM/NetApp Storage Administrator
Legg Mason Technology Services
*410-580-7032
btchu...@leggmason.com
-Original Message-
From: ADSM: Dist Stor Ma
Once that is done, what statement in the local inclexcl file would override it?
>>> "Tchuise, Bertaut" 10/1/2009 2:19 PM >>>
David,
You will need to update the client option in your clientoptset with
FORCE=NO to allow the client to override the value.
BERTAUT TCHUISE
TSM/NetApp Storage Administ
Include.fs
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
David E Ehresman
Sent: Thursday, October 01, 2009 2:30 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] exclude.fs
Once that is done, what statement in the local inclexcl file would
ove
INCLEXCL is an additive option such that Force does not pertain.
Richard Sims
On Oct 1, 2009, at 2:19 PM, Tchuise, Bertaut wrote:
David,
You will need to update the client option in your clientoptset with
FORCE=NO to allow the client to override the value.
BERTAUT TCHUISE
TSM/NetApp Stora
When I put an exclude.fs (forec=no) in the clientopt and an include.fs in the
client inclexcl file, I get
ANS1149E No domain is available for incremental backup. The domain may be empty
or all file systems in the domain are excluded.
when trying to do an incremental of the filesystem.
/cdcopy
Richard is right, I overlooked the inclexcl exclusion with the Force
parameter.
Force
Specifies whether the server forces the client to use the option set
value. The value is ignored for additive options, such as INCLEXCL
and DOMAIN. The default is NO.
Thus for any inclexcl option in yo
On 1 okt 2009, at 20:35, Tchuise, Bertaut wrote:
Include.fs
when was this introduced in TSM? ;-)
--
Met vriendelijke groeten/Kind regards,
Remco Post
I'm finding that what I know about how the DB works in 5.5 doesn't
really equal how it works in 6.1. On a Linux box I brought up to migrate
clients to a 6.1 server I created a 20GB log and 100GB DB. There 'will
be' about 150 nodes moved to this instance but currently about 20 are
backing up. My 5.5
Hi Geoff,
What I have seen is following.
If you have a basic TSM 6.1 installation I normally count at least TSM 5.5 DB x
3 to be sure.
If I turn on DEDUP on TSM 6.1 I count TSM 5.5 DB x 6.
And yes the DB will be large for you.
The only thing I struggle with right now is how much Arch Log and Act
21 matches
Mail list logo
