DRM question
I have a tape, in the DRM copy pool, that indicates 0.0% utilization. A couple of days ago a reclaim was running, for this tape, every hour. The reclaim was ending with "success" but the tape was not expiring. I brought the tape back on site and checked it into the library. DRM now indicates the tape is "mountable" so it will go offsite again tomorrow but it's in the library for now. The tape indicates the last write date was 11/10/2000. "q content" won't display what's on the tape. "delete vol" won't delete the tape because it thinks there's data on the tape. "delete vol discarddata=yes" doesn't seem to want to give the tape back. What am I missing here? Why won't it give the tape back? Why won't it reclaim this tape? My server is TSM 3.7.4 running on Solaris 2.7. Thanks, in advance, for any ideas. Tom Fluker Viasystems Technologies
moving a server
I realize the topic has been discussed in the past but I'll ask again in case someone has had more recent experience... I would like to upgrade from ADSM 3.1 to TSM 3.7 AND change servers from RS/6000 to Sun at the same time. I don't plan to make any changes to the 3494/3590 devices but the disk storage pools will, obviously, change. Has anybody done anything quite like this? Can you give me some pointers or pitfalls that I can avoid? Is it going to require a server export/import or can I just use the database backup tape? Any suggestions, checklists, notes, will be greatly appreciated. Thanks in advance, Tom Fluker Viasystems Technologies
3494 problem
Anybody seen a 3494 problem that presents itself indicating "ANR8300E SENSE=00.00.00.67" What does that sense code mean? Thanks, Tom Fluker Viasystems Technologies
recovering copypools
Anyone had any experience with recovering copypool (offsite) data. Apparently the manager of our offsite storage location has lost several tapes that ADSM considers part of the offsite copypool. upd vol xxx access=destroyed only works for primary storage pools How do I tell ADSM that tapes/data in the copy pool has been lost? Thanks, Tom Fluker Viasystems Technologies
Re: ADSM and SQL-Backtrack
look at "/BACKTRACK:oracatalog" your backups are there Tom Fluker Viasystems Technologies > -Original Message- > From: Lu Ann Mezera [SMTP:[EMAIL PROTECTED]] > Sent: Monday, September 18, 2000 12:18 PM > To: [EMAIL PROTECTED] > Subject: ADSM and SQL-Backtrack > > We have ADSM 3.2.1 and are in the processing of implementing SQL > Backtrack > to backup up our Oracle databases on AIX and SQL Server 7.0 databases on > NT. > We know that Backtrack is pushing the backups to ADSM because when our > Information Architect goes into Backtrack to do a database restore, she is > successful. Also, the amount of scratch tapes in our MagStar are rapidly > depleting. When we do a QUERY OCCUPANCY * * command in dsmadmc, we see > two > (2) names for our Database AIX node where the Oracle databases are > installed > called /BACKTRACK:tmp-control-dir and /BACKTRACK:oracatalog. I can see > there are 30,000+ files and 240+ gig worth of data. > > This is my question. When I go into the ADSM gui, I see the high level > file > space structure of those 2 /BACKTRACK filespaces but don't see any > file/directory detail. Why is this?
Re: compatibility
we're getting a signal 11... apparently a problem with the OBSI module... BMC sez "they want to have the ADSM client upgraded to 4.1. Then reinstall the 2.4.10 version of the OBSI..." signal 11 occurs frequently during the backup resulting in incomplete backup... my server is ADSM 3.1 on AIX and the client is Sun 2.5 running ADSM 3.1.0.8 Tom > -Original Message- > From: Davidson, Becky [SMTP:[EMAIL PROTECTED]] > Sent: Monday, August 14, 2000 3:53 PM > To: [EMAIL PROTECTED] > Subject: Re: compatibility > > Our DBA's just told us that BMC said that SQL-BACKTRACK isn't compatible > with anything about 3.7.1 for a client? What version are you running? > What > kind of problems with Backtrack are you having? > > -Original Message- > From: Fluker, Tom R [mailto:[EMAIL PROTECTED]] > Sent: Monday, August 14, 2000 2:26 PM > To: [EMAIL PROTECTED] > Subject: compatibility > > > I've got a problem with SQL-BACKTRACK (signal 11)... BMC is telling me to > load the 4.1 client software. > > My server is ADSM 3.1... > > Has anybody had any experience running TSM 4.1 client software into ADSM > 3.1 > server? Probably just asking for trouble and BMC will probably tell me to > upgrade server if that doesn't work. Man it must be great to have > software > "up to date" all the time > > Thanks for any help > > Tom Fluker > Viasystems Technologies
compatibility
I've got a problem with SQL-BACKTRACK (signal 11)... BMC is telling me to load the 4.1 client software. My server is ADSM 3.1... Has anybody had any experience running TSM 4.1 client software into ADSM 3.1 server? Probably just asking for trouble and BMC will probably tell me to upgrade server if that doesn't work. Man it must be great to have software "up to date" all the time Thanks for any help Tom Fluker Viasystems Technologies
