Re: Backing up Windows2003 Server with Client 5.2

2003-09-12 Thread Andrew Raibeck
Bill, your read of the client manual is correct. For Windows 2003, TSM 5.2
uses the Microsoft VSS (Volume Shadowcopy Service) to back up system state
and system services, versus the "legacy" methods used in TSM 5.1 and
earlier to back up what we called the "system object".

In addition, the Windows 2003 system state/service backups use a different
transaction protocol that doesn't pin the server recovery log for
extensive periods of time, as might the "system object" backup method.
This support required changes on the server side as well, and thus the
requirement for a 5.2 server.

You can use the 5.1.6.x client and system object backup method for backing
up the Windows 2003 to a TSM 5.1 server.

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.




Bill Boyer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/11/2003 12:00
Please respond to "ADSM: Dist Stor Manager"

To: [EMAIL PROTECTED]
cc:
Subject:Backing up Windows2003 Server with Client 5.2


I ran a full backup of a Win2003 server last night with the 5.2.0.2
client.
The event shows as failed, but the backup actually backed up nothing.
Here's
the stats:

09/10/2003 22:11:48 --- SCHEDULEREC STATUS BEGIN
09/10/2003 22:11:48 Total number of objects inspected:   44,113
09/10/2003 22:11:48 Total number of objects backed up:0
09/10/2003 22:11:48 Total number of objects updated:  0
09/10/2003 22:11:48 Total number of objects rebound:  0
09/10/2003 22:11:48 Total number of objects deleted:  0
09/10/2003 22:11:48 Total number of objects expired:  0
09/10/2003 22:11:48 Total number of objects failed:  44,113
09/10/2003 22:11:48 Total number of bytes transferred: 2.44 GB
09/10/2003 22:11:48 Data transfer time:  139.91 sec
09/10/2003 22:11:48 Network data transfer rate:18,331.90 KB/sec
09/10/2003 22:11:48 Aggregate data transfer rate:  4,511.33 KB/sec
09/10/2003 22:11:48 Objects compressed by:0%
09/10/2003 22:11:48 Elapsed processing time:   00:09:28
09/10/2003 22:11:48 --- SCHEDULEREC STATUS END
09/10/2003 22:11:48 --- SCHEDULEREC OBJECT END BD72200 09/10/2003 22:00:00
09/10/2003 22:11:48 Scheduled event 'BD72200' completed successfully.

In the server log (this is a TSM 5.1.7.1 server on AIX 4.3.3) I see
numerous:

09/10/2003 22:06:49  ANRD smnode.c(19134): ThreadId<20> Session
38868 for
  node NWTRACKIT : Invalid filespace for backup
group
  member: 3.
09/10/2003 22:06:49  ANR0444W Protocol error on session 38868 for node
  NWTRACKIT (WinNT) - out-of-sequence verb (type
Data)
  received.
09/10/2003 22:06:50  ANRD smnode.c(19134): ThreadId<31> Session
38883 for
  node NWTRACKIT : Invalid filespace for backup
group
  member: 3.
09/10/2003 22:06:50  ANR0444W Protocol error on session 38883 for node
  NWTRACKIT (WinNT) - out-of-sequence verb (type
Data)
  received.
09/10/2003 22:06:50  ANR0484W Session 38868 for node NWTRACKIT (WinNT)
  terminated - protocol violation detected.
09/10/2003 22:06:50  ANR0484W Session 38883 for node NWTRACKIT (WinNT)
  terminated - protocol violation detected.


Looking at the 5.2 client manual, it says that to backup the "system
Services" I need a TSM 5.2 server?!??!!? Does that mean I can't back up a
Win2003 server unless I'm at 5.2 all the way around? This is an AIX4.3
server so I can't upgrade it to TSM 5.2.

Bill Boyer
"Some days you are the bug, some days you are the windshield." - ??


Re: 4.2.2.12 to 5.1.0.0 upgrade and PATHS

2003-09-12 Thread Farren Minns
We just have a simple set-up of one TSM server connected via TCP to a 3494
lib with two drives in it. As far as I know, we don't use library managers
and clients (I'm guessing not as this is the first I've heard of them) so
I'm thinking we should be OK.

Thanks to all for the advice

Farren
|+---+|
||   P Baines||
||   <[EMAIL PROTECTED]>   ||
||   Sent by: "ADSM: Dist Stor   |   To:       [EMAIL PROTECTED]  |
||   Manager"|           cc:  |
||   <[EMAIL PROTECTED]>  |           Subject:        Re: 4.2.2.12 |
||   |   to 5.1.0.0 upgrade and PATHS |
||   09/12/2003 07:46 AM ||
||   Please respond to "ADSM:||
||   Dist Stor Manager"  ||
||   ||
|+---+|








If you are upgrading library manager and clients you should be careful. The
upgrade process will define paths on all your servers, and it all looks and
works ok. Until you want to define a new drive (or delete/redefine a drive)
on a library client. Then you will discover that the 4.2 Admin Guide is
wrong (5.1 is correct). All drive and path definitions now need to be done
on the library manager. Only a library definition is done on the clients.
If
you don't use library managers and clients the upgrade process should
define
your paths and you should be OK. (My experience on AIX)

Paul.

