Message if server is waiting for mount over 15 minutes?

[Niklas Lundstrom]

Hello
 
Is there a way to get a warning or a message if a session or process has waited over 
15 minutes for a mount?
 
 
MVH
Niklas Lundström
Föreningssparbanken IT
08-5859 5164
 

Redirect backup to new pool

[Sergey Chernyaev]

Hi all!
After installing new storage device how is more convenient to redirect
BACKUP from old pool to new, but not simultaneously, moving nodes by
turns. All options and schedules for nodes writed on server.

I think, it's need new policy domain, in backup copy group used new
pool, and nodes and schedules moved to this policy domain when needed.

Other ideas?

Other question (may be offtopic): is here anybody from Russia? :)

Re: Failed incremental backup for NT 2003.

[PAC Brion Arnaud]

Hoa,


You'll find an article on Microsoft support web site
(http://support.microsoft.com), which may solve your problem : do a
search for "833167" and you'll be directed to an article about "Time-out
errors occur in Volume Shadow Copy service writers, and shadow copies
are lost during backup and during times when there are high levels of
input/output". There is an associated patch you should ask them and
apply on your client. We did it and it solved the problem !
Cheers. 


Arnaud 


**
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: [EMAIL PROTECTED]

**

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Hoa V Nguyen
Sent: Thursday, 28 October, 2004 18:29
To: [EMAIL PROTECTED]
Subject: Failed incremental backup for NT 2003.

Hi gurus,

Our NT guys have issues to backup NT 2003 with following errors
messages:

10/24/2004 18:44:24 CreateSnapshotSet(): AddToSnapshotSet() returns
hr=VSS_E_UNEXPECTED_PROVIDER_ERROR
10/24/2004 18:44:26 ANS1950E Backup via Microsoft Volume Shadow Copy
failed.  See error log for more detail.

I would appreciated you folks shed some light please.

We have opened a PMR 60173,370 with IBM regarding the windows 2003 TSM
client errors,but didn't hear any good news yet.

Client version: 5.2.3
TSM   5.2.2.3

Thank you.
Hoa.

Re: Redirect backup to new pool

[Henrik Wahlstedt]

Hi,

One way is to copy your policy domain to a new domain. Update your copy
groups to point to new storage pool belonging to the new device.
And update domain option to the new domain for your nodes.


//Henrik





Sergey
ChernyaevTo: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc: (bcc: Henrik Wahlstedt)
CC.RU>   Subject: Redirect backup to new pool
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>


2004-10-29
11:18
Please
respond to
"ADSM: Dist
Stor Manager"






Hi all!
After installing new storage device how is more convenient to redirect
BACKUP from old pool to new, but not simultaneously, moving nodes by
turns. All options and schedules for nodes writed on server.

I think, it's need new policy domain, in backup copy group used new
pool, and nodes and schedules moved to this policy domain when needed.

Other ideas?

Other question (may be offtopic): is here anybody from Russia? :)




---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

ANE4018E : file name too long on AIX

[PAC Brion Arnaud]

Hi List !

I got some bad looking messages on my TSM server (AIX 5.2.0.0  with TSM
5.2.2.1) yesterday, like :

10/27/04 19:55:52 ANE4018E (Session: 380998, Node: X )
Error process 
   ing
'/fswas/was51/AppServer/installedApps/pacrs800Networ 
 
k/AirWarder_1.6.4.16_train.ear/AirWarderScheduleEJB.jar':
   file name too long(SESSION: 380998)

The client is installed on a AIX 5.2.0.0 and has version 5.2.0.0. 
I can't understand why I'm getting those errors, as AFAIK, TSM is
supposed to handle long file names so far they're supported by the OS,
which is the case here !
Something else to note : this  AirWarderScheduleEJB.jar is not a file,
but a directory, so it looks like the TSM client is not searching
further in the directory tree, which is only one directory deeper, for
finding files to backup.
Someone having an idea on this ?
TIA, cheers.

Arnaud 


**
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: [EMAIL PROTECTED]

**

Re: Redirect backup to new pool

[Sergey Chernyaev]

Henrick, so I also thought :)

After moving node to a new policy domain, data stored in old pool moved
to new pool?

Thanks

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Henrik Wahlstedt
Sent: Friday, October 29, 2004 2:27 PM
To: [EMAIL PROTECTED]
Subject: Re: Redirect backup to new pool

Hi,

One way is to copy your policy domain to a new domain. Update your copy
groups to point to new storage pool belonging to the new device.
And update domain option to the new domain for your nodes.


//Henrik





Sergey
ChernyaevTo: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc: (bcc: Henrik Wahlstedt)
CC.RU>   Subject: Redirect backup to
new pool
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>


2004-10-29
11:18
Please
respond to
"ADSM: Dist
Stor Manager"






Hi all!
After installing new storage device how is more convenient to redirect
BACKUP from old pool to new, but not simultaneously, moving nodes by
turns. All options and schedules for nodes writed on server.

I think, it's need new policy domain, in backup copy group used new
pool, and nodes and schedules moved to this policy domain when needed.

Other ideas?

Other question (may be offtopic): is here anybody from Russia? :)




---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the information or copying of this message is prohibited. If you are not
the addressee, please notify the sender immediately by return e-mail and
delete this message.
Thank you.

Re: Redirect backup to new pool

[Henrik Wahlstedt]

Hi again Sergey,

Not automaticlly, you have to do a 'move nodedata YourNode From=Old stgpol
To=New stgpool'.
Or a move data depending of what suits your best.


//Henrik






Sergey
ChernyaevTo: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc: (bcc: Henrik Wahlstedt)
CC.RU>   Subject: Re: Redirect backup to new pool
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>


