Thank you very much Erwann, but it does not help. There is no visible
improvement.
Grigori G. Solonovitch
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann
SIMON
Sent: Sunday, August 21, 2011 4:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re:
Working with timestamps can be onerous. One sometimes has to be wily to
compensate for processing time. Try:
select msgno, severity, message, originator, nodename, ownername, schedname, \
domainname, servername, sessid, session, process, date_time \
from actlog \
where DATE(DATE_TIME)=
We had an incident this morning that ended up being caused by a Windows
server that was renamed (internally) and connected to a domain (previously
standalone), thus initiating a full backup of an 8TB volume/space, since
TSM now sees it as new filespaces.
How do I handle this to avoid a full backup
Please correct me if I am wrong, but I was under the impression that if a
Windows node does NOT have a NODENAME statement in it's dsm.opt, it simply
asks the OS for the hostname and uses that. This value is also used for
the filespace names.
So, if this Windows node has been backing up without a
Hi Richard,
You're right, and I see a mistake in my statement. I should have written
"date(date_time)=current_date" and not
"date(current_timestamp)=current_date"...
Best regards / Cordialement / مع تحياتي
Erwann SIMON
Le 22/08/2011 13:29, Richard Sims a écrit :
Working with timestamps can
-Zoltan Forray wrote: -
>We had an incident this morning that ended up being caused by a
>Windows server that was renamed (internally) and connected to a
>domain (previously standalone), thus initiating a full backup of
>an 8TB volume/space, since TSM now sees it as new filespaces.
>
>How
-Zoltan Forray wrote: -
>Please correct me if I am wrong, but I was under the impression that
>if a Windows node does NOT have a NODENAME statement in it's dsm.opt,
>it simply asks the OS for the hostname and uses that. This value is
>also used for the filespace names.
The documented def
All you have to do is use the same "Wizard" that you used
to create the "Service" and update instead of create. This let's you
change the node name used by the service.
David Longo
>>> Thomas Denier 8/22/2011 12:27 PM >>>
-Zoltan Forray wrote: -
>Please correct me if I am wrong, but I
Thomas,
Thanks for both of your responses. You have confirmed what we are seeing.
We rooted through the registry and see the keys with the old node name
and encrypted password. The box was renamed and rebooted but the GUI was
never bought up. As soon as we bought up the GUI, it grabbed the hos
Of course, even with a NODENAME statement and reworking the scheduler, the
filespace names are still based on the hostname. We have renamed plenty
of other servers that had nodename statements and the first backup was
brand-new.
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Common
Thank you very much, Richard. This query is much faster and gives the same
result from data point of view.
I have only question about period of time from 00:00:00 till 00:02:59.
Is this query correct for mentioned period of time?
Grigori G. Solonovitch
-Original Message-
From: ADSM: Dis
I am currently running TSM V5.5 on AIX. I am setting up a TSM V6.2 server on
Linux at a new data center. I would like to use backup sets to transfer client
data from the old to the new data centers. This backupset data will be used to
populate the newly built clients - not as a backup data sto
On Aug 22, 2011, at 2:17 PM, Grigori Solonovitch wrote:
> Thank you very much, Richard. This query is much faster and gives the same
> result from data point of view.
> I have only question about period of time from 00:00:00 till 00:02:59.
> Is this query correct for mentioned period of time?
>
Hi,
I've got a problem. An installation failed when creating an instance and I
decided to uninstall and start over. I removed the installation using the
uninstall script provided. But when I ran install.bin the next time it asked
for the password of the instance owner and then failed.
So it seems
The autonomous installler places files under /var/ibm that needs to be removed
incase the installation fails. I'm not infront of a machine atm so I cant give
you the exact path, but previously when installations failed, I made sure to
remove the entire directory containing configuration files (t
I've read through your question 3 times now and I'm still trying to figure out
what you're doing :)
You're mentioning creating backupsets. For me, a backupset is a way of
restoring a client without having to transfer the data across the LAN. But
you're also mentioning TSM servers placed on AIX
16 matches
Mail list logo