-Original Message-
From: David Nicholson [mailto:[EMAIL PROTECTED]
Sent: 11 September 2003 19:17
To: [EMAIL PROTECTED]
Subject: Re: 4.2.2.12 to 5.1.0.0 upgrade and PATHS


My recollection is that we simply had to define the paths. However, SOP
says be prepared for anything. I also recall that we were told to remove
the DRIVE def's from all TSM library clients. The DRIVE's only need to be
defined to the library manager/owner in a library sharing environment now.
The devices still need to be defined to the OS on the library client, but
TSM does not require the DRIVE to be defined to library clients. I am not
sure that it is required to delete the DRIVE def's from clients, but was
recommended.

Dave Nicholson
Whirlpool Corporation





Farren Minns <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/11/2003 11:34 AM
Please respond to "ADSM: Dist Stor Manager"


To:     [EMAIL PROTECTED]
cc:
Subject:        Re: 4.2.2.12 to 5.1.0.0 upgrade and PATHS


I'm assuming that the Library and Device definitions will still be in
place, so then it'll just be the paths that need defining. Or do I need to
define new drives and lib too ?

Farren
|++---|
||   Lawrence Clark               | |
||   <[EMAIL PROTECTED]| |
||   .US>                         |   To:       [EMAIL PROTECTED] |
||   Sent by: "ADSM: Dist Stor    |           cc: |
||   Manager"                     |           Subject:        Re:
4.2.2.12|
||   <[EMAIL PROTECTED]>       |   to 5.1.0.0 upgrade and PATHS |
||                                | |
||   09/11/2003 04:07 PM          | |
||   Please respond to "ADSM: Dist| |
||   Stor Manager"                | |
||                                | |
|++---|







On the other hand, we upgraded from 4.2 to 5.1, have two 3494 libraries,
and did not have to manually define the paths..

>>> [EMAIL PROTECTED] 09/11/03 10:22AM >>>
We made the same upgrade 4.2 to 5.1 on our AIX server. We also have
3494
library. We deffinetly had to manually define the paths after the
upgrade.


Dave Nicholson
Whirlpool Corporation





Farren Minns <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/11/2003 07:53 AM
Please respond to "ADSM: Dist Stor Manager"


To:     [EMAIL PROTECTED]
cc:
Subject:        4.2.2.12 to 5.1.0.0 upgrade and PATHS


Hi TSMers

Ok, my questions about the 4.2 to 5.1 upgrade are prolly getting
boring,
but I always like to make sure I've asked every silly question I can so
as
not to get caught out.

So, next week I'm going from 4.2.2.12 to 5.1.6.2 on a Solaris 2.7
node.

I understand that PATHS are a new feature (or complication) of 5.1 but
want
to know if, after upgrade I HAVE to define these. I was speaking to an
IBM
rep the other day and he said yes, but I have heard others say they
didn't
have to do it (sorry to keep hastling you Gary). Our setup is one tcp
attached 3494 library with two scsi 3590 tape drives. I'm surprised
that
the upgrade would not see these devices already set up and create the
paths
accordingly.

Anyone got a defint

Re: How have you got your fiber-attached LTO drives connected to your TSM server?

2003-09-12 Thread Zlatko Krastev
It highly depends on what you are trying to achieve - cost, performance,
redundancy or mixture of them.
1. Cost - two hubs and single-attached drives split between them is the
cheapest (and worst in terms of performance/redundancy) solution.
2. Performance - do it all switched! Consider carefully not only
host-to-switch and switch-to-tape throughput but also potential
switch-to-switch bottlenecks (possibly non-TSM traffic). Special attention
should be paid on paths order/usage if redundant paths are available.
3. Redundancy - put a *pair* of switches and connect each drive to both!
You said plans are for upgrade to LTO-2. IBM Ultrium2 drives have two
ports and new Atape versions support SAN path failover.

Some of the comments were that you should have no more than 2 drives per
HBA. If you indeed achieve 5:1 compression this might mean even 2 will not
work at the maximum performance. OTOH if you have (or plan) SAN clients to
utilize extra drives the equation might be different - 2 HBAs x 2 drives +
2 drives for StA = 6. And then you should plan carefully not only TSM
Server-SAN-library route but also TSM StA-SAN-library one.

Zlatko Krastev
IT Consultant






Tom Kauffman <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10.09.2003 19:39
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:How have you got your fiber-attached LTO drives connected to 
your TSM
server?


I will be going fiber-attach next year and will have two adapters in my
TSM
server.

Do I put a fiber switch in the tape library (3584), tie all the drives to
it, and run two fibers back to the TSM server?

Do I run seperate fibers for all the drives back to my existing switches?

Do I put a pair of fiber hubs in somewhere, and hook half the drives to
each
hub?

Ah, yes, it's that wonderful time of year when the leaves start to turn --
and the next year's budget projections are due :-)

Tom Kauffman
NIBCO, Inc
CONFIDENTIALITY NOTICE:  This e-mail and any attachments are for the
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return e-mail and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.


Backup NAS data using TSM

2003-09-12 Thread Nicolas Savva
Hi to all,

What alternatives does TSM provide for backing up NAS data?
Do i have to register NAS as a node to TSM Srever?

Thanks in advance
Nick

Privileged/Confidential information may be contained in this message and
may be subject to legal privilege. Access to this e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient (or responsible for delivery of the message to such person),  you
may not use, copy, distribute or deliver to anyone this message (or any
part of its contents) or take any action in reliance on it. In such case,
you should destroy this message, and notify us immediately.

If you have received this email in error, please notify us immediately by
e-mail or telephone and delete the e-mail from any computer. If you or your
employer does not consent to internet e-mail messages of this kind, please
notify us immediately.

All reasonable precautions have been taken to ensure no viruses are present
in this e-mail. As we cannot accept responsibility for any loss or damage
arising from the use of this e-mail or attachments we recommend that you
subject these to your virus checking procedures prior to use.

The views, opinions, conclusions and other information expressed in this
electronic mail are not given or endorsed by Laiki Group unless otherwise
indicated by an authorised representative independent of this message.



W2K, ACL's and Active Directory questions

2003-09-12 Thread Alex den Hartog
I hope someone can shed some light on this:

We are trying to figure out if it's possible to do a restore of -only- the
file permissions of a file or directory on a Windows 2000 server. The actual
file still resides on the server, this file doen not need to be replaced nor
restored, but ONLY the permissions and security-info of that file or
directory need to be restored. Is this possible?
My second question is about Active directory. To what extent can you restore
different objects from within the AD structure? OR is it only possible to do
an entire file restore from the AD server? Do I need to set it up
specifically for the AD-server?
Thank you in advance for your help.

_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
http://join.msn.com/?page=features/virus


Re: DSMFMT takes forever ( 15 hours). 100 gb

2003-09-12 Thread Paul Ripke
On Friday, Sep 12, 2003, at 08:58 Australia/Sydney, Adrian Hicks wrote:

We have never had a prob. on JFS2, it whizzes along well. Are you
formatting a single 100Gig SP ?? Personally I'd break it up into at
least 4 volumes ??
Problems seen with just `dd' and large files, and also with Oracle.
Appears to be vmtune minperm/maxperm/maxclient/strict_maxperm AIX
filecache tuning issue. I'll investigate it one of these centuries
when I have some spare time and a test/victim system.
So not strictly a TSM topic, but of interest nonetheless. Anyone
interested, we can take this off-list.
Cheers,
--
Paul Ripke
Unix/OpenVMS/TSM/DBA
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams


Re: TSM 4.2 and Exchange TDP 1.1.1

2003-09-12 Thread Del Hoobler
Gerald,

Version 1.1.1 used a different command-line syntax.
You should just be able to issue the "ADSMQUERYDB" command
and redirect the output to a file.
For example:

   EXCDSMC /ADSMQUERYDB:* /ADSMPWD:password   > OUTPUT.TXT

Thanks,

Del



>  I was just looking at my Exchange TDP output and have it showing all
> exchange backups ever created. It shows directory backups and
information
> store backups (full and incremental. exchange 5.5). Is there someway I
can
> query our output this list of backups to a text file? On the TDP side I
> don't see anything in the GUI. I'm guessing I need to do something with
the
> TDP cmdline to query a list of this (with dates) so I can hand this to
> someone and get an idea of what to restore. Time to read some notes but
if
> someone knows off the top of their head how to do this I'd appreciate
the
> info.


SV: Backup NAS data using TSM

2003-09-12 Thread Christian Svensson
Hi Nick!
It?s diffrent between diffrent NAS units.
If you got a NAS unit from SnapAppliance you can install the BA Client
on the NAs unit. And run as a normal server.
But how you do with a Maxtor och IBM NAS do i don?t know.
So please leve more information about which NAS unit you want answer
for.

/Christian

-Ursprungligt meddelande-
Fran: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Nicolas
Savva
Skickat: den 12 september 2003 09:35
Till: [EMAIL PROTECTED]
Amne: Backup NAS data using TSM


Hi to all,

What alternatives does TSM provide for backing up NAS data?
Do i have to register NAS as a node to TSM Srever?

Thanks in advance
Nick


Privileged/Confidential information may be contained in this message and
may be subject to legal privilege. Access to this e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient (or responsible for delivery of the message to such person),
you
may not use, copy, distribute or deliver to anyone this message (or any
part of its contents) or take any action in reliance on it. In such
case,
you should destroy this message, and notify us immediately.

If you have received this email in error, please notify us immediately
by
e-mail or telephone and delete the e-mail from any computer. If you or
your
employer does not consent to internet e-mail messages of this kind,
please
notify us immediately.

All reasonable precautions have been taken to ensure no viruses are
present
in this e-mail. As we cannot accept responsibility for any loss or
damage
arising from the use of this e-mail or attachments we recommend that you
subject these to your virus checking procedures prior to use.

The views, opinions, conclusions and other information expressed in this
electronic mail are not given or endorsed by Laiki Group unless
otherwise
indicated by an authorised representative independent of this message.




DB increasing rapidly

2003-09-12 Thread Joni Moyer
Hello everyone!

I have a quick question about the database percent utilized.   Within the
past two days we have changed all disk storage pool volumes, DB volumes and
recovery log volumes from MOD-3's to MOD-9's therefore we have mainly
changed the whole configuration of disk for the TSM server.  During this
whole process the database has increased 10%.  It had been 11GB utilized at
85% and it is now 95%.  Could the addition/deletion of DB, log and storage
pool volumes cause this tremendous increase in the database?  How will the
database decrease?

The TSM server is on os/390 2.10 at level 5.1.6.2.

Thanks!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338


Re: DB increasing rapidly

2003-09-12 Thread Mahesh Tailor
Joni,

I had something like this happening and it turned out that my expiration
processes were ending too soon [because of too short a duration].  After
I ran the expiration without a duration a couple of times, all was back
to normal.

Mahesh


On Fri, 2003-09-12 at 08:08, Joni Moyer wrote:
> Hello everyone!
>
> I have a quick question about the database percent utilized.   Within the
> past two days we have changed all disk storage pool volumes, DB volumes and
> recovery log volumes from MOD-3's to MOD-9's therefore we have mainly
> changed the whole configuration of disk for the TSM server.  During this
> whole process the database has increased 10%.  It had been 11GB utilized at
> 85% and it is now 95%.  Could the addition/deletion of DB, log and storage
> pool volumes cause this tremendous increase in the database?  How will the
> database decrease?
>
> The TSM server is on os/390 2.10 at level 5.1.6.2.
>
> Thanks!
>
> Joni Moyer
> Systems Programmer
> [EMAIL PROTECTED]
> (717)975-8338


Re: Non-IBM LTO tapes in a 3584

2003-09-12 Thread Tom Kauffman
For what it's worth, we brought in 380 tapes with our library two years ago.
They were all Fuji tapes. We haven't had any problems with them that
couldn't be traced back to drive or drive firmware issues.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: Mark Ferraretto [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 10, 2003 11:31 PM
To: [EMAIL PROTECTED]
Subject: Non-IBM LTO tapes in a 3584


All,

We're looking at purchasing extra LTO-1 tapes to go in our 3584.  To date,
we've been running IBM tapes but we've gotten cheaper prices on HP and
Imation tapes.  Both HP and Imation are priced about 30% less than the IBM
tapes.

But I'm wondering if there are any quality issues with either of these
brands.  Also, I'm wondering if running non-IBM tapes in a 3584 might raise
any issues.

Can anyone help?

Thanks

Mark


--
Mark Ferraretto
Unix Systems Administrator
Deutsche Bank Hong Kong
w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971
[EMAIL PROTECTED]


--

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
CONFIDENTIALITY NOTICE:  This e-mail and any attachments are for the exclusive and 
confidential use of the intended recipient.  If you are not the intended recipient, 
please do not read, distribute or take action in reliance upon this message. If you 
have received this in error, please notify us immediately by return e-mail and 
promptly delete this message and its attachments from your computer system. We do not 
waive attorney-client or work product privilege by the transmission of this message.


deleting database BACKUPINCR volumes

2003-09-12 Thread Fought,Tom
Okay. I am trying to determine if I can script
the deletion of database BACKUPINCR volumes.
Any pointers would be appreciated.
Thanks
Tom


Re: DB2 high speed SP switch backups dead slow.

2003-09-12 Thread Miles Purdy
Some things to try:

1. verify that the MTU is consistent for all nodes, from your cws:
[EMAIL PROTECTED]:/>dsh  "netstat -i | grep css0"
unxa_sp: css0  65504 link#4 3496790 0  4212524 0 0
unxa_sp: css0  65504 192.168.17  unxa_sw3496790 0  4212524 0 0
unxb_sp: css0  65504 link#4 3500733 0  3392237 0 0
unxb_sp: css0  65504 192.168.17  unxb_sw3500733 0  3392237 0 0
unxc_sp: css0  65504 link#3 3435131 0  3620093 0 0
unxc_sp: css0  65504 192.168.17  unxc_sw3435131 0  3620093 0 0
unxm_sp: css0  65504 link#5 3486660 0  5827317 0 0
unxm_sp: css0  65504 192.168.17  unxm_sw3486660 0  5827317 0 0
unxp_sp: css0  65504 link#521731474 0 30705999 0 0
unxp_sp: css0  65504 192.168.17  unxp_sw   21731474 0 30705999 0 0
unxr_sp: css0  65504 link#682760978 0 79211973 0 0
unxr_sp: css0  65504 192.168.17  unxr_sw   82760978 0 79211973 0 0

Yours should be: 65520.

2. my dsmserv.opt
TCPWINDOWSIZE 2048
BUFPoolsize 262144

3. client dsm.sys settings:
unxr:/usr/tivoli/tsm/client/ba/bin>cat dsm.sys
Servername  unxr
   NODENAME unxr
   TCPPort  1500
   SHMPort  1510
   TCPServeraddress 127.0.0.1
   tcpb 64
   tcpwindowsize2048
   tcpnodelay   Yes
   TXNbytelimit 2097152
   resourceutilization  10
   passwordaccess   generate
   LARGECOMMBUFFERS No

4. are you sure you want client compression?

5. And again, try and identify the bottleneck.

Miles


>>> "Muthyam  Reddy" <[EMAIL PROTECTED]> 11-Sep-03 10:13:50 AM >>>
** High Priority **

thanks a lot for quick responce.

we have
AIX:4.3.3.0
PSSP version:3.1.1.0
OS kernel:64bit in all SP nodes 
TSM Tapedrives:IBM 3590 Tape Drive and Medium Changer.

I have set css0 spoolsize,rpoolsize to 16777216 in both client and server.
TSM server type:S80, 7017
SP switch css0 type:SP Switch Communications Adapter (Type 6-F)
TSM software level:5.1.5.0 in both client and server.
all out nodes are hoocked to SHARK disk storage.those SSA drives.

dsm.sys parametrs at client.

tcpnodelay  yes
compression yes
LARGECOMMBUFFERS NO
TCPwindow 2048
TCPbuffsize   256 
TCPNodelayyes 
PASSWORDACCESS generate
   resourceutilization  8

thanks and regards
muthyam



>>> "Miles Purdy" <[EMAIL PROTECTED]> 09/10/03 03:47PM >>>
That seems terribly slow. 430 GB in 14 hours is only 8.7 MB/s aggregate throughput. 
Over four streams that's only 2 MB/s/stream. It has been my experience that the source 
hdisks are usually the bottleneck.

There are only two tunables for the switch adapter, rpoolsize and spoolsize.
These can be changed, for example:
chdev -l css0 -a spoolsize=14680064
chdev -l css0 -a rpoolsize=16777216

A couple of things that come to mind:
- are you mixing machines with 32 and 64 bit kernels on the same SP Switch?
- what version of AIX are you running? What version of PSSP? What tape drives do you 
have?
- what are your vmtune settings?
- where is the bottleneck?
   - is the switch performing well?
   - check the source disks
   - check the VMM




>>> [EMAIL PROTECTED] 10-Sep-03 2:18:05 PM >>>
** High Priority **

Hi TSMers,
I hope someone got experiance on same before .

This is problem about db2(7.1) backups on high speed switch to TSM .Present we are 
taking 430Gb of data to tsm which is taking 14 hrs to finish.recently I have changed 
couple of paramters on 'css' and 'no' to improve performance based on IBM docs.Still 
my backups takes same time.
no doubt I missed some parts on TSM/AIX/db2  to lubricate.
Please can any one dump some ideas to fix this this and how long its taking in ur 
environment same setup.
We are using four session on db2(7.1) and copying to tape pools directly.


please send ur back times with same environments.

please send me some tips to make my backups fast.

please write if wants information.

thanks and regards
muthyam








This electronic mail transmission contains information from Joy Mining Machinery
which is confidential, and is intended only for the use of the proper addressee.
If you are not the intended recipient, please notify us immediately at the return
address on this transmission, or by telephone at (724) 779-4500, and delete
this message and any attachments from your system.  Unauthorized use, copying,
disclosing, distributing, or taking any action in reliance on the contents of
this transmission is strictly prohibited and may be unlawful.

<>


Re: DSMFMT takes forever ( 15 hours). 100 gb

2003-09-12 Thread Ochs, Duane
Tried it as 4-25 GB. With the TSM software down, it takes about the same
amount of time 1 gb per minute.

-Original Message-
From: Adrian Hicks [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 5:59 PM
To: [EMAIL PROTECTED]
Subject: Re: DSMFMT takes forever ( 15 hours). 100 gb


We have never had a prob. on JFS2, it whizzes along well. Are you
formatting a single 100Gig SP ?? Personally I'd break it up into at
least 4 volumes ??

Adrian

-Original Message-
From: Paul Ripke [mailto:[EMAIL PROTECTED]
Sent: Friday, 12 September 2003 8:19 AM
To: [EMAIL PROTECTED]
Subject: Re: DSMFMT takes forever ( 15 hours). 100 gb


On Friday, Sep 12, 2003, at 02:52 Australia/Sydney, Ochs, Duane wrote:

I've seen very bad performance from JFS2 on AIX 5.1 under certain
circumstances - as soon as I understand more on the how+why, I'll be
raising a ticket with IBM.

> I guess I can sum it up to not enough system to perform the task.
> Stopped
> the TSM software and the format completes a little more than 1 GB per
> minute.
>
> Duane
>
>>  -Original Message-
>> From: Ochs, Duane
>> Sent: Wednesday, September 03, 2003 11:22 AM
>> To:   [EMAIL PROTECTED] MARIST. EDU (E-mail)
>> Subject:  DSMFMT takes forever ( 15 hours). 100 gb
>>
>> Does anyone know of or had problems with formatting additional space
>> for
>> diskpools ?
>>
>> TSM server : AIX 5.1 ML3 64-bit enabled. 2GB memory 2 cpu H80
>>
>> Disk type : 6 member raid set about 700 GB
>>
>> JFS2
>>
>> Trying to format 100gb diskpool. Each time I have tried it brings the
>> TSM
>> server to almost a stand still. TSM is up on the box but nothing is
>> running during 8 hours of the format. Should be more than enough time
>> to
>> format 100gb of space.
>>
>> Any ideas ?
>>
>> Duane Ochs
>> Enterprise Computing
>>
>> Quad/Graphics
>>
>> Sussex, Wisconsin
>> 414-566-2375 phone
>> 414-917-0736 beeper
>> [EMAIL PROTECTED]
>> www.QG.com
>>
>>
>
>
--
Paul Ripke
Unix/OpenVMS/TSM/DBA
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams


This message and any attachment is confidential and may be privileged or
otherwise protected from disclosure.  If you have received it by mistake
please let us know by reply and then delete it from your system; you should
not copy the message or disclose its contents to anyone.


==


Re: Non-IBM LTO tapes in a 3584

2003-09-12 Thread Shawn Price
Mark,
 For what it's worth, my boss cheaped out and got some non IBM tapes for our
3584, and I've had nothing but problems with them. Mostly Imation and a few
Emtecs. We are running the first generation LTO 1 drives, so there might be
an issue with those as well. I have now gone in and just started pulling the
tapes that have gone read-only more than twice and replaced them with IBMs.

Shawn

> From: Mark Ferraretto <[EMAIL PROTECTED]>
> Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> Date: Thu, 11 Sep 2003 12:30:57 +0800
> To: [EMAIL PROTECTED]
> Subject: Non-IBM LTO tapes in a 3584
>
> All,
>
> We're looking at purchasing extra LTO-1 tapes to go in our 3584.  To date,
> we've been running IBM tapes but we've gotten cheaper prices on HP and Imation
> tapes.  Both HP and Imation are priced about 30% less than the IBM tapes.
>
> But I'm wondering if there are any quality issues with either of these brands.
> Also, I'm wondering if running non-IBM tapes in a 3584 might raise any issues.
>
> Can anyone help?
>
> Thanks
>
> Mark
>
>
> --
> Mark Ferraretto
> Unix Systems Administrator
> Deutsche Bank Hong Kong
> w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971
> [EMAIL PROTECTED]
>
>
> --
>
> This e-mail may contain confidential and/or privileged information. If you are
> not the intended recipient (or have received this e-mail in error) please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is strictly
> forbidden.
>


Re: Non-IBM LTO tapes in a 3584

2003-09-12 Thread Dan Foster
Hot Diggety! Shawn Price was rumored to have written:
>  For what it's worth, my boss cheaped out and got some non IBM tapes for
>  our 3584, and I've had nothing but problems with them. Mostly Imation
>  and a few Emtecs. We are running the first generation LTO 1 drives, so
>  there might be an issue with those as well. I have now gone in and just
>  started pulling the tapes that have gone read-only more than twice and
>  replaced them with IBMs.

Make sure your library and drives are at the latest firmware revision
levels -- this is especially important since more recent firmware revs
fixes bugs that causes problems with non-IBM tapes from what I hear.

Latest 3584 library firmware you can get from IBM's web/ftp site: 3300
if no D42 drives in library; else, 3060.

To check firmware rev for library w/AIX: # lscfg -vl smc0 | grep FW

The library firmware rev # also appears on the main LCD panel screen.

Latest 3584 drive firmware you can get from IBM's web/ftp site: 36U3 for
LTO-1 drives and 38D0 for LTO-2 drives.

To check firmware rev for drive w/AIX: # lscfg -vl rmt0 | grep FW
(...and for each drive... rmt1, rmt2, etc.)

-Dan


Reclamation preempting reclamation?

2003-09-12 Thread Chris Murphy
Hello all,

Enviro: TSM Server 5.1.7.0 on Win2k SP4 (both servers)
SERVER1 source server, SERVER2 is the target server for the virtual volumes

Yesterday morning, during expiration, several reclamation processes were
kicked off for some onsite FILE volumes and several offsite virtual volumes
as well as a tape volume.  It appears from the log, that during the
reclamation of one of the offsite virtual volumes on the target server, a
process preempted the reclamation.  However, no processes were running, and
no restores were running on the target machine.  For some, reason, it
appears the target server cancels the session for the first reclamation with
the entry:

"ANR0494I Volume E:\TSMDATA\SERVER1\VV_BOISE_BKP1.DBB in use. Session 3610
for node SERVER1 (Windows) being preempted by higher priority operation."

Now, this volume was still mounted by process 292, as the mount retention
had not expired but the process had just ended.  As can be seen in the
ACTLOGS below, the second reclamation, process 294, attempts to reclaim its
volume, which happens to be located within the same FILE volume on the
target server.  It appears this process "preempts" the target server as the
volume was still mounted by the previous process, 292, which had just
completed.  So, my issues are this:

1.) Why would process 294 "preempt" process 292?  You can use the session
numbers (3610 for 292 and 3611 for 294) to see that it is really process 292
that is canceled, but it was *already* finished according to the logs on
the source server.

2.) As can then be seen further down, due to the cancellation, the source
server, SERVER1, sees this as a write error to the volume on the target.
Shouldn't this be handled more gracefully?  For instance, when reclamation
of a tape volume is preempted and canceled, the destination tape does not
experience a "write error" and get placed in READ ONLY mode.  So it appears
that when using virtual volumes, the process is not as graceful, and the
cancellation of the process by the target is not appropriately conveyed to
the source so that it may handle the issue gracefully.

SERVER 1 ACTLOG:

09/11/2003 08:10:08  ANR0984I Process 292 for SPACE RECLAMATION started in
the BACKGROUND at 08:10:08.
09/11/2003 08:10:08  ANR1040I Space reclamation started for volume
SERVER2.BFS.050166820, storage pool DIRECTORY_OFFSITE1 (process number 292).
09/11/2003 08:10:08  ANR8340I FILE volume H:\TSMDATA\SERVER1\1018.BFS
mounted.
09/11/2003 08:10:08  ANR8340I FILE volume H:\TSMDATA\SERVER1\1000.BFS
mounted.
09/11/2003 08:10:11  ANR1044I Removable volume
H:\TSMDATA\SERVER1\1000.BFS is required for space reclamation.
09/11/2003 08:10:13  ANR8340I SERVER volume SERVER2.BFS.063289412 mounted.
09/11/2003 08:10:13  ANR1340I Scratch volume SERVER2.BFS.063289412 is now
defined in storage pool DIRECTORY_OFFSITE1.
09/11/2003 08:10:17  ANR8340I FILE volume H:\TSMDATA\SERVER1\1030.BFS
mounted.
09/11/2003 08:11:41  ANR8341I End-of-volume reached for FILE volume
H:\TSMDATA\SERVER1\1018.BFS.
09/11/2003 08:11:41  ANR8340I FILE volume H:\TSMDATA\SERVER1\1033.BFS
mounted.
09/11/2003 08:12:32  ANR8340I FILE volume H:\TSMDATA\SERVER1\1030.BFS
mounted.
09/11/2003 08:13:10  ANR1041I Space reclamation ended for volume
H:\TSMDATA\SERVER1\1000.BFS.
09/11/2003 08:13:10  ANR8340I FILE volume H:\TSMDATA\SERVER1\1000.BFS
mounted.
09/11/2003 08:13:10  ANR1044I Removable volume
H:\TSMDATA\SERVER1\0FFF.BFS is required for space reclamation.
09/11/2003 08:13:11  ANR8340I FILE volume H:\TSMDATA\SERVER1\0FFF.BFS
mounted.
09/11/2003 08:13:11  ANR0986I Process 292 for SPACE RECLAMATION running in
the BACKGROUND processed 4 items for a total of 4,164 bytes with a
completion state of SUCCESS at 08:13:11.
09/11/2003 08:13:11  ANR1041I Space reclamation ended for volume
SERVER2.BFS.050166820.
09/11/2003 08:13:11  ANR0984I Process 294 for SPACE RECLAMATION started in
the BACKGROUND at 08:13:11.
09/11/2003 08:13:11  ANR1040I Space reclamation started for volume
SERVER2.BFS.050166820, storage pool DIRECTORY_OFFSITE1 (process number 294).
09/11/2003 08:13:11  ANR1044I Removable volume SERVER2.BFS.050166820 is
required for space reclamation.
09/11/2003 08:13:11  ANR8340I SERVER volume SERVER2.BFS.050166820 mounted.
09/11/2003 08:13:12  ANR4383E Session failure, target server SERVER has
aborted current transaction; reason: Transaction failed.
09/11/2003 08:13:12  ANR1411W Access mode for volume SERVER2.BFS.063289412
now set to "read-only" due to write error.
09/11/2003 08:13:12  ANR1181E astxn.c514: Data storage transaction
0:485863386 was aborted.
09/11/2003 08:13:13  ANR2183W afmove.c4235: Transaction 0:485863386 was
aborted.
09/11/2003 08:13:13  ANR0985I Process 294 for SPACE RECLAMATION running in
the BACKGROUND completed with completion state FAILURE at 08:13:13.
09/11/2003 08:13:13  ANR1093W Space reclamation terminated for volume
SERVER2.BFS.050166820 - transaction aborted.
09/11/2003 08:13:13  ANR1042I Space reclama

Re: Non-IBM LTO tapes in a 3584

2003-09-12 Thread Stephen Comiskey
Hi,

As well as having the latest firmware, IBM have recently issued a small
plastic clip for LTO1 drives.  We were having problems with tapes ejecting
(both IBM and non-IBM) and this helped resolve it along with the firmware
upgrade.

cheers
Stephen
Dublin, Ireland


|-+--->
| |   Dan Foster  |
| |   <[EMAIL PROTECTED]>  |
| |   Sent by: "ADSM: |
| |   Dist Stor   |
| |   Manager"|
| |   <[EMAIL PROTECTED]|
| |   T.EDU>  |
| |   |
| |   |
| |   12/09/03 15:59  |
| |   Please respond  |
| |   to "ADSM: Dist  |
| |   Stor Manager"   |
| |   |
|-+--->
  
>---|
  |
   |
  |To:  [EMAIL PROTECTED]  
|
  |cc: 
   |
  |Subject: Re: Non-IBM LTO tapes in a 3584
   |
  
>---|




THIS MESSAGE ORIGINATED ON THE INTERNET - Please read the detailed
disclaimer below.
---


Hot Diggety! Shawn Price was rumored to have written:
>  For what it's worth, my boss cheaped out and got some non IBM tapes for
>  our 3584, and I've had nothing but problems with them. Mostly Imation
>  and a few Emtecs. We are running the first generation LTO 1 drives, so
>  there might be an issue with those as well. I have now gone in and just
>  started pulling the tapes that have gone read-only more than twice and
>  replaced them with IBMs.

Make sure your library and drives are at the latest firmware revision
levels -- this is especially important since more recent firmware revs
fixes bugs that causes problems with non-IBM tapes from what I hear.

Latest 3584 library firmware you can get from IBM's web/ftp site: 3300
if no D42 drives in library; else, 3060.

To check firmware rev for library w/AIX: # lscfg -vl smc0 | grep FW

The library firmware rev # also appears on the main LCD panel screen.

Latest 3584 drive firmware you can get from IBM's web/ftp site: 36U3 for
LTO-1 drives and 38D0 for LTO-2 drives.

To check firmware rev for drive w/AIX: # lscfg -vl rmt0 | grep FW
(...and for each drive... rmt1, rmt2, etc.)

-Dan


---
The following message has been automatically added by the mail gateway to
comply with a Royal & SunAlliance IT Security requirement.

As this email arrived via the Internet you should be cautious about its
origin and content. Replies which contain sensitive information or
legal/contractual obligations are particularly vulnerable. In these cases
you should not reply unless you are authorised to do so, and adequate
encryption is employed.

If you have any questions, please speak to your local desktop support team
or IT security contact.
---






__

Notice of Confidentiality

This transmission contains information that may be confidential and that may also be 
privileged. Unless you are the intended recipient of the message (or authorised to 
receive it for the intended recipient) you may not copy, forward, or otherwise use it, 
or disclose it or its contents to anyone else. If you have received this transmission 
in error please notify us immediately and delete it from your system.

Email: [EMAIL PROTECTED]


Re: Backing up Windows2003 Server with Client 5.2

2003-09-12 Thread Bill Boyer
Just to make sureif I use the 5.1.6.x client configured just like I do
for the WIndows2000 servers, I'll have a complete backup of the Windows2003
server? I realize it may not be taking advantage of the "features" of
Windows2003 and the TSM 5.2 level, but I just need to make sure these
servers are getting FULLY backed up.

Bill Boyer
DSS, Inc.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Andrew Raibeck
Sent: Friday, September 12, 2003 3:20 AM
To: [EMAIL PROTECTED]
Subject: Re: Backing up Windows2003 Server with Client 5.2


Bill, your read of the client manual is correct. For Windows 2003, TSM 5.2
uses the Microsoft VSS (Volume Shadowcopy Service) to back up system state
and system services, versus the "legacy" methods used in TSM 5.1 and
earlier to back up what we called the "system object".

In addition, the Windows 2003 system state/service backups use a different
transaction protocol that doesn't pin the server recovery log for
extensive periods of time, as might the "system object" backup method.
This support required changes on the server side as well, and thus the
requirement for a 5.2 server.

You can use the 5.1.6.x client and system object backup method for backing
up the Windows 2003 to a TSM 5.1 server.

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.




Bill Boyer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/11/2003 12:00
Please respond to "ADSM: Dist Stor Manager"

To: [EMAIL PROTECTED]
cc:
Subject:Backing up Windows2003 Server with Client 5.2


I ran a full backup of a Win2003 server last night with the 5.2.0.2
client.
The event shows as failed, but the backup actually backed up nothing.
Here's
the stats:

09/10/2003 22:11:48 --- SCHEDULEREC STATUS BEGIN
09/10/2003 22:11:48 Total number of objects inspected:   44,113
09/10/2003 22:11:48 Total number of objects backed up:0
09/10/2003 22:11:48 Total number of objects updated:  0
09/10/2003 22:11:48 Total number of objects rebound:  0
09/10/2003 22:11:48 Total number of objects deleted:  0
09/10/2003 22:11:48 Total number of objects expired:  0
09/10/2003 22:11:48 Total number of objects failed:  44,113
09/10/2003 22:11:48 Total number of bytes transferred: 2.44 GB
09/10/2003 22:11:48 Data transfer time:  139.91 sec
09/10/2003 22:11:48 Network data transfer rate:18,331.90 KB/sec
09/10/2003 22:11:48 Aggregate data transfer rate:  4,511.33 KB/sec
09/10/2003 22:11:48 Objects compressed by:0%
09/10/2003 22:11:48 Elapsed processing time:   00:09:28
09/10/2003 22:11:48 --- SCHEDULEREC STATUS END
09/10/2003 22:11:48 --- SCHEDULEREC OBJECT END BD72200 09/10/2003 22:00:00
09/10/2003 22:11:48 Scheduled event 'BD72200' completed successfully.

In the server log (this is a TSM 5.1.7.1 server on AIX 4.3.3) I see
numerous:

09/10/2003 22:06:49  ANRD smnode.c(19134): ThreadId<20> Session
38868 for
  node NWTRACKIT : Invalid filespace for backup
group
  member: 3.
09/10/2003 22:06:49  ANR0444W Protocol error on session 38868 for node
  NWTRACKIT (WinNT) - out-of-sequence verb (type
Data)
  received.
09/10/2003 22:06:50  ANRD smnode.c(19134): ThreadId<31> Session
38883 for
  node NWTRACKIT : Invalid filespace for backup
group
  member: 3.
09/10/2003 22:06:50  ANR0444W Protocol error on session 38883 for node
  NWTRACKIT (WinNT) - out-of-sequence verb (type
Data)
  received.
09/10/2003 22:06:50  ANR0484W Session 38868 for node NWTRACKIT (WinNT)
  terminated - protocol violation detected.
09/10/2003 22:06:50  ANR0484W Session 38883 for node NWTRACKIT (WinNT)
  terminated - protocol violation detected.


Looking at the 5.2 client manual, it says that to backup the "system
Services" I need a TSM 5.2 server?!??!!? Does that mean I can't back up a
Win2003 server unless I'm at 5.2 all the way around? This is an AIX4.3
server so I can't upgrade it to TSM 5.2.

Bill Boyer
"Some days you are the bug, some days you are the windshield." - ??


another problems with TSMv5.2 client install.

2003-09-12 Thread
Trying to install TSM client v5.2 on Sun v2.8, 32 bit architecture.  The install is 
laying down the 64 bit TIVsmCapi rather than the 32 bit TIVsmCapi.
Upon starting the client, via dsmc, the following error gets generated:

 libCrun.so.1: open failed:  No such file or directory

Has anyone seen this, and if so, what have you done to work around it other than 
installing TSMv4.xx


Re: Problem with backup scripts

2003-09-12 Thread Andrew Raibeck
You indicate that you are using a script to launch dsmc, and that you are
getting RC 8. You next ask why the scheduled backup is failed instead of
completed. So I am wondering: are you using the TSM scheduler to schedule
ACTION=COMMAND where the command is your script? If so, then take another
look at the table in the "Automating tasks" chapter that describes the
return codes. The last row, "other", describes how return codes for
COMMAND actions are handled.

In general, for ACTION=COMMAND, any nonzero return code will be treated as
failed. The reason for this is that unlike commands such as SELECTIVE,
INCREMENTAL, ARCHIVE, etc., TSM has know knowledge of the internal
workings of commands launched via ACTION=COMMAND schedules. In reporting a
return code for these commands, the only convention we can observe is that
return code 0 is generally accepted as success. Thus anything else
(nonzero return code) is treated as a failure. If *you* know that your
scheduled command can exit with a nonzero return code, then in your script
you can test the return code from the command. If it meets your criteria
for success, you can exit the script with return code 0 and the scheduled
event will be reported as Complete. Otherwise you can exit with a nonzero
return code.

In your case, your script happens to launch the TSM client. Since we
*know* that RC 8 means at least one warning message was issued, I would
not advise that you translate this to return code 0 in your script,
although that is your option if you wish (do so at your own risk).
Instead, the reason for the RC 8 should be investigated and corrected.

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.




Neilson Lui <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/11/2003 00:49
Please respond to "ADSM: Dist Stor Manager"

To: [EMAIL PROTECTED]
cc:
Subject:Re: Problem with backup scripts


Have already looked at the manual... But how come the status of my
scheduled backup is FAILED instead of COMPLETED as indicated on the manual

09/11/2003 03:30:00  09/11/2003 03:30:05  OPICSFS_DAIL- OPXFS_AS
Failed
   Y_BACKUP



"Hooft, Jeroen"
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]
RIGIN.COM> cc:
Sent by: "ADSM:Subject: Re: Problem
with backup scripts
Dist Stor Manager"
<[EMAIL PROTECTED]
DU>


09/11/2003 03:16 PM
Please respond to
"ADSM: Dist Stor
Manager"






Look in the Windows Client manual for returncodes:


RC 8: The operation completed with at least one warning message. For
scheduled events, the status will be Completed. Review dsmerror.log (and
dsmsched.log for scheduled events) to determine what warning messages were
issued and to assess their impact on the operation.





-Original Message-
From: Neilson Lui [mailto:[EMAIL PROTECTED]
Sent: donderdag 11 september 2003 2:13
To: [EMAIL PROTECTED]
Subject: Problem with backup scripts


We just upgrade our clients from 5.1.5.0 to 5.1.6.6 and our server running
on Win2K from 5.1.5.0 to 5.1.7.2  , after the upgrade most of our backup
scripts fails with return code 8, can anyone help ? BTW, the backup was
complete with no errors:

scripts is

dsmc incr "c:\\*" -sudir=yes > c:/tsmscript/tsmdaily.log


and the message on the actlog is

09/11/2003 03:46:52   ANE4952I (Session: 5836, Node: OPXFS_AS)  Total
number of
   objects inspected:   59,099

09/11/2003 03:46:52   ANE4954I (Session: 5836, Node: OPXFS_AS)  Total
number of
   objects backed up:5,822

09/11/2003 03:46:52   ANE4958I (Session: 5836, Node: OPXFS_AS)  Total
number of
   objects updated:  0

09/11/2003 03:46:52   ANE4960I (Session: 5836, Node: OPXFS_AS)  Total
number of
   objects rebound:  0

09/11/2003 03:46:52   ANE4957I (Session: 5836, Node: OPXFS_AS)  Total
number of
   objects deleted:  0

09/11/2003 03:46:52   ANE4970I (Session: 5836, Node: OPXFS_AS)  Total
number of
   objects expired: 13

09/11/2003 03:46:52   ANE4959I (Session: 5836, Node: OPXFS_AS)  Total
number of
   objects failed:   0

09/11/2003 03:46:52   ANE4961I (Session: 5836, Node: OPXFS_AS)  Total
number of
   bytes transferred:  1.23 GB

09/11/2003 03:46:52   ANE4971I (Session: 5836, Node: OPXFS_AS)  LanFree
data
   bytes:

Re: TSM 4.2 and Exchange TDP 1.1.1

2003-09-12 Thread Ochs, Duane
>From the command line of the Exchange server.

excdsmc /adsmquerydb:* /adsmoptfile: >"what ever file you want to output it
to"


-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 8:27 PM
To: [EMAIL PROTECTED]
Subject: TSM 4.2 and Exchange TDP 1.1.1


I was just looking at my Exchange TDP output and have it showing all
exchange backups ever created. It shows directory backups and information
store backups (full and incremental. exchange 5.5). Is there someway I can
query our output this list of backups to a text file? On the TDP side I
don't see anything in the GUI. I'm guessing I need to do something with the
TDP cmdline to query a list of this (with dates) so I can hand this to
someone and get an idea of what to restore. Time to read some notes but if
someone knows off the top of their head how to do this I'd appreciate the
info.

Gerald



This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.


Re: DB2 high speed SP switch backups dead slow.

2003-09-12 Thread Zlatko Krastev
Long, long time ago, in ancient Rome there was a sentence - "divide and
conquer". Unfortunately I did not see this aproach used while it helps
most of the time.
Why not to isolate each part of the data route and ensure it is working at
best possible throughput? This might help to identify the bottleneck. The
subject is stating the "SP switch" backups are slow but are they due to
switch problems or for other reason(s)?!?

1. What is the speed when DB2 backup is performed to a file within the
same system? If its is good proceed with next, if not - investigate.
Information to be considered:
- number of disks (Shark is Shark, but how many ranks are used for DB and
what nodes/applications are accessing the same rank)
- number of tablespaces, managed by system or managed by database
- tablespace(s) page size
- what is the load on the DB2 during backup (the SP is not bought for
nothing)
- what is the load on the processors, HBAs and hdisks/vpaths before and
during backup

2. Number one advice when network problems are suspected - run FTP and
measure the performance. If the FTP is performing fine (this is a SP
switch on the end, it ought to achieve about 95-100 MB/s) stop blaming the
network. If FTP is slow, the TSM will also be slow without any fault on
its side - investigate the switch or TCP/IP stack.

3. Check for IP addressing problems (apologies if sounds silly or
offending) - if TCPServeraddress points to Ethernet address instead of
css0 address, obviously the speed would be lower by an order.
BTW: Miles, in your example TCPS=127.0.0.1 and switch is not used at all,
so the example does not relate to "switch" problem of the subject.

4. Check the speed of a backup performed by a client running on same
system as TSM server - will drop the network from the equation. If
performance is poor, the TSM server has to be tuned. If performance is
good - investigate other parts.

Zlatko Krastev
IT Consultant






Muthyam Reddy <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10.09.2003 22:18
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:DB2 high speed SP switch backups dead slow.


** High Priority **

Hi TSMers,
I hope someone got experiance on same before .

This is problem about db2(7.1) backups on high speed switch to TSM
.Present we are taking 430Gb of data to tsm which is taking 14 hrs to
finish.recently I have changed couple of paramters on 'css' and 'no' to
improve performance based on IBM docs.Still my backups takes same time.
no doubt I missed some parts on TSM/AIX/db2  to lubricate.
Please can any one dump some ideas to fix this this and how long its
taking in ur environment same setup.
We are using four session on db2(7.1) and copying to tape pools directly.


please send ur back times with same environments.

please send me some tips to make my backups fast.

please write if wants information.

thanks and regards
muthyam


Re: Excluding files during restore

2003-09-12 Thread Zlatko Krastev
In one of the new versions of the client a new option in the
dsm.sys/dsm.opt silently slipped - Exclude.Restore. It is not documented
at all, you cannot find it neither in the client manual nor in the `dsmc
help`!!!
But if you start the GUI client, select from the menu Edit -> Preferences,
choose Include-Exclude tab and select Category=Restore,  you can
specify which files you want *not* to be restored. They will be skipped on
restore same as ordinary Exclude prevents during incremental backup. Even
if you choose only that excluded file, you will not get it restored -
there is force backup using `dsmc selective` but there is no "selective
restore".
You can use compete exclude patterns:
Exclude.Restore "C:\my garbage\...\*"
Exclude.Restore /home/user/unwanted/*log

BTW: Andy, I think the option is useful (one of our customers liked it
very much) but needs to be documented. I've missed it till few days ago as
I am using the GUI client only when I teach a class (and teaching I've
learned about the option :-)))

Zlatko Krastev
IT Consultant






"Fernando Figueiredo (EDS)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10.09.2003 20:21
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Excluding files during restore


Hi!

Using command line to do a restore I would like to exclude some files or
directories.
Can I exclude files/directories using "dsmc restore"?


FF
EDS Portugal
Core Infrastructure - Systems Administration


Re: Non-IBM LTO tapes in a 3584

2003-09-12 Thread Shawn Price
Stephen,
 Was there some kind of announcement from IBM about this? I just had a tape
drive replaced yesterday (LTO-1) because the tape was stuck (The changer
couldn't remove it but I could wiggle it and it came out). None of the IBM
people I talked to have told me about this. Do you know where the clip goes
and specifically what it fixes?

Thanks

Shawn

> From: Stephen Comiskey <[EMAIL PROTECTED]>
> Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> Date: Fri, 12 Sep 2003 16:12:24 +0100
> To: [EMAIL PROTECTED]
> Subject: Re: Non-IBM LTO tapes in a 3584
>
> Hi,
>
> As well as having the latest firmware, IBM have recently issued a small
> plastic clip for LTO1 drives.  We were having problems with tapes ejecting
> (both IBM and non-IBM) and this helped resolve it along with the firmware
> upgrade.
>
> cheers
> Stephen
> Dublin, Ireland
>
>
> |-+--->
> | |   Dan Foster  |
> | |   <[EMAIL PROTECTED]>  |
> | |   Sent by: "ADSM: |
> | |   Dist Stor   |
> | |   Manager"|
> | |   <[EMAIL PROTECTED]|
> | |   T.EDU>  |
> | |   |
> | |   |
> | |   12/09/03 15:59  |
> | |   Please respond  |
> | |   to "ADSM: Dist  |
> | |   Stor Manager"   |
> | |   |
> |-+--->
>> -
>> --|
> |
> |
> |To:  [EMAIL PROTECTED]
> |
> |cc:
> |
> |Subject: Re: Non-IBM LTO tapes in a 3584
> |
>> -
>> --|
>
>
>
>
> THIS MESSAGE ORIGINATED ON THE INTERNET - Please read the detailed
> disclaimer below.
> --
> -
>
>
> Hot Diggety! Shawn Price was rumored to have written:
>>  For what it's worth, my boss cheaped out and got some non IBM tapes for
>>  our 3584, and I've had nothing but problems with them. Mostly Imation
>>  and a few Emtecs. We are running the first generation LTO 1 drives, so
>>  there might be an issue with those as well. I have now gone in and just
>>  started pulling the tapes that have gone read-only more than twice and
>>  replaced them with IBMs.
>
> Make sure your library and drives are at the latest firmware revision
> levels -- this is especially important since more recent firmware revs
> fixes bugs that causes problems with non-IBM tapes from what I hear.
>
> Latest 3584 library firmware you can get from IBM's web/ftp site: 3300
> if no D42 drives in library; else, 3060.
>
> To check firmware rev for library w/AIX: # lscfg -vl smc0 | grep FW
>
> The library firmware rev # also appears on the main LCD panel screen.
>
> Latest 3584 drive firmware you can get from IBM's web/ftp site: 36U3 for
> LTO-1 drives and 38D0 for LTO-2 drives.
>
> To check firmware rev for drive w/AIX: # lscfg -vl rmt0 | grep FW
> (...and for each drive... rmt1, rmt2, etc.)
>
> -Dan
>
>
> ---
> The following message has been automatically added by the mail gateway to
> comply with a Royal & SunAlliance IT Security requirement.
>
> As this email arrived via the Internet you should be cautious about its
> origin and content. Replies which contain sensitive information or
> legal/contractual obligations are particularly vulnerable. In these cases
> you should not reply unless you are authorised to do so, and adequate
> encryption is employed.
>
> If you have any questions, please speak to your local desktop support team
> or IT security contact.
> ---
>
>
>
>
>
>
> __
>
> Notice of Confidentiality
>
> This transmission contains information that may be confidential and that may
> also be privileged. Unless you are the intended recipient of the message (or
> authorised to receive it for the intended recipient) you may not copy,
> forward, or otherwise use it, or disclose it or its contents to anyone else.
> If you have received this transmission in error please notify us immediately
> and delete it from your system.
>
> Email: [EMAIL PROTECTED]
>


Re: Excluding files during restore

2003-09-12 Thread Andrew Raibeck
> BTW: Andy, I think the option is useful (one of our
> customers liked it very much) but needs to be documented.

Well, I'm afraid that I am going to have to disappoint on this, at least
for now. The option is deliberately undocumented, as it was put in there
for use only at the direction of IBM service. I don't even think it should
have been put in the GUI preferences editor, and in fact is being pulled
from the preferences editor for future releases. This option has not been
through any formal testing, so you use it at your own risk.

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.




Zlatko Krastev <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/12/2003 10:12
Please respond to "ADSM: Dist Stor Manager"

To: [EMAIL PROTECTED]
cc:
Subject:Re: Excluding files during restore


In one of the new versions of the client a new option in the
dsm.sys/dsm.opt silently slipped - Exclude.Restore. It is not documented
at all, you cannot find it neither in the client manual nor in the `dsmc
help`!!!
But if you start the GUI client, select from the menu Edit -> Preferences,
choose Include-Exclude tab and select Category=Restore,  you can
specify which files you want *not* to be restored. They will be skipped on
restore same as ordinary Exclude prevents during incremental backup. Even
if you choose only that excluded file, you will not get it restored -
there is force backup using `dsmc selective` but there is no "selective
restore".
You can use compete exclude patterns:
Exclude.Restore "C:\my garbage\...\*"
Exclude.Restore /home/user/unwanted/*log

BTW: Andy, I think the option is useful (one of our customers liked it
very much) but needs to be documented. I've missed it till few days ago as
I am using the GUI client only when I teach a class (and teaching I've
learned about the option :-)))

Zlatko Krastev
IT Consultant






"Fernando Figueiredo (EDS)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10.09.2003 20:21
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Excluding files during restore


Hi!

Using command line to do a restore I would like to exclude some files or
directories.
Can I exclude files/directories using "dsmc restore"?


FF
EDS Portugal
Core Infrastructure - Systems Administration


Re: Backing up Windows2003 Server with Client 5.2

2003-09-12 Thread Andrew Raibeck
> Just to make sureif I use the 5.1.6.x client configured
>just like I do for the WIndows2000 servers, I'll have a
> complete backup of the Windows2003 server?

Well, since I don't know how you have TSM clients configured on Windows
2000, so I can't say whether such a setup gets you a complete backup. But
if I go with the spirit of the question   ;-)then for traditional
incremental backup of the ALL-LOCAL domain, the answer is "yes". Peruse
the 5.1.6.x client README file for further info on Windows 2003 support
(searching for 2003 should help you find the info easily enough). I
suggest going with 5.1.6.7.

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.




Bill Boyer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/12/2003 08:38
Please respond to "ADSM: Dist Stor Manager"

To: [EMAIL PROTECTED]
cc:
Subject:Re: Backing up Windows2003 Server with Client 5.2


Just to make sureif I use the 5.1.6.x client configured just like I do
for the WIndows2000 servers, I'll have a complete backup of the
Windows2003
server? I realize it may not be taking advantage of the "features" of
Windows2003 and the TSM 5.2 level, but I just need to make sure these
servers are getting FULLY backed up.

Bill Boyer
DSS, Inc.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Andrew Raibeck
Sent: Friday, September 12, 2003 3:20 AM
To: [EMAIL PROTECTED]
Subject: Re: Backing up Windows2003 Server with Client 5.2


Bill, your read of the client manual is correct. For Windows 2003, TSM 5.2
uses the Microsoft VSS (Volume Shadowcopy Service) to back up system state
and system services, versus the "legacy" methods used in TSM 5.1 and
earlier to back up what we called the "system object".

In addition, the Windows 2003 system state/service backups use a different
transaction protocol that doesn't pin the server recovery log for
extensive periods of time, as might the "system object" backup method.
This support required changes on the server side as well, and thus the
requirement for a 5.2 server.

You can use the 5.1.6.x client and system object backup method for backing
up the Windows 2003 to a TSM 5.1 server.

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.




Bill Boyer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/11/2003 12:00
Please respond to "ADSM: Dist Stor Manager"

To: [EMAIL PROTECTED]
cc:
Subject:Backing up Windows2003 Server with Client 5.2


I ran a full backup of a Win2003 server last night with the 5.2.0.2
client.
The event shows as failed, but the backup actually backed up nothing.
Here's
the stats:

09/10/2003 22:11:48 --- SCHEDULEREC STATUS BEGIN
09/10/2003 22:11:48 Total number of objects inspected:   44,113
09/10/2003 22:11:48 Total number of objects backed up:0
09/10/2003 22:11:48 Total number of objects updated:  0
09/10/2003 22:11:48 Total number of objects rebound:  0
09/10/2003 22:11:48 Total number of objects deleted:  0
09/10/2003 22:11:48 Total number of objects expired:  0
09/10/2003 22:11:48 Total number of objects failed:  44,113
09/10/2003 22:11:48 Total number of bytes transferred: 2.44 GB
09/10/2003 22:11:48 Data transfer time:  139.91 sec
09/10/2003 22:11:48 Network data transfer rate:18,331.90 KB/sec
09/10/2003 22:11:48 Aggregate data transfer rate:  4,511.33 KB/sec
09/10/2003 22:11:48 Objects compressed by:0%
09/10/2003 22:11:48 Elapsed processing time:   00:09:28
09/10/2003 22:11:48 --- SCHEDULEREC STATUS END
09/10/2003 22:11:48 --- SCHEDULEREC OBJECT END BD72200 09/10/2003 22:00:00
09/10/2003 22:11:48 Scheduled event 'BD72200' completed successfully.

In the server log (this is a TSM 5.1.7.1 server on AIX 4.3.3) I see
numerous:

09/10/2003 22:06:49  ANRD smnode.c(19134): ThreadId<20> Session
38868 for
  node NWTRACKIT : Invalid filespace for backup
group
  member: 3.
09/10/2003 22:06:49  ANR0444W Protocol error on session 38868 for node
  NWTRACKIT (WinNT) - out-of-sequence verb (type
Data)
  received.
09/10/2003 22:06:50  ANRD smnode.c(19134): ThreadId<31> Session
38883 for
  node NWTRACKIT : Invalid filespace for backup
group
 

TSM Client Query

2003-09-12 Thread Gerald Wichmann
We frequently get tapes from other sources and are expected to restore them.
The problem I'm finding is the original environment sends me their TSM
database and it may have restores for a given server (say SERVERA) going
back a year (so lets say 365 backups that the TSM DB is aware of). Now they
only send me 200 tapes and I'm faced with figuring out which of those
backups that the DB knows about for SERVERA do I *actually have*? I realize
this is probably a perfect candidate for a select query or macro where I
pass in a list of volumes and it spits out what backup dates it knows about.
Something I'll have to figure out how to determine.

Similarly I'm curious though whether this is doable with Agent backups
(specifically Exchange)..

Anyone develop something like this so I don't have to reinvent the wheel?
Any thoughts? Appreciate the help lately.

Thanks!
Gerald



This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.


Upcoming FLASH - HPUX PCI drivers atdd 1909/3109 now available on external ftp site -- fix for TSM barcode mismatch problem

2003-09-12 Thread Sam Giallanza
TSM Community,


Upcoming Flash (number will be sent later under separate email)


Who is Affected:  IBM Tivoli Storage Manager (ITSM) 5.2 for Solaris and
HP-UX customers using IBM 3584, 3583, 3582, or 3581 tape libraries with
Ultrium LTO tape drives.

Problem:  Eight character volume names are being returned for the barcode
label from the tape library.  Previous ITSM releases labeled these volumes
with six character volume names from the barcode label.  This problem
causes the barcode labels to not match the labels written to the tape
volume for customers upgrading to ITSM 5.2 if the volume was labeled at a
previous level and checked in with ITSM 5.2.  When this condition is
encountered on a scratch volume the status is changed to private and the
operation tries to select another scratch volume.

Recommendation:  First upgrade to the following device driver levels or
higher for the tape library.

ftp://ftp.software.ibm.com/storage/devdrvr/HPUX/11.0_PCI/atdd.1.9.0.9.bin
ftp://ftp.software.ibm.com/storage/devdrvr/HPUX/11.0_PCI/atdd.fixlist

ftp://ftp.software.ibm.com/storage/devdrvr/HPUX/11i_PCI/atdd.3.1.0.9.bin
ftp://ftp.software.ibm.com/storage/devdrvr/HPUX/11i_PCI/atdd.fixlist

ftp://ftp.software.ibm.com/storage/devdrvr/Solaris/IBMtape.4.0.7.7.bin
ftp://ftp.software.ibm.com/storage/devdrvr/Solaris/IBMtape.fixlist

If upgrading is not possible at this time do not use barcodes for the LABEL
LIBVOL, CHECKIN LIBVOL, or AUDIT LIBRARY commands in order to prevent
problems with six character volumes and to prevent the creation of more
eight character volume names. Instead, explicitly specify a 6 character
label name.  For example, on the LABEL LIBVOL command, specify the 6
character label on the media  as the volume name rather than use the
barcode option.

After upgrading no further action is required if all volumes from the
output of QUERY LIBVOL, QUERY VOLUME, and QUERY VOLHISTORY have six
character volume names.  Volumes with eight character volumes names can
still be used, but the CHECKIN LIBVOL and AUDIT LIBRARY commands with
barcodes cannot be used on theses volumes.  To re-label the volumes to six
character volume names wait for the volume to return to scratch or move the
data off the volume using the MOVE DATA command, checkout the volume from
ITSM using the CHECKOUT LIBVOL command, and label the volume using the
LABEL LIBVOL command.


Cordially,


Sam J. Giallanza
Tivoli Certified Consultant
[EMAIL PROTECTED]
520.799.5512


Re: Non-IBM LTO tapes in a 3584

2003-09-12 Thread Anderson F. Nobre
I know a client that has bought Imation tapes and when they have used the
tape cartridges they jamed into the drive units.

Regards,

Anderson

- Original Message -
From: "Mark Ferraretto" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 11, 2003 1:30 AM
Subject: Non-IBM LTO tapes in a 3584


> All,
>
> We're looking at purchasing extra LTO-1 tapes to go in our 3584.  To date,
we've been running IBM tapes but we've gotten cheaper prices on HP and
Imation tapes.  Both HP and Imation are priced about 30% less than the IBM
tapes.
>
> But I'm wondering if there are any quality issues with either of these
brands.  Also, I'm wondering if running non-IBM tapes in a 3584 might raise
any issues.
>
> Can anyone help?
>
> Thanks
>
> Mark
>
>
> --
> Mark Ferraretto
> Unix Systems Administrator
> Deutsche Bank Hong Kong
> w: +852 2203 6362m: +852 9558 8032f: +852 2203 6971
> [EMAIL PROTECTED]
>
>
> --
>
> This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.