2004-10-29
12:36
Please
respond to
"ADSM: Dist
Stor Manager"






Henrick, so I also thought :)

After moving node to a new policy domain, data stored in old pool moved
to new pool?

Thanks

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Henrik Wahlstedt
Sent: Friday, October 29, 2004 2:27 PM
To: [EMAIL PROTECTED]
Subject: Re: Redirect backup to new pool

Hi,

One way is to copy your policy domain to a new domain. Update your copy
groups to point to new storage pool belonging to the new device.
And update domain option to the new domain for your nodes.


//Henrik





Sergey
ChernyaevTo: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc: (bcc: Henrik Wahlstedt)
CC.RU>   Subject: Redirect backup to
new pool
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>


2004-10-29
11:18
Please
respond to
"ADSM: Dist
Stor Manager"






Hi all!
After installing new storage device how is more convenient to redirect
BACKUP from old pool to new, but not simultaneously, moving nodes by
turns. All options and schedules for nodes writed on server.

I think, it's need new policy domain, in backup copy group used new
pool, and nodes and schedules moved to this policy domain when needed.

Other ideas?

Other question (may be offtopic): is here anybody from Russia? :)




---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the information or copying of this message is prohibited. If you are not
the addressee, please notify the sender immediately by return e-mail and
delete this message.
Thank you.




---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

Re: Redirect backup to new pool

[Sergey Chernyaev]

Henrick, big thanks fo your help! 

I have'nt time now to finding these things in manuals (( 

With best regards,
Sergey


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Henrik Wahlstedt
Sent: Friday, October 29, 2004 2:56 PM
To: [EMAIL PROTECTED]
Subject: Re: Redirect backup to new pool

Hi again Sergey,

Not automaticlly, you have to do a 'move nodedata YourNode From=Old
stgpol To=New stgpool'.
Or a move data depending of what suits your best.


//Henrik






Sergey
ChernyaevTo: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc: (bcc: Henrik Wahlstedt)
CC.RU>   Subject: Re: Redirect
backup to new pool
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>


2004-10-29
12:36
Please
respond to
"ADSM: Dist
Stor Manager"






Henrick, so I also thought :)

After moving node to a new policy domain, data stored in old pool moved
to new pool?

Thanks

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Henrik Wahlstedt
Sent: Friday, October 29, 2004 2:27 PM
To: [EMAIL PROTECTED]
Subject: Re: Redirect backup to new pool

Hi,

One way is to copy your policy domain to a new domain. Update your copy
groups to point to new storage pool belonging to the new device.
And update domain option to the new domain for your nodes.


//Henrik





Sergey
ChernyaevTo: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc: (bcc: Henrik Wahlstedt)
CC.RU>   Subject: Redirect backup to
new pool
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>


2004-10-29
11:18
Please
respond to
"ADSM: Dist
Stor Manager"






Hi all!
After installing new storage device how is more convenient to redirect
BACKUP from old pool to new, but not simultaneously, moving nodes by
turns. All options and schedules for nodes writed on server.

I think, it's need new policy domain, in backup copy group used new
pool, and nodes and schedules moved to this policy domain when needed.

Other ideas?

Other question (may be offtopic): is here anybody from Russia? :)




---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the information or copying of this message is prohibited. If you are not
the addressee, please notify the sender immediately by return e-mail and
delete this message.
Thank you.




---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the information or copying of this message is prohibited. If you are not
the addressee, please notify the sender immediately by return e-mail and
delete this message.
Thank you.

AW: Failed incremental backup for NT 2003.

[Stefan Holzwarth]

Arnaud,
Thank you very much for this valuable information.
Since 5.2.2.x we see that error and where looking for the reason.
There where some fixes in TSM but you know it was only the half of the whole
thing.
Kind regards,
Stefan Holzwarth

