Re: FYI: Another shop with the archive hang problem... RE: hang ar chive (dsmc) on Sun Solaris

2001-10-23 Thread Michael Oski
We too have this issue occurring on our Solaris 2.6 systems with the 4.1.2 TSM client. I was looking at the 4.2.1 client as a possible solution since the fixed APAR list in the README lists a "fixed dsmc lockup after successfully sending data" entry. I cannot for the life of me find the APAR numbe

Re: Will TSM back up open files on Novell Netware NSS volumes?

2001-07-25 Thread Michael Oski
Not sure if NSS is an issue or not, haven't used Netware in a couple of years. As for open files in general though, I did use St. Bernard Software's Open File Agent (OFA) on a few platforms including a Netware SFT III environment. It's a piece of cake to install and setup, and I used ADSM 3.1, Arc

Re: Antwort: Re: using compression on netware tsm clients

2001-07-17 Thread Michael Oski
Keep in mind that Netware volumes have a feature for compressing the actual files located on disk. Is the process running uncompressing Netware-compressed files, then recompressing them via TSM? I've had issues several years ago where this was the case. MO On Friday, July 13, 2001, at 07:52 AM,

Re: dsm.sys file not being read in aix

2001-06-19 Thread Michael Oski
Richard, I'll give it a try, I was basically stating my understanding of the documentation. It seemed that the point of the scheduler need to be restarted after changing the dsm.opt or dsm.sys files is made, but no mention that the same was true for the inclexcl file. I assumed that this was by d

Re: Space reclamation processes

2001-06-19 Thread Michael Oski
Richard, Wow! You have "advantageous times" - emphasis on the plural?!?! hehe Seriously, I recently "lucked out" and got my DBA group to schedule backups around a daily maintenance schedule - it only took 7 months of pleading and the implementation of a new DR process (thankfully mandated from

Re: dsm.sys file not being read in aix

2001-06-15 Thread Michael Oski
Having include/excludes in the dsm.sys file works, it's just not the preferred method. If you need to adjust your includes/excludes, and a "dsmc sched" process is running, the process will not pick up the changes to dsm.sys since it is read only upon startup. By placing the list in an inclexcl fil

Re: Mac OS X requirements survey

2001-06-06 Thread Michael Oski
The problem with backing up MacOS X files with the Classic client is that the new file attributes will be lost. MacOS up to version 9.1 store resources and attributes for file differently then MacOS X. Many of the files you backup will not restore correctly if the new method of resource and attrib

Re: ADSM/TSM

2001-06-05 Thread Michael Oski
Yes, I do it regularly now that we're building out a new DR site. The things to do are: 1) dsmfmt new DB and Log volumes on the new AIX system 2) start dsmserv with the format option (specifying new log and db volumes) 3) start dsmserv restore db (specifying parameters as necessary to restore you

Re: Netware and Btrieve

2001-06-05 Thread Michael Oski
Are you setting the copy serialization to static/shared static/dynamic/ or shared dynamic? I would think that shared dynamic would allow TSM to grab the file if nothing is being written to it, then release back when done. Unless there's an APAR on not releasing the file handle, I don't see why it

Re: Mac X client requirement's survey

2001-06-05 Thread Michael Oski
At minimum, a command line dsmc & dsmadmc functionality with support for HFS+ and UFS file systems. This way the scheduler could be put in a cron entry for nightly processes. Personally, I don't care much about a gui, but that's because I'm a Unix geek - hehe MO On Tuesday, June 5, 2001, at 12:

Re: Netware client code

2001-06-04 Thread Michael Oski
As for throughput, I get about 20GB to 25GB per hour across 1Gb switched LAN (full duplex). This is going from Sun 450/4500/6500's and RS/6000 H70/H80/S7A/S80's to TSM servers on RS/6000 H70's or S80's. Sounds like 400MB per hour is what you're getting - I'd look first at network interface and swi

Re: Backupsets

2001-06-04 Thread Michael Oski
Scott, I think you can drill down through the monitor.nlm and look at the devices installed on a Netware server. It should give you at least a starting point to determine what name TSM would use. It's been a few years since I worked on a Netware server, but I think from monitor.nlm you select dev

Re: HTTP sessions in TSM 4.1.3.0 (also, memory leak...)

2001-05-24 Thread Michael Oski
Hello, I did quite a bit of testing of different browsers against different patch levels of TSM 3.7 regarding this problem. The key point to remember - DON'T try to cancel the sessions! It will skyrocket your CPU utilization and remain that way until dsmserv is restarted. What I found was that di

Re: TSM client for Mac OS X (again)

2001-05-22 Thread Michael Oski
Well... I'm not exactly dismayed that we announced the pre-installation sooner than originally planned. ;-) I *am*, however, dismayed that Tivoli hasn't mentioned one word about this platform. I can see where a full-function GUI client may take them a little time to complete, but the underlying A

Re: Runaway CPU

2001-04-25 Thread Michael Oski
We, as well have experienced this. I have an environment I can occasionally test issues out on and did some research on browsers running on MacOS X and Solaris. Not sure if other platforms experience the same problems with the same browsers, but FYI this is what I found: The correct behavior can

Re: ANR8359E ANR8830E

2001-04-23 Thread Michael Oski
I've got a dozen or so 3494 Libraries with 2 to 5 3590 E1A's per silo. I typically run into these errors a few times per week on a regular basis. I've also had the micro code upgraded, and had *many* hardware replacements/adjustments performed. At this point, the only thing to do is track the erro

Re: mount failed

2001-04-23 Thread Michael Oski
Do a "q vol E03 f=d" and see if the volume is flagged unavailable. This will happen from time to time if an error is encountered during a read or write operation. The TSM server doesn't know whether the drive or tape are the source of the problem, so it typically will mark both unavailable - o