Hello
I'm running TSM client in an authorized user configuration.
This authorized user has specific ACL set on the directory we want to
backup.
It drived me to launch my backup by specifying the filespace I want to
backup while calling dsmc ; for exemple :
dsmc incr /appli/myappli
Hi,
did you try to comment out the prole entry in the inittab?
Regards
TSM User [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
07/04/2008 10:41 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
[ADSM-L] TDP for SAP
Used for years - and using it to rebuild my tsm server at a DR site -
never had any problem
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Wanda Prather
Sent: Wednesday, July 09, 2008 7:51 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM DB backup to
John,
If TSM thinks that the cartridges are already offsite, then you
should be able to remove them from the library using library commands.
See publication 96845 Chapter 4, Export Data Cartridges:
http://docs.sun.com/app/docs/prod/L700.tape#hic
Cheers,
Neil Strand
Storage Engineer - Legg
Marc -
A 'dsmc Incremental Fspec' type backup where the Fspec identifies a
directory or file within a file system constitutes a partial
incremental backup. It is still an Incremental, where the TSM server
(or JBB database) is referred to for the list of Active files within
the involved area.
Tuncel -
SeeInactive files, rebind
in http://people.bu.edu/rbs/ADSM.QuickFacts
Richard Sims
Good Morning all,
Does anyone have any servers running solid databases that are backed up
by TSM? I just found out we now need to ensure recoverability of this
IVR system. The contactor provided information on backups via Symantec
Intelligent Disaster Recovery. We are a TSM shop and have been
This worked! I was able to checkin/checkout 7 of the 12 'missing' volumes (it
couldn't find 5 of them). That tells me that they are no longer in the library
so now I will request a report from our offsite storage vendor for the
remaining tapes. I suspect that they made it there after all.
FYI... the Windows 5.5.1 clients are now available.
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
IBM Tivoli Storage
And V5.5.1 server fix pack 1
Download V5.5 Fix Pack 1 (AIX) 7/7/2008 US English 49324193 FTP
Download V5.5 Fix Pack 1 (HP) 7/7/2008 US English 248662428 FTP
Download V5.5 Fix Pack 1 (Linux) 7/7/2008 US English 2686 FTP
Download V5.5 Fix Pack 1 (Solaris) 7/7/2008 US English 113438317 FTP
Download
Greetings,
There are a couple people at our company that contend that FC is
going away, and in a very short time everything will be iscsi. I am
afraid I am completely ignorant about iscsi as it relates to tape
traffic. My questions are:
1) Can anybody tell me what is going on in the
We're running an RS6000 w/AIX. TSM 5.3.2. We'd like to migrate to Linux.
I don't have a ton of information, but I need to know if anyone has had
experience in similar situation or desires. Please let me know if you have
any resources to discuss this! Many thanks in advance!!
I think someone is pulling a fast one on you. Most likely this is
caused by sales people of iscsi equipment. However, FC is still faster,
and more reliable. The only reason it would go away is if your managers
and CIO decided to do away with it. From what I've seen out of Brocade,
they'd be
Howard,
Thanks for your input. Our very vocal proponent of iscsi is
probably getting his information from a Gartner-wannabe trade rag that
is being sponsored by iscsi vendors. He is from our Network group, and
has never been responsible for a storage environment himself. By
Gartner once said that iSCSI would be the dominant way of connecting to
storage by 2001.
FC is going away as fast as tape drives are.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: Thursday, July 10, 2008 3:14 PM
Greetings,
One common way to migrate between different server types is to:
1) Install and configure your new TSM server
2) Create at least one administrator account that has the same name on
both the old and new TSM server
2) Using that account, establish TSM server-to-server
John,
The Gresham Storage Director provides both iSCSI and/or FC connectivity
for your backup servers and manages physical tape and other devices off
the back-end. iSCSI works well with this and has many good attributes
including using existing infrastructure for remote connectivity. We
have
Death to free magazines!
On 7/10/08, Andy Huebner [EMAIL PROTECTED] wrote:
Gartner once said that iSCSI would be the dominant way of connecting to
storage by 2001.
FC is going away as fast as tape drives are.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager
You can change the tsmjbbd.ini file to PreserveDbOnExit=1 just before you
reboot. Give it a few seconds, and the journal service should pick it up
dynamically. Then go ahead and reboot.
Obviously we support PreserveDbOnExit=1, else it would not be there. I
was simply trying to point out the
Well, I guess I really stepped in it... :-)
Journal based backup is primarily targeted for cases where there are lots
(hundreds of thousands or millions) of files with a small percent of
changed files. In these cases, the backup operation might take hours to
run, but only spend a handful of
Hi Alex,
Good out-of-the-box thinking, but the drawbacks are probably more severe
than the advantages:
- The TSM journal service (at least on Windows) is not a filter driver.
- Such a solution would cause lots of problems for the OS itself.
- I wouldn't want to be in your shoes if you
Question is
1. Are you able to configure TDP correctly ?
2. Which Database you are using to backed up by TDP ?
3. Have you initialized and certified password for TDP access ?
May clearly mention what exactly problem you are facing ?
Gajendra Kr. Khera
[Direction Is More Important Than
22 matches
Mail list logo