-Ursprüngliche Nachricht-
Von: PAC Brion Arnaud [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 29. Oktober 2004 11:40
An: [EMAIL PROTECTED]
Betreff: Re: Failed incremental backup for NT 2003.


Hoa,


You'll find an article on Microsoft support web site
(http://support.microsoft.com), which may solve your problem : do a
search for "833167" and you'll be directed to an article about "Time-out
errors occur in Volume Shadow Copy service writers, and shadow copies
are lost during backup and during times when there are high levels of
input/output". There is an associated patch you should ask them and
apply on your client. We did it and it solved the problem !
Cheers. 


Arnaud 


**
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: [EMAIL PROTECTED]

**

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Hoa V Nguyen
Sent: Thursday, 28 October, 2004 18:29
To: [EMAIL PROTECTED]
Subject: Failed incremental backup for NT 2003.

Hi gurus,

Our NT guys have issues to backup NT 2003 with following errors
messages:

10/24/2004 18:44:24 CreateSnapshotSet(): AddToSnapshotSet() returns
hr=VSS_E_UNEXPECTED_PROVIDER_ERROR
10/24/2004 18:44:26 ANS1950E Backup via Microsoft Volume Shadow Copy
failed.  See error log for more detail.

I would appreciated you folks shed some light please.

We have opened a PMR 60173,370 with IBM regarding the windows 2003 TSM
client errors,but didn't hear any good news yet.

Client version: 5.2.3
TSM   5.2.2.3

Thank you.
Hoa.

Re: ANE4018E : file name too long on AIX

[Richard Sims]

On Oct 29, 2004, at 6:32 AM, PAC Brion Arnaud wrote:
I got some bad looking messages on my TSM server (AIX 5.2.0.0  with TSM
5.2.2.1) yesterday, like :
10/27/04 19:55:52 ANE4018E (Session: 380998, Node: X )
Error processing '/fswas/was51/AppServer/installedApps/pacrs800Networ
k/AirWarder_1.6.4.16_train.ear/AirWarderScheduleEJB.jar':
file name too long(SESSION: 380998)
The client is installed on a AIX 5.2.0.0 and has version 5.2.0.0.
I can't understand why I'm getting those errors, as AFAIK, TSM is
supposed to handle long file names so far they're supported by the OS,
which is the case here !
Something else to note : this  AirWarderScheduleEJB.jar is not a file,
but a directory, so it looks like the TSM client is not searching
further in the directory tree, which is only one directory deeper, for
finding files to backup.
Someone having an idea on this ?
Arnaud - In that we haven't heard of this message for a long time, the
 problem may be with the file or file system itself.
As the (Unix) client manual says: "As long as the file system allows
creation of the file, the Tivoli Storage Manager client will back up
or archive the file."
I would do 'ls -aldx' on that file system object.  When dealing with
file names, what you see in a simple ls is not necessarily reality,
in that there may be binary crud in there, which the 'x' will reveal.
Your observation that the object is not a file is interesting.  A
.jar suffix is supposed to denote a Java ARchive *file*, not a
directory.  So something seems wrong there.
I would further examine the ls output to see if the object has any
unusual characteristics, perhaps being a hard link.  I would see if
'dsmc s' on it yielded different results than 'dsmc i'.  If so,
contact TSM Support to have them pursue.  You might also try boosting
the client level beyond base 5.2.0.0 and see if any difference,
before calling.
   Richard Sims

Re: Failed incremental backup for NT 2003.

[Hoa V Nguyen]

Appreciated Arnaud & Richard.

Hoa Nguyen.



PAC Brion Arnaud <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/29/2004 04:40 AM
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
Re: Failed incremental backup for NT 2003.






Hoa,


You'll find an article on Microsoft support web site
(http://support.microsoft.com), which may solve your problem : do a
search for "833167" and you'll be directed to an article about "Time-out
errors occur in Volume Shadow Copy service writers, and shadow copies
are lost during backup and during times when there are high levels of
input/output". There is an associated patch you should ask them and
apply on your client. We did it and it solved the problem !
Cheers.


Arnaud


**
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: [EMAIL PROTECTED]

**

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Hoa V Nguyen
Sent: Thursday, 28 October, 2004 18:29
To: [EMAIL PROTECTED]
Subject: Failed incremental backup for NT 2003.

Hi gurus,

Our NT guys have issues to backup NT 2003 with following errors
messages:

10/24/2004 18:44:24 CreateSnapshotSet(): AddToSnapshotSet() returns
hr=VSS_E_UNEXPECTED_PROVIDER_ERROR
10/24/2004 18:44:26 ANS1950E Backup via Microsoft Volume Shadow Copy
failed.  See error log for more detail.

I would appreciated you folks shed some light please.

We have opened a PMR 60173,370 with IBM regarding the windows 2003 TSM
client errors,but didn't hear any good news yet.

Client version: 5.2.3
TSM   5.2.2.3

Thank you.
Hoa.

Re: ANE4018E : file name too long on AIX

[PAC Brion Arnaud]

Hi Richard,

First of all, thanks for your response !
Now concerning the tests your asked me to perform :
1) ls -aldx did not show anything abnormal -> only regular files, no
links
2) selective backup : was successful !

To test further, I even tried to create a new file under that directory
and to run an incremental backup : here again, no problem ...
It looks like that problem can't be reproduced, or that it appears only
during scheduled backups ...
I'm going to wait until tomorrow (or better said Monday, as the W.E. is
near), to see if this happens again, and react in consequence of the
results ...

Cheers.

Arnaud 


**
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: [EMAIL PROTECTED]

**

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Friday, 29 October, 2004 14:02
To: [EMAIL PROTECTED]
Subject: Re: ANE4018E : file name too long on AIX

On Oct 29, 2004, at 6:32 AM, PAC Brion Arnaud wrote:
> I got some bad looking messages on my TSM server (AIX 5.2.0.0  with 
> TSM
> 5.2.2.1) yesterday, like :
>
> 10/27/04 19:55:52 ANE4018E (Session: 380998, Node: X )
> Error processing '/fswas/was51/AppServer/installedApps/pacrs800Networ
> k/AirWarder_1.6.4.16_train.ear/AirWarderScheduleEJB.jar':
> file name too long(SESSION: 380998)
>
> The client is installed on a AIX 5.2.0.0 and has version 5.2.0.0.
> I can't understand why I'm getting those errors, as AFAIK, TSM is 
> supposed to handle long file names so far they're supported by the OS,

> which is the case here !
> Something else to note : this  AirWarderScheduleEJB.jar is not a file,

> but a directory, so it looks like the TSM client is not searching 
> further in the directory tree, which is only one directory deeper, for

> finding files to backup.
> Someone having an idea on this ?

Arnaud - In that we haven't heard of this message for a long time, the
  problem may be with the file or file system itself.
As the (Unix) client manual says: "As long as the file system allows
creation of the file, the Tivoli Storage Manager client will back up or
archive the file."

I would do 'ls -aldx' on that file system object.  When dealing with
file names, what you see in a simple ls is not necessarily reality, in
that there may be binary crud in there, which the 'x' will reveal.

Your observation that the object is not a file is interesting.  A .jar
suffix is supposed to denote a Java ARchive *file*, not a directory.  So
something seems wrong there.

I would further examine the ls output to see if the object has any
unusual characteristics, perhaps being a hard link.  I would see if
'dsmc s' on it yielded different results than 'dsmc i'.  If so, contact
TSM Support to have them pursue.  You might also try boosting the client
level beyond base 5.2.0.0 and see if any difference, before calling.

Richard Sims

