Re: NT Script to check for failed backups

Hi Jean-Baptiste, I'm really interested in your script. We are backuping about 50 NT servers and our only procedures is to catch information manually from the TSM server. However, we are soon applying a check within the TSM server that will show us if the backup failed or succeed. But i'm very

Re: schedule ADSM

Thanks Del, i feel so stupid, knowing that for a long time. in fact I had modify myself these options on all the nodes. I hadn't take time to check this ###@@!! Thank's. I think it will correct the problem... By the way. with server in 4.1.. or 4.1.5 and a baclient 4.2.1., you only need " befo

Re: schedule ADSM

ve to worry about either set of quotes. Just a thought... Brian Scott EDS - Enterprise Distributed Capabilities MS 3278 Troy, MI 48098 * phone: 248-265-4596 (8-365) * mailto:[EMAIL PROTECTED] -Original Message- From: Regelin Michael (CHA) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May

Re: schedule ADSM

L PROTECTED] Objet : Re: schedule ADSM A "Return code=1" for me means password problem. I usually try to sign onto the client with Domino Command Line and try to do a "domdsmc q adsm" command "Regelin Michael (CHA)"

Re: schedule ADSM

Hi Del, thank's for your response. There is no message in domdsm.log. Only in dsmerr.log (the one configure whith the schedule). Here is the opt file: Commethod tcpip tcpport 1506 TCPServeraddressADSM3 COMPression off DOMain ALL-LOCAL Subdir

schedule ADSM

I'm having problem to schedule a selective backup with TDP for DOMINO 1.1.2. On the server NT, I have 3 different schedule: 1 for Backup/Archive 1 for Incremental and weekly selective (ADSM server = ADSM1 / ADSM node = domino-firm) 1 for monthly selective (ADSM server = ADSN3 / ADSM node = domin

Re: Help Understanding Mgmt classes

p, so retention/expiration must be done manually; in v2 of this TDP, objects stored in backup storage are given the same name, so their retention/expiration becomes "automated" like for files backed up by the b/a-client -- and the management class rules, as I described, will apply. Hope

Re: Help Understanding Mgmt classes

Hi Don, I'm not sure to understand your answer. By the way, thanks for your answer. I'm interested in this mailing and was not the originator. Our Backup solution is based on tdp for domino 1.1.2. Our tsm client is 4.2.1.20 based on Windows Nt4 server. here is our strategy: a full backup a w

Re: TDP performance!!!!!

Hi, A typical behavior of your problem, is that when installing a swtich or a router, sometime there is a collision between the full-duplex and halp-duplex configurtion. Make sure that on your switch (port level) and on your server (Nic level) your have the same parameters (of course full-duplex

Re: expiring object

, use exclude *.nsf exclude *.ntf Bill SmoldtSSSI STORServer, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Regelin Michael (CHA) Sent: Thursday, April 25, 2002 3:42 AM To: [EMAIL PROTECTED] Subject: Re: expiring object Ok thanks. How then s

Re: expiring object

e may be others on a server. Instead, use exclude *.nsf exclude *.ntf Bill SmoldtSSSI STORServer, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Regelin Michael (CHA) Sent: Thursday, April 25, 2002 3:42 AM To: [EMAIL PROTECTED] Subj

Re: expiring object

Ok thanks. How then should I write my dsm.opt file when doing an Incremental backup with Archive Client knowing that TDP will allready backup the *.nsf and *.ntf files ? Should I put an exclude like this in the dsm.opt of the archive client: exclude *:\...\*.n?f And should I consider backupin

Re: expiring object

Thanks Del, I will apply the modifications. By the way, do you know what will happend if to backup trigger the same file and the two backup have different Management Class. Does the two of them apply to determine the expiration delay or is only one applying the expiration ? Thanks in advance.

Re: expiring object

Hi Del, I thought I had to include *.nsf.data only if i had made a exclude of the hole directory Witch is not the case. Isn't it correct ? Example: Exclude mail\* Include mail\user1.nsf include mail\user1.nsf.DATA >

Re: expiring object

Thanks Del, the show version command was very helpful. It show that many files are bound to a managment class that I did not specified. In this case, it is the MC Default that is shown for the most part. But analysing the .OPT file, I'm using the good MC. Maybe the syntax of the command is not c

Re: expiring object

Thanks Del, Our client version is 1.1.2. The command: DOMDSMC QUERY DBB * /SUBDIR=YES" shows all the file with subdir that have been backed up. But only one version is shown. I'm not sure how to use the Show version command ? where do i use it I'm not familiar with command line... thanks

expiring object

Hello, When consulting the gui client for a Restore, I'm surprised to see that some files are not present to be restored. the management class have been set up correctly to keep 13 versions. Only 2 versions are visible (in active and inactive mode). I controled the dsm.opt. It is correctly usin

verbose after successfully backed up

hi there, I have 15 ADSM Nodes installed and running under AIX. I have 15 GUI client installed on 12 Nt server and 3 AIX server Client type: TSM Archive client 4.2.1.20 (full backup of the system) TDP for Domino client 1.1.2 (selective and incremental backup + archivelog for Domino) When the ba