Hello Andy,
thanks for sharing that with us. It was a pleasure to read. There are many
information worth having a look at.
Thanks for your hint.
Marcus
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von
Andrew Raibeck
Gesendet: Dien
Try with options "wait=yes preview=yes"
Grigori G. Solonovitch
Senior Systems Architect Ahli United Bank Kuwait www.ahliunited.com.kw
Please consider the environment before printing this E-mail
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
We have implemented TSM Client 6.4.0/TDP for Exchange 6.4.0 for Exchange 2010
(DAG configuration ) recently.
It was not easy - a few SRs to IBM and Microsoft have been raised.
Implementation was quite painful, but final result is good.
Grigori G. Solonovitch
Senior Systems Architect Ahli United
Grant,
If you care to script, do daily:
Select new volumes assigned to pools in last 24 hours.
(Maybe search actlog for ANR1340I messages.)
Filter for volumes in pools with collocate (NODE or GROUP).
For each volume check volumeusage for any nodes that do not belong.
Assume the first node belon
I understand that getting a good backup is the most important, but when
you offer a feature that is "best efforts" with no way to verify, why
have the feature?
eg
TSM will use "best efforts" to do a backup of a client.
As you know there are times when for one reason or another a backup
cannot be
If you absolutely need for nodes to be isolated on their own media, why aren't
they in their own individual domains which point to their own storage pools,
all of which might share a library?
Frankly, I like that TSM will override collocation preferences when its at
MAXSCR for volumes in a po
Hello
We use collocation to segment data into collocation groups and nodes,
but recently found that collocation is on a "best efforts" basis and
will use any tape if there is not enough space.
I understand the theory behind this but it does not help with compliance
requirements. I know that we s
Back in the day, it almost always used to be a duplex mismatch. "Get off
my lawn!" :-)
On 4/16/2013 6:36 AM, Zoltan Forray wrote:
But, how do you address/resolve this kind of problem?
On Tue, Apr 16, 2013 at 9:22 AM, Allen S. Rout wrote:
On 04/16/2013 08:59 AM, Zoltan Forray wrote:
The act
Neil
Had something similar, again with the filespace_name column
To resolve, i do this:
select char(filespace_name,20), etc
On 16 April 2013 21:25, Neil Schofield
wrote:
> I'm in the throes of an upgrade from TSM Server 5.5 to 6.3 and have had a
> bit of a problem re-writing some of our custom
I'm in the throes of an upgrade from TSM Server 5.5 to 6.3 and have had a
bit of a problem re-writing some of our custom SQL scripts. I was wondering
if anyone can point out what I'm doing wrong.
I understand that to get the select statements to return a table format
instead of a list format I nee
Hi Andy,
thank you for sharing :-)
Regards,
Michael
On Tue, Apr 16, 2013 at 9:54 PM, Andrew Raibeck wrote:
> Hello TSM community,
>
> I would like to draw your attention to a newly published guide for
> optimizing Tivoli Storage Manager performance. This guide is oriented
> toward TSM versio
Hello TSM community,
I would like to draw your attention to a newly published guide for
optimizing Tivoli Storage Manager performance. This guide is oriented
toward TSM version 6.3 and 6.4, and supersedes the previous performance
tuning guides. The guide features a whole new approach to:
* Config
All,
I'm working on this, and I need to know if it is still possible to create all
the needed parms in the dsm.opt and tdpexc.cfg files rather than having to
manually run the config wizard on every server?
If so, where can I find a table of all the pertinent parms?
I want a repeatable process, e
Hi Tim,
Yes.
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 04/16/2013
01:18:06 PM:
> From: Tim Brown
> To: ADSM-L@vm.marist.edu,
> Date: 04/16/2013 01:23 PM
> Subject: Re: tsm tdp vss issues exchange 2010
> Sent by: "ADSM: Dist Stor Man
Del,
Thanks!
If I have DB1 mounted as active on Exchange1 and DB1 mounted as passive on
Exchange2 does that
constitute 2 healthy copies ?
Thanks,
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del
Hoobler
Sent: Tuesday, 16 April, 201
Hi Tim,
Have you showed this to Microsoft?
The output below is from Microsoft's tool
for integrity checking (ESEUTIL).
Microsoft may be able to tell you why ESEUTIL
could not access the file.
On a side note... in case you were not aware:
For databases in an Exchange Server DAG that have
two or
Try ba stg ... preview=volumesonly.
Joerg Pohlmann
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Thorneycroft, Doug
Sent: Tuesday, April 16, 2013 09:45
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Tapes required by backup stgpool
You could
You could look at the last written date, any tape written to since the last
backup "backup stgpool" was completed
Should be needed.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Benhayoune Khalid
Sent: Tuesday, April 16, 2013 9:35 AM
To: ADS
Hi everybody,
TSM 6.2 on AIX 5.3
Is there any way to determine the primary tapes needed by a "backup stgpool"
command before launching it.
Thanks in advance.
Regards.
On 04/16/2013 09:36 AM, Zoltan Forray wrote:
> On Tue, Apr 16, 2013 at 9:22 AM, Allen S. Rout wrote:
>> On 04/16/2013 08:59 AM, Zoltan Forray wrote:
>>>
>>> The active session is only up to 222GB so it isn't volume - just one long
>>> transaction, I guess?
>>
>> (reliatively) Big files, transmitte
> Rick, that is interesting -
> How do they accomplish "gets written in ... smaller pieces"?
>
> Is this some TDP tuning parameters you invoke, or is it a matter of
> backing up 1 DB at a time instead of doing "backup *"?
>
> Thanks for any info!
>
> Wanda
>
I don't know myself, but some quick se
Initiating CHECKSUM mode...
Verifying log files...
Base name: E00
Log file:
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20\Logs\DB1_Logs\E03C7FB.log
- OK
Log file:
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20\Logs\DB1_Logs\E03C7FC.log
- OK
Log file:
\\?\G
I had a similar problem - one node has a 4TB (yes, TB) SQL database. Using
multiple streams helps. Still takes 17-hours to backup (from offsite across
10/100 public link - don't ask - been asking for a high-speed connection
for years - may finally get it this year).
On Tue, Apr 16, 2013 at 11:44
Yeow!
I need that Microsoft hit translated - into English!
Is it saying that the Microsoft exposure is for a volume that is being extended
while it is being snapped with VSS,
or for any volume that has EVER been extended?
(Should I be panicking at this point?)
W
-Original Message---
Hi Tim,
That may be ok. Is there more info later in the file?
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 04/16/2013
11:38:59 AM:
> From: Tim Brown
> To: ADSM-L@vm.marist.edu,
> Date: 04/16/2013 11:48 AM
> Subject: Re: tsm tdp vss iss
Rick, that is interesting -
How do they accomplish "gets written in ... smaller pieces"?
Is this some TDP tuning parameters you invoke, or is it a matter of backing up
1 DB at a time instead of doing "backup *"?
Thanks for any info!
Wanda
-Original Message-
From: ADSM: Dist Stor Manag
Seeing this error. Not sure how to interpret ?
Error: Access to source database
'\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20\Logs\DB1_Logs\E00' failed
with Jet error -1811.
Thanks,
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of De
Most of our problems like this are SQL db backups that are one big file.
We ask the Win admins and DBA's to change the backup such that it gets
written in a bunch of smaller pieces.
Try and identify the big file that is is being backed up. Can it be
broken into smaller pieces? Can it be zip'ed i
May or may not be related I have an AVAMAR box in our environment and EMC
issued a VSS-related problem recently.
EMC references 2748349: http://support.microsoft.com/kb/2748349 for resolution.
EMC comments: "The data for applications backed up by other Avamar VSS plug-ins
(Exchange VSS, Sh
Hi Tim,
It looks like the Exchange integrity check is failing.
Check this file:
C:\adsm.sys\vss_staging\TDP_EXCH2\TSMPOK\20130416071952\b6d6da44-9ba6-4426-9503-1e2183bab0d3_Audit.txt.log
to see why.
Thanks,
Del
"ADSM: Dist Stor Manager"
We address it with a larger log file. Our is 100G.
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan
Forray
Sent: Tuesday, April 16, 2013 9:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Addressing "log pinned" condition on V6
Has anyone had numerous issues with TSM TDP for Exchange 2010. We continue to
struggle with VSS issues
and Microsoft claims its not their issue. We initially had Exchange circular
logging enabled and have since
turned that off as recommended. I see that TSM TDP for Exchange 6.4 is
available.
But, how do you address/resolve this kind of problem?
On Tue, Apr 16, 2013 at 9:22 AM, Allen S. Rout wrote:
> On 04/16/2013 08:59 AM, Zoltan Forray wrote:
> >
> > The active session is only up to 222GB so it isn't volume - just one long
> > transaction, I guess?
>
> (reliatively) Big files, tran
On 04/16/2013 08:59 AM, Zoltan Forray wrote:
>
> The active session is only up to 222GB so it isn't volume - just one long
> transaction, I guess?
(reliatively) Big files, transmitted (relatively) slowly, are my most
common log-pin culprit.
- Allen S. Rout
I have been experiencing frequent "log pinned" situations on a v6.2.5.0
server - by this I mean my monitoring program starts alerting me about the
active log reaching >75% (currently at 50GB).
Yes, I have identified the node causing this but want to know how to
diagnose and resolve why this node i
35 matches
Mail list logo