Re: ANE4018E : file name too long on AIX

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of PAC Brion Arnaud
>First of all, thanks for your response !
>Now concerning the tests your asked me to perform :
>1) ls -aldx did not show anything abnormal -> only regular 
>files, no links
>2) selective backup : was successful !
>
>To test further, I even tried to create a new file under that 
>directory and to run an incremental backup : here again, no problem ...
>It looks like that problem can't be reproduced, or that it 
>appears only during scheduled backups ...

Possible source of your problem:

When a manual backup works, but a scheduled one doesn't, the problem is
almost always one of permissions.

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
Office 262.521.5627  

Client upgrade to 5.2.3.1

[Bill Dourado]

Hello All,

I have just upgraded a client from 5.2.2.0 to 5.2.3.1 as recommended by
IBM
and this list,  to get over a problem.

This is part of the log of the first scheduled backup since the upgrade :

29-10-2004 14:04:26 Total number of objects inspected:   22,734
29-10-2004 14:04:26 Total number of objects backed up:0
29-10-2004 14:04:26 Total number of objects updated:  1
29-10-2004 14:04:26 Total number of objects rebound:  0
29-10-2004 14:04:26 Total number of objects deleted:  0
29-10-2004 14:04:26 Total number of objects expired: 33
29-10-2004 14:04:26 Total number of objects failed:  22,734
29-10-2004 14:04:26 Total number of bytes transferred: 1.59 GB
29-10-2004 14:04:26 Data transfer time:   19.09 sec
29-10-2004 14:04:26 Network data transfer rate:87,603.71 KB/sec
29-10-2004 14:04:26 Aggregate data transfer rate:  4,737.23 KB/sec
29-10-2004 14:04:26 Objects compressed by:0%
29-10-2004 14:04:26 Elapsed processing time:   00:05:53
29-10-2004 14:04:26 --- SCHEDULEREC STATUS END
29-10-2004 14:04:26 --- SCHEDULEREC OBJECT END S2321_ONE_OFF 29-10-2004
13:35:00
29-10-2004 14:04:26 Scheduled event 'S2321_ONE_OFF' completed
successfully.


All seems to be OK except the statistics(1.59 GB was backed up after all)

29-10-2004 14:04:26 Total number of objects inspected:   22,734
29-10-2004 14:04:26 Total number of objects failed:  22,734


Has anybody experienced this before ?

TSM Server for Windows 5.2.2.0  -OS  Windows Server 2003
TSM Client Backup/Archive 5.2.3.1-OS   Windows Server 2003

Thanks

Bill

Is it possible to save an MVS dataset with the TSM Backup Client dsmc in OMVS (Open Edition UNIX)

[Werner Nussbaumer]

Is it possible to start the TSM Client "dsmc" in Open Edition OMVS (UNIX) and in OMVS 
dsmc to backup an MVS dataset?
 
Thanks for any help,
regards
Werner Nussbaumer

Re: Client upgrade to 5.2.3.1

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Bill Dourado
>I have just upgraded a client from 5.2.2.0 to 5.2.3.1 as 
>recommended by IBM and this list,  to get over a problem.
[snip]

What does the rest of the dsmsched.log say? (If you have the QUIET
option in your dsm.opt file, remark it out, and let the scheduled backup
run again.)

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
Office 262.521.5627  

SAN partition as snapshot partition

[Sandra]

Dear List,
I have to take backup of Windows 2000 machine with open file support. It has 2
partitions C: and D:, and both are critical. If I am going to take image or
snapshot backup, It can't perform it because none of these two partitions can
hold snapshot location.

Is there any workaround to this?

Can I use SAN partition as snapshot location?

Kind Regards,
Sandra

Re: Notes TDP 5.1.5

[Del Hoobler]

Gerald,

A few points and comments:

- Keep in mind that the Domino transaction log is one large
  logical log file (in 64M segments) that contains entries
  for each and every logged database. It was built for
  not only built for crash recoverability... but also to
  enhance performance during standard production operations.

- Data Protection for Domino actually uses a log "prefetch"
  algorithm. That is, while the Domino server is replaying the
  current transaction log, Data Protection for Domino uses
  another set of threads to start restoring the next logical
  transaction log in sequence. The log prefetch and the log replay
  are performed simultaneously to maximize efficiency.
  Data Protection for Domino prefetches one log ahead.
  If the Domino server starts asking for logs file out of sequence,
  prefetching is automatically turned off.

- You can also turn "prefetching" off to see if prefetching is actually
  detrimental in your environment. You can turn it off by adding
  the following to "domdsm.cfg" (or whatever configuration file
  you are using):
 LOGPREfetch NO

- It is true that transaction log replay can be quite lengthy.
  Many customers set up a procedure to perform full database backups
  more often so that the log replay time for restores is smaller
  because there are less transaction logs to replay.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/28/2004
07:58:50 PM:

> A question regarding TDP if anyone knows for sure..
>
> The way the Notes TDP replays incremental logs is it pulls down a
> single 64MB TXN file at a time, replays those transactions, then pulls
> the next one down (restores). It's a pretty slow process that spends
> most of the restore time actually replaying the transactions. The
> restore of those single TXN files is quick and dirty. If a restore
> takes 12 hours to do the incremental portion, most of those 20 hours
> isn't restoring the actual TXN files but rather replaying the data
> between each TXN file.
>
> Does anyone know if theres a quicker way? Perhaps i can selectively
> restore all TXN files and dump them to disk someplace, then initiate a
> Notes command to replay them straight off disk, taking TSM out of the
> equation and more importantly, freeing up the drive for another job?

