Re: Starting a incremental backup from the Server GUI??
It should be - - if the client did not start backup between 23:00 and 00:00 the schedule will be "Missed" Samiran Das Zlatko Krastev To: [EMAIL PROTECTED] Subject: Re: Starting a incremental backup from Sent by: the Server GUI?? "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 03/27/2002 01:45 PM Please respond to "ADSM: Dist Stor Manager" "Pending" state means that the schedule will start soon. This state is entered when schedule time is passed but the schedule will start with random delay within startup window. If you want to change this behavior look for SET RANDOMIZE command. For example if the server is with default randomization of 25% and you have a schedule at 23:00 with default duration of 1 hour: - before 23:00 the schedule will be "Future" - after 23:00 but before actual start the schedule will be "Pending" - after actual start it will become "Started" and upon end will become "Failed" or "Completed" - if the client did not contacted the server between 23:00 and 23:15 the schedule will be "Missed" Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Re: Starting a incremental backup from the Server GUI?? Niklas Defining an immediate ClientAction should be the way to go! If it is showing 'pending' make sure the SCHEDULER service/daemon is running and if writing straight to tape that you have a drive free. It should be as simple as that! Also, try SCHEDMode PRompted as well! Regards, Demetrius Malbrough UNIX/TSM Administrator -Original Message- From: Niklas Lundstrom [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 4:05 AM To: [EMAIL PROTECTED] Subject: Starting a incremental backup from the Server GUI?? Hello Is it possible to start a client backup from the server? Now I have schedmode set to polling, but if the client misses the schedule I want to start a backup from the server instead of going to the client and starting it there. I've been looking at the immediate action schedules but the schedule don't seem to start, the schedule status is pending Regards Niklas Lundström
Re: problem with tape library on solaris
did you check output of "q devc f=d"? What is the mount limit and do you have sufficient mount point? Samiran Das Gerald Wichmann To: [EMAIL PROTECTED] Subject: problem with tape library on solaris Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 05/20/2002 09:47 PM Please respond to "ADSM: Dist Stor Manager" Solaris 8, Sun E250, ATL500 tape library (2 drives), TSM 4.2.2 First time getting a tape library working on solaris so I could be doing something wrong.. this is a test system. anyways it all seemed to work until I tried using the library: 05/21/02 17:01:26ANR2017I Administrator ADMIN issued command: BACKUP DB dev=dc.tape.lib_tape_1 type=f 05/21/02 17:01:27ANR0984I Process 2 for DATABASE BACKUP started in the BACKGROUND at 05:01:27 PM. 05/21/02 17:01:27ANR2280I Full database backup started as process 2. 05/21/02 17:01:47ANR4571E Database backup/restore terminated - insufficient number of mount points available for removable media. 05/21/02 17:01:47ANR0985I Process 2 for DATABASE BACKUP running in the BACKGROUND completed with completion state FAILURE at 05:01:47 PM. tsm: SERVER1>q libr Library Name: LIB_TAPE_1 Library Type: SCSI Device: /dev/rmt/7lb Private Category: Scratch Category: External Manager: Shared: No LanFree: ObeyMountRetention: tsm: SERVER1>q dr f=d Library Name: LIB_TAPE_1 Drive Name: LIB_DRIVE_1 Device Type: DLT On-Line: Yes Device: /dev/rmt/0mt Element: 16 Allocated to: Last Update by (administrator): ADMIN Last Update Date/Time: 05/21/02 17:00:43 Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE Library Name: LIB_TAPE_1 Drive Name: LIB_DRIVE_2 Device Type: DLT On-Line: Yes Device: /dev/rmt/6mt Element: 17 Allocated to: Last Update by (administrator): ADMIN Last Update Date/Time: 05/21/02 17:00:58 Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE bash-2.05# ls -l /dev/rmt total 36 lrwxrwxrwx 1 root root 44 May 12 01:13 0mt -> ../../devices/pci@1f,4000/scsi@2,1/mt@1,0:mt lrwxrwxrwx 1 root root 45 May 12 01:13 0mtn -> ../../devices/pci@1f,4000/scsi@2,1/mt@1,0:mtn lrwxrwxrwx 1 root root 45 May 12 01:13 0mtt -> ../../devices/pci@1f,4000/scsi@2,1/mt@1,0:mtt lrwxrwxrwx 1 root root 42 May 12 01:14 1op -> ../../devices/pci@1f,4000/scsi@5/op@2,0:op lrwxrwxrwx 1 root root 43 May 12 01:14 1opt -> ../../devices/pci@1f,4000/scsi@5/op@2,0:opt lrwxrwxrwx 1 root root 42 May 12 01:14 2op -> ../../devices/pci@1f,4000/scsi@5/op@3,0:op lrwxrwxrwx 1 root root 43 May 12 01:14 2opt -> ../../devices/pci@1f,4000/scsi@5/op@3,0:opt lrwxrwxrwx 1 root root 42 May 12 01:14 3op -> ../../devices/pci@1f,4000/scsi@5/op@4,0:op lrwxrwxrwx 1 root root 43 May 12 01:14 3opt -> ../../devices/pci@1f,4000/scsi@5/op@4,0:opt lrwxrwxrwx 1 root root 42 May 12 01:14 4op -> ../../devices/pci@1f,4000/scsi@5/op@5,0:op lrwxrwxrwx 1 root root 43 May 12 01:14 4opt -> ../../devices/pci@1f,4000/scsi@5/op@5,0:opt lrwxrwxrwx 1 root root 42 May 12 01:14 5lb -> ../../devices/pci@1f,4000/scsi@5/lb@6,0:lb lrwxrwxrwx 1 root root 43 May 12 01:14 5lbt -> ../../devices/pci@1f,4000/scsi@5/lb@6,0:lbt lrwxrwxrwx 1 root other 44 May 18 00:07 6mt -> ../../devices/pci@1f,4000/scsi@2,1/mt@2,0:mt lrwxrwxrwx 1 root other 45 May 18 00:07 6mtn -> ../../devices/pci@1f,4000/scsi@2,1/mt@2,0:mtn lrwxrwxrwx 1 root other 45 May 18 00:07 6mtt -> ../../devices/pci@1f,4000/scsi@2,1/mt@2,0:mtt lrwxrwxrwx 1 root other 44 May 18 00:09 7lb -> ../../devices/pci@1f,4000/scsi@2,1/lb@0,0:lb lrwxrwxrwx 1 root other 45 May 18 00:09 7lbt -> ../../devices/pci@1f,4000/scsi@2,1/lb@0,0:lbt bash-2.05# /usr/kernel/drv/lb.conf
Re: problem with tape library on solaris
Your devclass definition says device type as LTO where as your drive definition says device type as DLT. The output given by you says your drives are DLT type. Target 1 Unit 0 Removable Tape QUANTUM DLT7000 2560 Target 2 Unit 0 Removable Tape QUANTUM DLT7000 2560 So define a new device class as follows >define devc DC.TAPE.LIB_TAPE_2 LIB_TAPE_1 devtype=dlt Direct you data base backup to this device class and database backup should be working. For your storage pool, you need to delete the storage pool and redefine it using this new device class. Then you can delete you old device class. Samiran Das Gerald Wichmann To: [EMAIL PROTECTED] Subject: Re: problem with tape library on Sent by: solaris "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 05/21/2002 09:28 PM Please respond to "ADSM: Dist Stor Manager" Yep.. I should've posted that output as well. I've confirmed that other processes also cause the same error (e.g. migrations). Guess I'll call IBM this morning and see what they have to say. I probably forgot something somewhere.. tsm: SERVER1>q devc f=d Device Class Name: DC.TAPE.LIB_TAPE_1 Device Access Strategy: Sequential Storage Pool Count: 1 Device Type: LTO Format: ULTRIUMC Est/Max Capacity (MB): 102,400.0 Mount Limit: DRIVES Mount Wait (min): 60 Mount Retention (min): 60 Label Prefix: ADSM Library: LIB_TAPE_1 Directory: Server Name: Retry Period: Retry Interval: Shared: Last Update by (administrator): ADMIN Last Update Date/Time: 05/12/02 01:14:47 Regards, Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w) -Original Message- From: Samiran Das [mailto:[EMAIL PROTECTED]] Sent: Monday, May 20, 2002 10:26 PM To: [EMAIL PROTECTED] Subject: Re: problem with tape library on solaris did you check output of "q devc f=d"? What is the mount limit and do you have sufficient mount point? Samiran Das Gerald Wichmann To: [EMAIL PROTECTED] Subject: problem with tape library on solaris Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 05/20/2002 09:47 PM Please respond to "ADSM: Dist Stor Manager" Solaris 8, Sun E250, ATL500 tape library (2 drives), TSM 4.2.2 First time getting a tape library working on solaris so I could be doing something wrong.. this is a test system. anyways it all seemed to work until I tried using the library: 05/21/02 17:01:26ANR2017I Administrator ADMIN issued command: BACKUP DB dev=dc.tape.lib_tape_1 type=f 05/21/02 17:01:27ANR0984I Process 2 for DATABASE BACKUP started in the BACKGROUND at 05:01:27 PM. 05/21/02 17:01:27ANR2280I Full database backup started as process 2. 05/21/02 17:01:47ANR4571E Database backup/restore terminated - insufficient number of mount points available for removable media. 05/21/02 17:01:47ANR0985I Process 2 for DATABASE BACKUP running in the BACKGROUND completed with completion state FAILURE at 05:01:47 PM. tsm: SERVER1>q libr Library Name: LIB_TAPE_1 Library Type: SCSI Device: /dev/rmt/7lb Private Category: Scratch Category: External Manager: Shared: No LanFree: ObeyMountRetention: tsm: SERVER1>q dr f=d Library Name: LIB_TAPE_1 Drive Name: LIB_DRIVE_1 Device Type: DLT On-Line: Yes Device: /dev/rmt/0mt Element: 16 Allocated to: Last Update by (administrator): ADMIN Last Update Date/Time: 05/21/02 17:00:43 Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE Library Name: LIB_TAPE_1 Drive Name: LIB_DRIVE_2
Re: Reclamation is not happening - HELP!
This slowness can happen when reclamation is done from primary storage pool tapes also. Assume content of the offsite tape is scattered over multiple on site tapes and tape drive has to seek to multiple location on tape to pick up required piece of data can add up to significant tape loading/unloading and tape seek operation. So it is not unusual for an old offsite tape to take long time for reclamation. You should actually allow the reclamation process to finish. If you feel that reclamation process is keeping your tape drives engaged for long, then you can stop reclamation of offsite tapes alltogather and allow the offsite tapes to become empty due to natural expiration process. Samiran Das "Rushforth, Tim" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] PEG.MB.CA> cc: Sent by: "ADSM: DistSubject: Re: Reclamation is not happening - Stor Manager" HELP! <[EMAIL PROTECTED] U> 05/22/2002 01:13 AM Please respond to "ADSM: Dist Stor Manager" Offsite reclamation runs very slow when processing input data from disk. (see http://msgs.adsm.org/cgi-bin/get/adsm0203/501.html) Also with offsite reclamation, TSM will process all the eligible offsite tapes at once (it does not process one offsite tape then the next). Have you tried a higher value, eg how many tapes are eligible over 95%, try this value etc. Tim Rushforth City of Winnipeg -Original Message- From: Coats, Jack [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 2:25 PM To: [EMAIL PROTECTED] Subject: Re: Reclamation is not happening - HELP! Currently, I have done the following: Allowed expiration to complete fully. Started reclamation again. It is running now but very slowly In the last 4+ hours, moved 55K files and 1.45G of data (from q proc) or if I do a "query volume * access=readw,reado status=full,filling stgpool=copypool" it says my LTO is 17% full. The machine does nothing but TSM, and is not under a load from I/O, networking, virtual memory, storage, or processor as far as I can tell. In any case it isn't filling quickly at all. Suggestions? PS... Thanks for all the comments & suggestions sofar! ... Jack
Re: Please Help
Could you able to connect to server and take backup say using dsmc command line or GUI? Which version of linux client you are using? There is a issue about null string password while you use passwordaccess generate. You could try to use a different password by changing it at server and trying backup again. Samiran Das "Crawford, Lindy" To: [EMAIL PROTECTED] Subject: Please Help Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] ST.EDU> 05/23/2002 06:26 PM Please respond to "ADSM: Dist Stor Manager" Hi TSMers I have loaded a linux client with tsm. When I try to do a backup from the web I get the following error message:- ANS2622S Invalid ID or password submitted. I have done the installation like any other unix client.but I seem to get the above error for this one. Please help...any ideas..!! > Lindy Crawford > Business Solutions: IT > BoE Corporate > > * +27-31-3642185 > +27-31-3642946 [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> WARNING: Any unauthorised use or interception of this email is illegal. If this email is not intended for you, you may not copy, distribute nor disclose the contents to anyone. Save for bona fide company matters, the BoE Group does not accept any responsibility for the opinions expressed in this email. For further details please see: http://www.nbs.co.za/emaildisclaim.htm
Re: 3583 LTO library and drives in Windows 2000
Gill, I will suggest you to do the following - Your drive definition shows you are using \\.\tape0 device, which means you are using windows driver for tape drive. You should install TSM device driver from TSM installation CD if you have not already done so. Then you need to disable your two drives and robotic arm in windows device manager and reboot your server. After that start TSM utilities MMC and in device information find out device name for your drive1 and drive 2. Then redefine your drives using TSM device name. Delete your storage pool LTOPOOL1 and device class LTOCLASS1. Define again LTOCLASS1 and don't specify any format parameter this time. Define your storage pool again. Ensure that your cartridge holder is installed properly in library and library door is closed. Samiran Das Dallas Gill cc: Sent by: "ADSM:Subject: 3583 LTO library and drives in Windows Dist Stor 2000 Manager" <[EMAIL PROTECTED] ST.EDU> 05/24/2002 04:05 AM Please respond to "ADSM: Dist Stor Manager" Can anybody out there help, I have a windows 2000 server currently running TSM 4.2(going to be upgraded to 5.1). I have just connected up to it, our 3583 LTO library. I have defined the library and the drives in TSM using the following commands DEFINE LIBRARY LTOLIB1 LIBTYPE=SCSI DEVCIE=LB6.0.3.2 DEFINE DRIVE LTOLIB1 DRV1 DEVICE=\\.\TAPE0 ELEMENT=256 DEFINE DRIVE LTOLIB1 DRV2 DEVICE=\\.\TAPE1 ELEMENT=257 DEFINE DEVCLASS LTOCLASS1 DEVTYPE=LTO FORMAT=DRIVE LIBRARY=LTOLIB1 DEFINE STGPOOL LTOPOOL1 LTOCLASS1 MAXSCRATCH=30 but when I go to label and checkin some tapes, the library picks the first tape then loads it into one of the drives and then it times out. with the following error codes in TSM: ANR8304E, ANR8302E, ANRD, ANR8446I. I hope that someone can shed some light on this for me. Thanks Dallas
Re: labeling 3590 volumes
If you try to label a volume if it is defined in volumes table, it will
fail even if you specify overwrite=yes. Under such case you can label it by
using dsmlabel command. Restriction is that you can not use label more that
6 characters long. So if your existing label is longer then you are stuck.
This process is unpredictable and there is no guarantee that you can get
your data back after labeling. So be careful and keep a recovery plan ready
if this trick fails.
Regards
Samiran Das
"Qualls, Ted
W {PBSG}"To: [EMAIL PROTECTED]
Subject: Re: labeling 3590 volumes
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
05/25/2002
05:32 AM
Please
respond to
"ADSM: Dist
Stor Manager"
have you tried a 'move data' against the volumes?
-Original Message-
From: Jolliff, Dale [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 11:56 AM
To: [EMAIL PROTECTED]
Subject: Re: labeling 3590 volumes
Already tried that, it fails with ANR8816E - volume is already defined to
the library.
I need some way to bypass the checkin step of the label process..
-Original Message-
From: Pearson, Dave [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 11:51 AM
To: [EMAIL PROTECTED]
Subject: Re: labeling 3590 volumes
I did a "Help Label" in TSM and if I'm thinking what you want... here it is
labe libv library_name volume_name overwrite=yes
Dave Pearson
Comptuer & Nework Service
Snohomish County PUD # 1
> -Original Message-
> From: Jolliff, Dale [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, May 24, 2002 9:41 AM
> To: [EMAIL PROTECTED]
> Subject: labeling 3590 volumes
>
> Is there anyway to overwrite the header/label of a 3590 tape?
>
> One of our ATLs had a problem with some 3590 drives and chewed up the
> header
> records.
> The assumption is that the tape is good, the header records are just bad.
>
> I would restore the volumes from the copypools, but it just so happened
> that
> the two volumes that got whacked were a primary and the copy of the
> primary
> --
>
> Anyway, I'm hoping there is a way to get TSM to overwrite the header
> records
> without destroying the data. If there isn't, we are going to try using
dd
> to recreate the headers.
>
> Anybody ever done that successfully?
