On Fri, 7 Aug 2009, I wrote:
[...]
I'd think that fudge factor * [V5.5] Log Consumption / days since reset
logc
might be a good way to estimate V6 log space requirements per day, for those
planning a V5 - V6 upgrade, once a plausible range for the fudge factor
(likely 1 ;-() has been
Hi All,
We recently upgraded a mac-Klient from 5.5.1.6
to 6.1.0.2 (because of the gui not running-problem)
Now we have a problem with the backup of a domain, which has a space inside
The domain-entries in dsm.opt looks like:
DOMAIN /
DOMAIN /Volumes/Promise RAID
... this worked so far.
Now
Wolfgang wrote:
Now my long term averages are in: for the interesting (V5.5) TSM servers
around here, the Log Consumption ranges from 5000 to 9000 MB/day.
So, does this tell me anything about future (V6) Log Space requirements?
I have test database 6.1.2 and I think:
1) you need additional space
Hi Christian,
Windows 2008 R2 support does require changes in the client to make it work
correctly. The supporting code is not yet available. If you go to the link
in my sig and click Client requirements, then find the article for
Microsoft Windows client requirements, you will find our
Hi,
Has anyone got TSM BA Client 6.1.0.2 working with Windows Server 2008 R2?
Best Regards
Christian Svensson
Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
Skype: cristie.christian.svensson
Hi Rainer,
I'm not sure yet what changed, but try putting single quotes (') around the
double quotes to bypass the problem:
DOMAIN '/Volumes/Promise RAID'
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes
Hi Andy,
DOMAIN '/Volumes/Promise RAID' -- it works :-)
thanks a lot
Rainer
Andrew Raibeck schrieb:
Hi Rainer,
I'm not sure yet what changed, but try putting single quotes (') around the
double quotes to bypass the problem:
DOMAIN '/Volumes/Promise RAID'
Best regards,
Andy
Andy
Don't forget the requirement for 3-full DB backups before the
translogs/archtranslogs are purged/reset. I too ran into the log
overflow/blew out 300GB of archtranslog space/filesystem and had to move
it to a 1TB disk to hopefully prevent this from happening again, as well
as performing 3-daily
You have to do three FULL DB backups per day? Can't you just have
enough log space to let this run for three days (or does that not meet
the 3 DB backup requirement?)
Does anyone know why there is a requirement for 3 DB backups before the
logs are reset?
Thanks,
Bill Evans
Research Computing
While I am new to managing TSM, I have tried to research this and have not
found much other than upgrade to 5.5.2 (we are on 5.5.1). Has anyone else
seen this on you HSM clients?
Client is failing. Event viewer on the client machine is full of
Journal for fs 'H:' reset:
and
Notification buffer
Window 2003 Server, SQL Server 2005, TSM 5.5.1.0 TDP 5.5.1.0
We are taking weekly full and daily diff backups of SQL databases using TDP.
What appears to happen if a database is created mid-week is that the DIFF
backup appears to work, no errors are flagged. However, an attempt to restore
this
2 full DB backups are the requirement today to flush the logs, I believe
this will be changed in the future..
Intellectuals solve problems; geniuses prevent them - Albert Einstein
Evans, Bill bev...@fhcrc.org
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
2009-09-02 16:30
Please
Danny,
Are you are using HSM and Jorurnaling on this particular client?
It looks like the journaling for the H: drive on the client is having issues.
Have there been any recent changes made to this client, ie,. HSM implemented,
Journaling implemented?
At first glance, the errors below look to me like more of an issue regarding
the TSM Journaling Engine on this client, rather than any HSM component.
When you say 'client is failing', can you give a little more description of
the symptoms which suggest this failure, perhaps some output from your
James,
Yes I am using journaling. Nothing has changed that I am aware of. This node
was built specificly to be used for HSM. I see no journal files at all on
the H: drive.
On Wed, Sep 2, 2009 at 10:38 AM, James Choate jcho...@chooses1.com wrote:
Danny,
Are you are using HSM and Jorurnaling on
Hi Steve,
You don't show the error messages, so it is difficult to guess what is
happening.
I assume you are restoring the DIFFERENTIAL as well as the previous FULL
when you perform the restore?
If so, is it possible something else is running a FULL backup, for
example, a snapshot tool?
Thanks,
Okay - I think this error gets us more towards the business end of your
problem.
Take a look at:
http://support.microsoft.com/kb/909424/en-us
Guessing at the history of this, if it pre-dates your involvement, an
explanation could be that TSM Journaling was enabled on this backup client
because
Start with an active log size that is twice the size of the recovery log
for the
existing V5 server. For example, if the V5 recovery log is 20 GB, start
with
an active log size of 40 GB for the upgraded V6.1 server.
I believe there's a technote about this, I'll try to find it
Intellectuals
18 matches
Mail list logo