Re: SAN partition as snapshot partition

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Sandra
>I have to take backup of Windows 2000 machine with open file 
>support. It has 2 partitions C: and D:, and both are critical. 
>If I am going to take image or snapshot backup, It can't 
>perform it because none of these two partitions can hold 
>snapshot location.

You should be able to put the snapshot location for D: onto C:.

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
Office 262.521.5627  

Re: TSM on AS/400

[Smith, Rachel]

Del,

I am looking for the log file that reports the activity/errors of the
backup on the client.
It captures the same log as the dsmsched.log but on the OS/400.

Thanks,
Rachel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: 28 October 2004 17:25
To: [EMAIL PROTECTED]
Subject: Re: TSM on AS/400


Rachel,

What exactly are you looking for?
dsmsched.log is the default output file of the TSM BA scheduler...
... which doesn't exists on OS/400. Can you be more specific on
what you are trying to find out?

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/28/2004
12:00:59 PM:

> Del,
>
> Yes, we are using Data Protection for Lotus Domino to perform the
> backups.
> I am not sure what tool was used to setup the scheduler...!
>
> Rachel.
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
> Del Hoobler
> Sent: 28 October 2004 13:35
> To: [EMAIL PROTECTED]
> Subject: Re: TSM on AS/400
>
>
> Rachel,
>
> There is not a native TSM BA Client or scheduler for OS/400.
> Are you using Data Protection for Lotus Domino to perform your
backups?
> What tool did you use to set up automated scheduling?
>
> Thanks,
>
> Del
>
> 
>
> "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/28/2004
> 07:27:00 AM:
>
> > Hi,
> >
> > We have just started testing TSM backups on an AS/400 running Lotus
> > Domino.
> > Can you tell me where I would find the dsmsched.log file within
> Domino?
> >
> >
> > Thanks

Re: SAN partition as snapshot partition

[Sandra]

Yes I know that but what about snapshot location of D?
I want to take backup of C and D at the same time, using schedule!
Later on I will have to take image backups of C and D too.

Regards,
Sandra

"Stapleton, Mark" wrote:

> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
> Behalf Of Sandra
> >I have to take backup of Windows 2000 machine with open file
> >support. It has 2 partitions C: and D:, and both are critical.
> >If I am going to take image or snapshot backup, It can't
> >perform it because none of these two partitions can hold
> >snapshot location.
>
> You should be able to put the snapshot location for D: onto C:.
>
> --
> Mark Stapleton ([EMAIL PROTECTED])
> Berbee Information Networks
> Office 262.521.5627

Re: Client upgrade to 5.2.3.1

[Bill Dourado]

Mark,

Thankyou for your reponse.

QUEIT option not in use.hundreds of files were backed up...
the log file is too long...nothing unusual appears..

Extracts:-

Executing scheduled command now.
29-10-2004 13:58:33 Node Name: S2321
29-10-2004 13:58:33 Session established with server TSM1: Windows
29-10-2004 13:58:33   Server Version 5, Release 2, Level 2.0
29-10-2004 13:58:33   Server date/time: 29-10-2004 13:59:35  Last access:
29-10-2004 13:34:17

29-10-2004 13:58:33 --- SCHEDULEREC OBJECT BEGIN S2321_ONE_OFF 29-10-2004
13:35:00
29-10-2004 13:58:33 Incremental backup of volume '\\s2321\c$'
29-10-2004 13:58:33 Incremental backup of volume '\\s2321\d$'
29-10-2004 13:58:33 Incremental backup of volume 'SYSTEMSTATE'
29-10-2004 13:58:33 Backup System State using shadow copy...
29-10-2004 13:58:37 Backup System State: 'System Files'.

29-10-2004 13:58:37 Backup System State: 'Registry'.

29-10-2004 13:58:37 Backup System State: 'COM+ Database'.

29-10-2004 13:58:37 Incremental backup of volume 'SYSTEMSERVICES'
29-10-2004 13:58:37 Backup System Services using shadow copy...
29-10-2004 13:58:39 Backup System Service: 'WMI Database'.

29-10-2004 13:58:39 Backup System Service: 'Event Log'.

29-10-2004 13:58:39 ANS1898I * Processed 1,000 files *
29-10-2004 13:58:39 Directory-->   0 \\s2321\c$\ [Sent]
29-10-2004 13:58:39 Directory-->   0 \\s2321\c$\ADSM.SYS
Changed
29-10-2004 13:58:39 Retry # 1  Directory-->   0
\\s2321\c$\ [Sent]
29-10-2004 13:58:39 Directory-->   0
\\s2321\c$\ADSM.SYS\xml.state [Sent]
29-10-2004 13:58:39 Directory-->   0 \\s2321\c$\Documents
and Settings\Administrator.DMN [Sent]
29-10-2004 13:58:39 ANS1228E Sending of object '\\s2321\c$\ADSM.SYS'
failed
29-10-2004 13:58:40 ANS4037E File '\\s2321\c$\ADSM.SYS' changed during
processing.  File skipped.
.
.
.
.
.
.

