Re: Two different retention policies for the same node

Michael migdelay of 7 will keep newly changed files for 7 days. Older ones will move off. So your basic OS files and so on won't be there. Only way around that is to run a selective once a week or change MODE to absolute in the backup copygroup on Sunday morning and back to modified on Monday m

Re: Two different retention policies for the same node

Thanks Steven and Wanda! Your ideas are very valuable! I've been thinking about Steven's recipe number 2. It seems ok, but in DR situation I wouldn't really want to mess with DB restores. But what if.. 1. Create a new domain for high priority servers (there are just a few of them) with the sam

Re: TSM V6 Tivoli Clients

Greetings, I think I will weigh in on this one. I think most of our Windows TSM client missed/failed backups fall pretty evenly into four groups: 1) Fixable problems within the OS, including VSS and WMI service failures/hangs. Included in this group is the occasional corrupt file/filesystem, or

Re: Dear Tuscon

On Mar 24, 2009, at 9:56 AM, Kauffman, Tom wrote: The TSM database is about 30 GB used of 46 GB assigned. We have a sub-rate T1 to our hot-site, with an RS-6000 installed. We are currently running mksysb images out to the system with rsync; they run to about 4.7 GB each and take about 1.2 hours.

Re: TDP 5.5.2 Communication Delays

Look here: http://www-01.ibm.com/support/docview.wss?uid=swg21305911 Under the first bullet: "Slow application start up when there is no internet connection" Thanks, Del "ADSM: Dist Stor Manager" wrote on 03/24/2009 01:42:35 PM: > [

Re: Changing a Node´s password

Hi Mario, >From the TSM Server? On the TSM Admin CLI this would be achieved by (logged in as an administrator with appropriate privs): UPDATE NODE You'd need to re-authenticate with this new password at the client side if using PASSWORDACCESS GENERATE in your options file there. This process m

Re: TSM V6 Tivoli Clients

"VSS is like a nose. Sometimes it runs, sometimes it blows." --- me. On Tue, Mar 24, 2009 at 3:05 PM, Zoltan Forray/AC/VCU wrote: > And of course after M$ changes/fixes their problems, they screw-up the TSM > clients which results in another client > patchlather--rinse--repeat >

Re: Changing a Node´s password

>From the TSM Server command line Upd node Thanks Abid Ilias Networking Services and Information Technology The University of Chicago -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Tuesday, March 24, 2009 2:09 PM To: AD

Re: Changing a Node´s password

log into the tsm server as n administrator with propper authority, and type as follows: Update node node-name newpassword All done. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@v

Re: Changing a Node´s password

UPdate it from the TSM server UPDATE NODE NEWPASSWORD -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Tuesday, March 24, 2009 3:09 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Changing a Node´s password Hi list, Is there

Changing a Node´s password

Hi list, Is there any way to change the TSM password for a Node without knowing the current password? Thanks Mario

Re: TSM V6 Tivoli Clients

And of course after M$ changes/fixes their problems, they screw-up the TSM clients which results in another client patchlather--rinse--repeat "ADSM: Dist Stor Manager" wrote on 03/24/2009 02:46:48 PM: > From: > > Richard Sims > > To: > > ADSM-L@VM.MARIST.EDU > > Date: > > 03/24/

Re: TSM V6 Tivoli Clients

On Mar 24, 2009, at 2:35 PM, Timothy Hughes wrote: I agree there are too many issues with the 5.5 clients, I am also hoping for a big improvement with 6.x specifically regarding the VSS issues. From all I've read, the VSS issues are the result of ongoing Microsoft programming errors, of which

Re: TSM V6 Tivoli Clients

Thanks, Todd, Adrian and Robert ! Robert, I agree there are too many issues with the 5.5 clients, I am also hoping for a big improvement with 6.x specifically regarding the VSS issues. regards! Clark, Robert A wrote: Ordinarily, I would agree with this sentiment. But as many problems as I'v

Re: TSM V6 Tivoli Clients

Ordinarily, I would agree with this sentiment. But as many problems as I've seen with the 5.5. clients, I'm hoping all the break fix attention at Tivoli has been focused on 6.x. There is also some pent-up demand for features expected in 6.x. [RC] -Original Message- From: ADSM: Dist Stor

Re: TDP 5.5.2 Communication Delays

I suspect that you are using SSL encryption, and thus certificates, as the IBM Tivoli Storage Manager Versions 5.4 and 5.5 Technical Guide redbook describes. Look into that area. Richard Sims

TDP 5.5.2 Communication Delays

We recently upgraded one of our SQL Servers to TDP SQL 5.5.2. We noticed there was a lag in the time it took to run a manual backup of a database. To check things out, I installed Network Monitor on the server to get an idea of the packets being sent. Here is a summary: Traffic sent by the proc

Re: Dear Tuscon

If you have multiple TSM servers, just backup to a flat file and push the db backup to your other TSM server. (same with hourly incr db backups) (and please don't go down the ~just use server to server communications with virtual volumes~ road... I don't like using virtual volumes on another server

Re: Dear Tuscon

I'm not sure of the true concern with this ? I'm using LTO-4 and yes my tapes that I perform DB backups on are 90%-95% empty afterwards. But to ensure recoverability I can live with that. Also the concern of "expensive" tapes over cheaper lower capacity is relative. "Back in the day" we used lowe

Re: Dear Tuscon

On 20 mrt 2009, at 15:39, Nick Laflamme wrote: My heart leapt when my RSS reader presented me an article in the TSM udpates feed from IBM with the heading, "Keeping more than one TSM server database backup on a tape." As I'm implementing a new server using 3592 drives, I haven't been happy with

Re: Dear Tuscon

The TSM database is about 30 GB used of 46 GB assigned. We have a sub-rate T1 to our hot-site, with an RS-6000 installed. We are currently running mksysb images out to the system with rsync; they run to about 4.7 GB each and take about 1.2 hours. They also put enough load on the corporate intern

Re: Dear Tuscon

How big is your TSM db? If it's not too big and you have extra disk space at both sites, you could: tsm db backup to local file devices compress the file devices copy/rdist/rsync to the dr site "Kauffman, Tom"

Re: Dear Tuscon

I only have one TSM server - and I'm not worried about my local TSM database. Its on an IBM DS-8100 (raid5) mirrored to a second DS-8100. My concern is having a readable TSM database backup off-site for use in a disaster recovery. We're not a big company; we flirt with the bottom end of the Forb

unsubscribe

Terry McColgan Help Desk Support Specialist Tivoli Storage Manager Specialist Ontario College of Teachers 121 Bloor Street East, Floor 6 Toronto, Ontario M4W 3M5 tmccol...@oct.ca 416-961-8800ext. 670 "Go ahead... backup." - Please consider the e

Re: how do I recover DSM records from a crashed SGI server?

The contemporary computer to receive the old SGI's files needs to have a file system which is compatible with the SGI's file system, and the TSM client needs to be programmed to handle that, where you would use the Virtualnodename option in conjunction with the old SGI's client password to access