Dear All,
I am facing problem in executing below script thro' tsm client scheduler
in background mode. if we start the scheduler service in forground by
executing dsmc scheule, the scripts works fine. However using nohup
dsmc schedule 2 /dev/null it fails to execute.
Our TSM server is on
Set the MAXNUMMP to the number of drives you are willing to have this
node monopolize. If you don't care that this node could grab all of the
drives in your library and leave everything else out in the cold, knock
yourself out. If you want to force reasonability on your DBA's, set it
to a lower
Without details from the failure, we can't do much to advise: fails
to execute provides us with no information. Delve into your
dsmerror.log to look for any possible info there. Also, whereas you
are using nohup, you should have a nohup.out file to examine.
Lastly, don't throw away potential
I second that; re-install should be easier than restore, and it's easy
to make it so with NIM.
Could be both. A mksysb image file to some NFS server serving the file
via NIM.
Gruss, Andreas
+++ Jetzt wieder Steigern Sparen! Neuprodukte bis zu 50% günstiger!
Die große SÜDKURIER-Auktion vom
Dear List,
I installed TSM Extended Edition 5.3 on Windows
2003 Server, and I have 18 AIX 5.3 Servers and 10 Windows 2003 Server.
All are the systems connected through SAN. I have IBM Total Storage 3584
Tape Library with 8 LTO Drives.
I have some queries; please can
Transparent encryption is not currently supported for the BA Client.
It's not quite as simple to support transparent encryption for
the BA Client as it is for the TSM API due to the no query restore
functionality of the BA Client.
Transparent encryption for the BA Client is a known requirement.
Well, I'd say that seems to be what is causing your intermittent failures
then. Unfortunately, there is no magic bullet approach to fix this
situation -- it requires cooperation of all the admins involved (TSM, DBA,
Unix, applications), and the TSM admin has the responsibility to educate
all
Thanks to all for your suggestions. Because the new GM data retention
policy calls for true full backups I've elected to use Selective backups
to be scheduled in a weekly, monthly, and yearly fashion. To make
matters worse this is for a cluster server so I created separate client
scheduler,
At 08:36 AM 9/15/2006, Andreas Kaiser wrote:
I second that; re-install should be easier than restore, and it's easy
to make it so with NIM.
Could be both. A mksysb image file to some NFS server serving the file
via NIM.
Gruss, Andreas
This is what we do for our AIX DR backup.
--
Paul
Instead of using a SELECTIVE backup which you need to specify what to backup,
just change the management class(es) used for the
weekly/monthly/yearly backups to MODE=ABSOLUTE. Then you backup schedules are
just INCREMENTAL using the existing DOMAIN, but
actually FULL backups each time.
You also
HI,
I´m going to install TSM in red hat 4, and I´ll connect a Sun Storedge
L1000 device to that server. Do you know where I could found drivers for
Storedge L1000 for that Red Hat distribution?.
I´ve searched in Sun web page but I couldn´t found them, now I´m looking
for them in
Sorry for the long-winded response, I was on a roll! Hope it helps...
This is exactly what I needed. I was considering putting the Oracle TDP
backups to disk (though we're tight on disk space). I didn't realize that
they wouldn't go down the storage hierarchy, though. Thanks for the
All,
I've been waiting for Tivoli to provide individual file restores from an image
backup in Windows. According to the latest 5.3.4 BA client it is still not an
option.
Andy, can you confirm?
Thanks,
Brian
Brian Scott
EDS
Global Client Engineering-GM
MS 3234
4594 W Nancy Dr.
Kankakee, IL
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 09/15/2006
11:37:44 AM:
I've been waiting for Tivoli to provide individual file restores
from an image backup in Windows. According to the latest 5.3.4 BA
client it is still not an option.
Never saw much use for this functionality. You do a
On Fri, 15 Sep 2006 09:38:32 -0400, Scott, Brian [EMAIL PROTECTED] said:
Thanks to all for your suggestions. Because the new GM data retention
policy calls for true full backups
Oy. Nothing like policy specifying methods, instead of requirements.
- Allen S. Rout
Is there any particular reason that normal, scheduled backup processing of
a Solaris system, completely ignores ZFS filesystems ?
The client is 5.3.3.0 and I have suggested to the owner of the system to
update to 5.3.4.4.
Searched on IBM result in nothing but references to zFS on USS/Unix.
The scenario is I have a copy pool tape that was accidently damaged. I
would like to know which primary pool tapes I would need to recreate
this copypool tape. The first obvious way is to run a backup stgpool
preview=yes command however that will ALSO show other volumes out of
sync and doesn't
Hello Zoltan,
I suspect that the TSM folks have not finished testing zfs, there may be
boundary conditions that might have problems.
One feature that you most likely are not using, and I suspect will not work, is
to try backing up files with the new acl's (the same as nfs version 4) and see
Hello,
I'm interested in finding out from those people who are using Sepaton
systems for their TSM backups, what kind of nightly volume do you write to
it? I have the specs from the company regarding what it supports; what
I'm interested in is how it holds up in the real world under heavy write
Last week, Bill Boyer posted a message (which I no longer have) about
splitting a database and library sharing. and ownership of tapes. I saw
one response suggesting exporting and importing the data, but nothing
else.
Did anyone ever come up with other ideas on this? I'm actually getting
ready
We run TSM 5.3.1 32bit on windows 2000 32bit Server. We are considering
moving to TSM 5.3.3 64bit on RedHat Enterprise Linux v4 AS x64.
Is it possible to migrate the database from 32bit server to 64bit server?
Anyone done it before and had it work?
Thanks,
Alex
All, I have two volumes on the same server that need to be backed up
alternately every other night. eg VolGWA needs to be backed up on M, W and Fri
and VolGWB needs to be backed up on T, Th, Sat and Sun. Is there a day
statement that can be made in the opt file so that it will know which
On Sep 15, 2006, at 5:29 PM, John Bortscheller wrote:
All, I have two volumes on the same server that need to be backed
up alternately every other night. eg VolGWA needs to be backed up
on M, W and Fri and VolGWB needs to be backed up on T, Th, Sat and
Sun. Is there a day statement that can
I don't understand why a client running this version of TSM would show an
entry in the activity log that says this was in use and skipped when it
shows it to be excluded by TSM. I see a number of clients showing this same
thing.
Dsmc query inclexcl shows this.
Excl Directory C:\adsm.sys
24 matches
Mail list logo