29-10-2004 13:59:20 Directory-->   0 \\s2321\d$\ [Sent]
29-10-2004 13:59:20 Directory-->   0
\\s2321\d$\Registration [Sent]
29-10-2004 13:59:20 Directory-->   0 \\s2321\d$\System
Volume Information [Sent]
29-10-2004 13:59:21 ANS1898I * Processed11,000 files *
29-10-2004 13:59:21 Normal File-->   354
\\s2321\d$\Interface\Adverts.txt [Sent]
29-10-2004 13:59:22 Directory-->   0
\\s2321\d$\Lotus\Domino\Data [Sent]
29-10-2004 13:59:23 ANS1898I * Processed11,500 files *
29-10-2004 13:59:23 Normal File--> 7,378
\\s2321\d$\Lotus\Domino\notes.ini [Sent]
29-10-2004 13:59:23 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\A&L SIP's & SAR's.ft [Sent]
29-10-2004 13:59:23 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\gtrhome [Sent]
29-10-2004 13:59:23 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\IBM_TECHNICAL_SUPPORT [Sent]
29-10-2004 13:59:23 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\LeaverNotify.ft [Sent]
29-10-2004 13:59:23 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\log.ft [Sent]
29-10-2004 13:59:23 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\mail [Sent]
29-10-2004 13:59:24 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\names.ft [Sent]
29-10-2004 13:59:24 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\PersonInfo.ft [Sent]
29-10-2004 13:59:24 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\PrintRequests.ft [Sent]
29-10-2004 13:59:24 Directory-->   0
\\s2321\d$\Lotus\Domino\Data\ShipReqSys.ft [Sent]
29-10-2004 13:59:24 Normal File--> 2,010
\\s2321\d$\Lotus\Domino\Data\admindata.xml [Sent]
29-10-2004 13:59:24 Normal File-->   201
\\s2321\d$\Lotus\Domino\Data\diagindex.nbf [Sent]
29-10-2004 13:59:24 Normal File--> 6,564
\\s2321\d$\Lotus\Domino\Data\fault_recovery.hst [Sent]
29-10-2004 13:59:24 Normal File-->   713,425
\\s2321\d$\Lotus\Domino\Data\fault_recovery.log [Sent]
29-10-2004 13:59:24 Normal File-->26
\\s2321\d$\Lotus\Domino\Data\ini.nbf [Sent]
29-10-2004 13:59:24 Normal File--> 1,542
\\s2321\d$\Lotus\Domino\Data\JOBSCHED.NJF [Sent]
29-10-2004 13:59:24 Normal File-->   408
\\s2321\d$\Lotus\Domino\Data\loadmon.ncf [Sent]
29-10-2004 13:59:24 Normal File--> 2,883,584
\\s2321\d$\Lotus\Domino\Data\Motiva.BAD [Sent]
29-10-2004 13:59:24 Normal File-->   100
\\s2321\d$\Lotus\Domino\Data\nsd.ini [Sent]
29-10-2004 13:59:24 Normal File--> 2,680
\\s2321\d$\Lotus\Domino\Data\nsdsysinfo.idx [Sent]
29-10-2004 13:59:24 Normal File-->   140
\\s2321\d$\Lotus\Domino\Data\pid.nbf [Sent]

.
.
.
.
.
.
9-10-2004 14:04:24 Directory-->   0 C:\adsm.sys  Changed
29-10-2004 14:04:24 Directory-->   0 C:\adsm.sys\xml.state
[Sent]
29-10-2004 14:04:25 ANS1228E Sending of object 'C:\adsm.sys' failed
29-10-2004 14:04:25 ANS4037E File 'C:\adsm.sys' changed dur

Re: TSM on AS/400

[Del Hoobler]

Rachel,

By default, the log file name is "DOMDSM.LOG".
This log file contains operation parameters and summary statistics.
It does not contain a list of each database processed.
You can obtain that by looking at the redirected command output.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/29/2004
10:40:26 AM:

> Del,
>
> I am looking for the log file that reports the activity/errors of the
> backup on the client.
> It captures the same log as the dsmsched.log but on the OS/400.
>
> Thanks,
> Rachel
>

Re: Client upgrade to 5.2.3.1

[Andrew Raibeck]

Bill,

This looks like APAR IC41440 which was introduced in version 5.2.2.9. A
fix is not yet available.

I suggest adding

   exclude.dir c:\adsm.sys

to your options file and restartnig the scheduler.

The circumvention documented in the APAR also recommends makeing sure you
are usint SHRSTATIC serialization.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/29/2004
07:42:40:

