this
drive is not defined to this server (ANR8940E). This causes some
transactions to fail due to the delay (storage media inaccessible).
Anyone, who can help me with this?
Best regards,
Jörg Nouvertné
http://home.wtal.de/the_swordsman/
Hi Nazir,
to backup non-Domino database files (e.g. Domino program files) you do
require a regular backup client. Only Domino databases and the TXN files are
covered by the TDP.
Best regards,
Jörg
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf
Hi Long,
if you try to reclaim a copypool, it might happen that due to the
unavailability of a primary tape, that whole reclamation fails immediately,
and almost all tapes are never being reclaimed. I had to struggle with this
quiet some time. Look for ANR1259W in the actlog.
Best regards,
Joer
uld not have to worry if it is a header problem on
> the tapes.
>
> -Original Message-
> From: Jörg Nouvertné [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 24, 2001 9:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: SAN Environment
>
>
> That's correct as
That's correct as long as you install the Storage Agent on the client, which
"borrows" a drive from the TSM server and send only the management info
through the LAN. Therefore you needs the (expensive) STA license and to my
knowledge the library sharing option.
We used it once but had to disable
Hello,
we had some trouble seeing the 3584 library when attached to a SAN. But I've
recognized in our configuration (lsdev -Cctape), that the LUN between drive
1 and drive 2 wasn't in use. Therefore I defined it manually into the "hole"
and it worked. By the way: You'll find the right device unde
Hi Chris,
I just experience the same issue with LTO drives/tapes, sporadically when
backing up over the LAN, and excessive when backin up LAN-free over the SAN.
I've opened a PMR with Tivoli, but in my optinion, this is a software issue,
although I cannot say which software. It's either the LTO
Hi,
you can use flexible admin schedules using admin scripts like this:
select process from processes where -
upper(process)='BACKUP STORAGE POOL'
if(RC_OK) goto reschedule
backup DB type=full devc=LTO
exit
reschedule:
del sch retry_backup_database type=admin
def sch retry_backup_database t=a
We just ordered them. Fuji confirmed proper functionality with the LTO
Ultrium drives in our 3584 and guaranteed onsite support if necessary. I can
share my experience in a couple of weeks.
Joerg Nouvertne
http://home.wtal.de/the_swordsman
> -Original Message-
> From: ADSM: Dist Stor Ma
Hello,
I asked someone of Tivoli about possible causes, and it seems that (if the
log usually behaves normal and is sized suffeciently) most likely long term
backups prevent log entries of completed transactions from being cleared.
It's the way, the log is strucuterd.
The next time this happens,
Hello,
although there might be some dirty tricks, to force a backup to write to a
specific tape, I don't see any reason to do this. One great advantage of *SM
is, that (from the client perspective) you don't have to care about the
storage media anymore. *SM makes sure (when properly configured, o
ng the feedback, and after the modules
passed the tests, I'll register the TSM namespace at CPAN.
As the next steps, I can imagine to collect scripts or code fragments based
on this module on my homepage. Volunteers are welcome.
Best regards,
Jörg Nouvertné
http://home.wtal.de/the_swordsman
You have to checkin the scratch volumes beforehand, *SM won't ask for them.
Kind regards,
Jörg
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Doug McLauchlan
> Sent: Mittwoch, 18. Juli 2001 03:34
> To: [EMAIL PROTECTED]
> Subject: Using Sc
Hello,
getting sick of reinventing the wheel every time I had to write a TSM script
in PERL, I've put some effort in creating a collection of TSM related PERL
modules, which are ready to be released in a beta version. The currently
implemented features are
1. User/Password handling
2. Interface
14 matches
Mail list logo
