Hello,
there are two things that will cause TSM to issue the volume mount
request:
- the tape inserted in the drive in the evening was already used over
night by reaching a migration threshold of the primary pool. In that case
check for the mountretention parameter on the devclass definition. You may
expand that period up to many hours
- the volume inserted in the tape drive is not the volume expected by the
TSM server. Because TSM uses a volume as long as there is any space left
you will need to mark the volume as "full" or "unavailable" just after
finishing the migration process. Or, you should create a storagepool for
each day.
Check the activity log for overnight migration and label readings - as
far as I remember there must be a massage that states "invalid volume
label" or something like that.
I don't understand why you want to delete the backup data on tape. Is
there a full backup every day? Is really all data kept in the diskpool? If
you migrate the data from the disk pool you cannot be sure to get a -
virtual - backup of your systems copied to tape in the morning. - But yes,
the easiest way is to run a "delete volume xxxxxx discard=yes" before
overwriting the tape.
Have you thought of using two copypools used alternativly each day or
week?
Best regards
Ullrich Mänz
System-Integration
FRITZ & MACZIOL Software und Computervertrieb GmbH
Ludwig Str. 180D, 63067 Offenbach, Germany
Amtsgericht Ulm, Handelsregister-Nummer: HRB 1936
Geschäftsführer: Heribert Fritz, Oliver Schallhorn, Frank Haines
Inhaber: Imtech N.V., Gouda, Niederlande
Referenzen finden Sie auf unserer Website, Rubrik 'News'.
For References, please click our website, button 'News'.
Mail powered by Lotus Notes Version 7
Tuncel Mutlu <Tuncel.Mutlu AT AKBANK DOT COM>
Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04.09.2009 11:01
Bitte antworten an
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
An
ADSM-L AT VM.MARIST DOT EDU
Kopie
Thema
[ADSM-L] handling mount requests
Hi,
I have a really (another country) remote TSM server (Windows 2003 x32)
with 1 x LTO-2 drive. TSM server 5.5.3.0, client version is 5.5.2.2. I
have created a disk pool on the TSM server, which I intend to migrate
every night to the LTO-2 cartridge. For now only 2 clients (the TSM server
one of them).
The issue:
- Before they had some other software (CA Arcserve v11.5) and
they (the stuff onsite) changed the cartridge every morning as they
arrived (as it was ejected), one cartridge every day of the weekday (and
they take the cartridge home)
- I configured it correct (manual library etc), and it is working
fine, but when I scheduled a migration job every night it awaits a reply
to mount the cartridge. But the cartridge is already inside ? How can I
avoid the reply issue ?
- I did assume that expiring precisely that tapes that morning
every day is difficult and I am thinking of deleting that volume every
morning ? What do you think ?
Regards,
Tuncel Mutlu
________________________________
[http://www.akbank.com/images/disclaimer.jpg]<
http://www.akbank.com/disclaimer.asp>
Bu e-posta ve muhtemel eklerinde verilen bilgiler kişiye özel ve gizli
olup, yalnızca mesajda belirlenen alıcı ile ilgilidir. Size yanlışlıkla
ulaşmışsa lütfen göndericiye bilgi veriniz, mesajı siliniz ve içeriğini
başka bir kişiye açıklamayınız, herhangi bir ortama kopyalamayınız. Bu
mesaj aksi sözleşme ile belirtilmedikçe herhangi bir finansal işlem
teklifi, alımı, satımı veya herhangi bir havalenin teyidi gibi bankacılık
işlemi yapılması amacını taşımamaktadır. Verilen tüm bilgilerin doğruluğu
ve bütünlüğünün garantisi verilmemekte olup, önceden bildirilmeksizin
değiştirilebilecektir. Bu mesajın içeriği Bankamızın resmi görüşlerini
yansıtmayabileceğinden Akbank T.A.Ş. hiçbir hukuki sorumluluğu kabul
etmez.
|