> Mark,
>
> Thankyou for your reponse.
>
> QUEIT option not in use.hundreds of files were backed up...
> the log file is too long...nothing unusual appears..
>
> Extracts:-
>
> Executing scheduled command now.
> 29-10-2004 13:58:33 Node Name: S2321
> 29-10-2004 13:58:33 Session established with server TSM1: Windows
> 29-10-2004 13:58:33   Server Version 5, Release 2, Level 2.0
> 29-10-2004 13:58:33   Server date/time: 29-10-2004 13:59:35  Last
access:
> 29-10-2004 13:34:17
>
> 29-10-2004 13:58:33 --- SCHEDULEREC OBJECT BEGIN S2321_ONE_OFF
29-10-2004
> 13:35:00
> 29-10-2004 13:58:33 Incremental backup of volume '\\s2321\c$'
> 29-10-2004 13:58:33 Incremental backup of volume '\\s2321\d$'
> 29-10-2004 13:58:33 Incremental backup of volume 'SYSTEMSTATE'
> 29-10-2004 13:58:33 Backup System State using shadow copy...
> 29-10-2004 13:58:37 Backup System State: 'System Files'.
>
> 29-10-2004 13:58:37 Backup System State: 'Registry'.
>
> 29-10-2004 13:58:37 Backup System State: 'COM+ Database'.
>
> 29-10-2004 13:58:37 Incremental backup of volume 'SYSTEMSERVICES'
> 29-10-2004 13:58:37 Backup System Services using shadow copy...
> 29-10-2004 13:58:39 Backup System Service: 'WMI Database'.
>
> 29-10-2004 13:58:39 Backup System Service: 'Event Log'.
>
> 29-10-2004 13:58:39 ANS1898I * Processed 1,000 files *
> 29-10-2004 13:58:39 Directory-->   0 \\s2321\c$\ [Sent]
> 29-10-2004 13:58:39 Directory-->   0 \\s2321\c$\ADSM.SYS
> Changed
> 29-10-2004 13:58:39 Retry # 1  Directory-->   0
> \\s2321\c$\ [Sent]
> 29-10-2004 13:58:39 Directory-->   0
> \\s2321\c$\ADSM.SYS\xml.state [Sent]
> 29-10-2004 13:58:39 Directory-->   0
\\s2321\c$\Documents
> and Settings\Administrator.DMN [Sent]
> 29-10-2004 13:58:39 ANS1228E Sending of object '\\s2321\c$\ADSM.SYS'
> failed
> 29-10-2004 13:58:40 ANS4037E File '\\s2321\c$\ADSM.SYS' changed during
> processing.  File skipped.
> .
> .
> .
> .
> .
> .
>
> 29-10-2004 13:59:20 Directory-->   0 \\s2321\d$\ [Sent]
> 29-10-2004 13:59:20 Directory-->   0
> \\s2321\d$\Registration [Sent]
> 29-10-2004 13:59:20 Directory-->   0 \\s2321\d$\System
> Volume Information [Sent]
> 29-10-2004 13:59:21 ANS1898I * Processed11,000 files *
> 29-10-2004 13:59:21 Normal File-->   354
> \\s2321\d$\Interface\Adverts.txt [Sent]
> 29-10-2004 13:59:22 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data [Sent]
> 29-10-2004 13:59:23 ANS1898I * Processed11,500 files *
> 29-10-2004 13:59:23 Normal File--> 7,378
> \\s2321\d$\Lotus\Domino\notes.ini [Sent]
> 29-10-2004 13:59:23 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\A&L SIP's & SAR's.ft [Sent]
> 29-10-2004 13:59:23 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\gtrhome [Sent]
> 29-10-2004 13:59:23 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\IBM_TECHNICAL_SUPPORT [Sent]
> 29-10-2004 13:59:23 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\LeaverNotify.ft [Sent]
> 29-10-2004 13:59:23 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\log.ft [Sent]
> 29-10-2004 13:59:23 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\mail [Sent]
> 29-10-2004 13:59:24 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\names.ft [Sent]
> 29-10-2004 13:59:24 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\PersonInfo.ft [Sent]
> 29-10-2004 13:59:24 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\PrintRequests.ft [Sent]
> 29-10-2004 13:59:24 Directory-->   0
> \\s2321\d$\Lotus\Domino\Data\ShipReqSys.ft [Sent]
> 29-10-2004 13:59:24 Normal File--> 2,010
> \\s2321\d$\Lotus\Domino\Data\admindata.xml [Sent]
> 29-10-2004 13:59:24 Normal File-->   201
> \\s2321\d$\Lotus\Domino\Data\diagindex.nbf [Sent]
> 29-10-2004 13:59:24 Normal File--> 6,564
> \\s2321\d$\Lotus\Domino\Data\fault_recovery.hst [Sent]
> 29-10-2004 13:59:24 Normal File-->   713,425
> \\s2321\d$\Lotus\Domino\Data\fault_recovery.log [Sent]
> 29-10-2004 13:59:24 Normal File-->26
> \\s2321\d$\Lotus\Domino\Data\ini.nbf [Sent]
> 

Re: TSM on AS/400

[Smith, Rachel]

Del,

I looked at the DOMDSM.LOG but there was no information in it that would
explain why a backup was queuing.
The tsm server was operating with no reported errors so I was looking
for some type of output that would explain why it happened...

What do you mean by redirected command output? Do you mean when the
backup is started to send output to a file?

Thanks for your help,
Rachel 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: 29 October 2004 16:17
To: [EMAIL PROTECTED]
Subject: Re: TSM on AS/400


Rachel,

By default, the log file name is "DOMDSM.LOG".
This log file contains operation parameters and summary statistics.
It does not contain a list of each database processed.
You can obtain that by looking at the redirected command output.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/29/2004
10:40:26 AM:

> Del,
>
> I am looking for the log file that reports the activity/errors of the
> backup on the client.
> It captures the same log as the dsmsched.log but on the OS/400.
>
> Thanks,
> Rachel
>

Re: Client upgrade to 5.2.3.1

[Warren, Matthew (Retail)]

I think the number of bytes transferred also includes information the
client and server send between each other - filepsace lists etc.. to
determine what requires backup.

Matt.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bill Dourado
Sent: Friday, October 29, 2004 2:51 PM
To: [EMAIL PROTECTED]
Subject: Client upgrade to 5.2.3.1

Hello All,

I have just upgraded a client from 5.2.2.0 to 5.2.3.1 as recommended by
IBM
and this list,  to get over a problem.

This is part of the log of the first scheduled backup since the upgrade
:

29-10-2004 14:04:26 Total number of objects inspected:   22,734
29-10-2004 14:04:26 Total number of objects backed up:0
29-10-2004 14:04:26 Total number of objects updated:  1
29-10-2004 14:04:26 Total number of objects rebound:  0
29-10-2004 14:04:26 Total number of objects deleted:  0
29-10-2004 14:04:26 Total number of objects expired: 33
29-10-2004 14:04:26 Total number of objects failed:  22,734
29-10-2004 14:04:26 Total number of bytes transferred: 1.59 GB
29-10-2004 14:04:26 Data transfer time:   19.09 sec
29-10-2004 14:04:26 Network data transfer rate:87,603.71 KB/sec
29-10-2004 14:04:26 Aggregate data transfer rate:  4,737.23 KB/sec
29-10-2004 14:04:26 Objects compressed by:0%
29-10-2004 14:04:26 Elapsed processing time:   00:05:53
29-10-2004 14:04:26 --- SCHEDULEREC STATUS END
29-10-2004 14:04:26 --- SCHEDULEREC OBJECT END S2321_ONE_OFF 29-10-2004
13:35:00
29-10-2004 14:04:26 Scheduled event 'S2321_ONE_OFF' completed
successfully.


All seems to be OK except the statistics(1.59 GB was backed up after
all)

29-10-2004 14:04:26 Total number of objects inspected:   22,734
29-10-2004 14:04:26 Total number of objects failed:  22,734


Has anybody experienced this before ?

TSM Server for Windows 5.2.2.0  -OS  Windows Server 2003
TSM Client Backup/Archive 5.2.3.1-OS   Windows Server 2003

Thanks

Bill


___ Disclaimer Notice __
This message and any attachments are confidential and should only be read by those to 
whom they are addressed. If you are not the intended recipient, please contact us, 
delete the message from your computer and destroy any copies. Any distribution or 
copying without our prior permission is prohibited.

Internet communications are not always secure and therefore Powergen Retail Limited 
does not accept legal responsibility for this message. The recipient is responsible 
for verifying its authenticity before acting on the contents. Any views or opinions 
presented are solely those of the author and do not necessarily represent those of 
Powergen Retail Limited. 

Registered addresses:

Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG.
Registered in England and Wales No: 3407430

Telephone +44 (0) 2476 42 4000
Fax +44 (0) 2476 42 5432

Re: TSM on AS/400

[Del Hoobler]

Rachel,


Did you try running this manully from a "green screen"?
What output are you seeing when you run "domdsmc"?
What do you mean by queuing? Is your backup hanging or is it failing?

If you can't get this working, you may want to place
a call with IBM support.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/29/2004
11:38:23 AM:

> Del,
>
> I looked at the DOMDSM.LOG but there was no information in it that would
> explain why a backup was queuing.
> The tsm server was operating with no reported errors so I was looking
> for some type of output that would explain why it happened...
>
> What do you mean by redirected command output? Do you mean when the
> backup is started to send output to a file?
>
> Thanks for your help,
> Rachel
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Del Hoobler
> Sent: 29 October 2004 16:17
> To: [EMAIL PROTECTED]
> Subject: Re: TSM on AS/400
>
>
> Rachel,
>
> By default, the log file name is "DOMDSM.LOG".
> This log file contains operation parameters and summary statistics.
> It does not contain a list of each database processed.
> You can obtain that by looking at the redirected command output.
>
> Thanks,
>
> Del
>
> 
>
> "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/29/2004
> 10:40:26 AM:
>
> > Del,
> >
> > I am looking for the log file that reports the activity/errors of the
> > backup on the client.
> > It captures the same log as the dsmsched.log but on the OS/400.
> >
> > Thanks,
> > Rachel
> >

Is it possible to save an

[Sam Sheppard]

 Top of message 
>>--> 10-29-04  11:29  S.SHEPPARD (SHS)Is it possible to save an

No.  USS client only operates on USS filespaces.  You could copy an MVS
dataset to a USS file and then back it up.

Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
---`


 Top of message 
>>--> 10-29-04  06:59  ..NETMAIL (001) Is it possible to save an
Date: Fri, 29 Oct 2004 15:58:31 +0200
From: "Werner Nussbaumer" <[EMAIL PROTECTED]>
Subject: Is it possible to save an MVS dataset with the TSM Backup
To: [EMAIL PROTECTED]
_Top_of_Message_

Is it possible to start the TSM Client "dsmc" in Open Edition OMVS =
(UNIX) and in OMVS dsmc to backup an MVS dataset?
=20
Thanks for any help,
regards
Werner Nussbaumer

---`

Domino server crashes

[Gill, Geoffrey L.]

Has anyone seen a windows 2000 domino server system crashing, bluescreen,
during backups? I haven't personally been able to tell if the system crashes
when it is doing nothing but I'm told as long as the services are not
running it seems to be ok. As soon as they try and run backups, manual or
scheduled, it blue screens.



client version 5.1.6.9 and Domino agent version 5.1.5.0.

TSM server 5.1.6.3.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 854-0975

Unable to bring 3583 back online

[Mike Bantz]

We had a main board go out on our 3583, where the SCSI cable connects from
the TSM server and then on to the two drives.

When I boot everything up, the drives are unavailable and I'm not able to
update them - it says that the 3583 is unavailable. When I look at the 3583
in TSM, it gives me an error that the serial number doesn't match.

I've tried updating this with autodetect, still no go. I've tried updating
this with the serial gleaned from the 3583 itself, still no go. The admin
console will kick back that the library is updated with the newly discovered
serial number, yet I am still not able to update the drives to online
because they show the library unavailable.

What exactly am I missing here?

Mike Bantz
Systems Administrator
Research Systems, Inc
4990 Pearl East Circle
Boulder, CO 80301
(303) 413-3999 direct
(303) 786-9909 fax
http://www.researchsystems.com 

Re: Unable to bring 3583 back online

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Mike Bantz
>When I boot everything up, the drives are unavailable and I'm 
>not able to update them - it says that the 3583 is 
>unavailable. When I look at the 3583 in TSM, it gives me an 
>error that the serial number doesn't match.
>
>I've tried updating this with autodetect, still no go. I've 
>tried updating this with the serial gleaned from the 3583 
>itself, still no go. The admin console will kick back that the 
>library is updated with the newly discovered serial number, 
>yet I am still not able to update the drives to online because 
>they show the library unavailable.

Details, you need to supply details.

If the TSM server is Windows-based, look at the device manager to see if
the library and the tape drives are visible and online. If it's
AIX-based, see if the tape drives and library are available (as opposed
to defined).

Failing that, you need to contact Tivoli support and open a ticket.

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
Office 262.521.5627