Exclude lists for TDP agents

[Bill Boyer]

I have a client that is using the TDP agents for MS-Exchange, Lotus Domino
and MS-SQL Server. These clients are also being backed up with the regular
TSM B/A client.

Could someone give us some pointers on exclude lists for the TSM B/A client
so that it doesn't backup the same data the TDP agent is backing up? The TDP
manuals don't go into this aspect of the 'total server' backup strategy.

Thanks,
Bill Boyer
DSS, Inc.
"He who laughs last, probably did a backup!" - ??

Re: root required to kill TSM daemons?

[Alex Paschal]

WELL, if you can't use sudo, and you can't write a C wrapper for the SUID
bit, and if PowerBroker can't just allow root privilage for a single
script/command/operation, I'd say your organization really needs to rethink
the services they provide to their IT customers.

Try cron as root a script that kills the scheduler process every day at
noon.

-Original Message-
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 1:16 PM
To: [EMAIL PROTECTED]
Subject: Re: root required to kill TSM daemons?


Our company uses Powerbroker access instead of sudo and they don't want to
give us
pbrun su-root privileges. Any other ideas?

-Original Message-
From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 11:47 AM
To: [EMAIL PROTECTED]
Subject: Re: root required to kill TSM daemons?


Pl look at sudo command acts as proxy for root only for that cmd.
BALANAND

-Original Message-
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: root required to kill TSM daemons?


We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
group needs to be able to stop the TSM daemons and start the start up
script, instead of always having the system admin. do this. Right now I am
told that there is no work around for root privileges being needed to kill
the TSM daemons. I'm wondering how other shops get around this problem? When
our TSM server crashes, all of the clients that are getting backed up are
getting hung schedulers and need to be bounced to resume working. The fact
that root privileges are needed to bounce the daemons is adding on days to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli had me
open an enhancement request.

Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

Re: root required to kill TSM daemons?

[Cheryl Miller]

Our company uses Powerbroker access instead of sudo and they don't want to
give us
pbrun su-root privileges. Any other ideas?

-Original Message-
From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 11:47 AM
To: [EMAIL PROTECTED]
Subject: Re: root required to kill TSM daemons?


Pl look at sudo command acts as proxy for root only for that cmd.
BALANAND

-Original Message-
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: root required to kill TSM daemons?


We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
group needs to be able to stop the TSM daemons and start the start up
script, instead of always having the system admin. do this. Right now I am
told that there is no work around for root privileges being needed to kill
the TSM daemons. I'm wondering how other shops get around this problem? When
our TSM server crashes, all of the clients that are getting backed up are
getting hung schedulers and need to be bounced to resume working. The fact
that root privileges are needed to bounce the daemons is adding on days to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli had me
open an enhancement request.

Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

backupsets - blocksizes

[John Bremer]

Seems we have found an area that can bog down restoring BACKUPSETS.  The
create backupset writes 32K blocks an will slow down any tape device that
performs better at 256K, for example.

Anybody know if there is a way to write larger blocks when creating BACKUPSETS?

Thanks.  John

At 10:10 AM 2/8/02 +, you wrote:
>Switch on perform tracing on the client.
>This will break down where the time is being spent, so you can identify your
>bottleneck
>I was seeing circa 3 mb. sec restoring a netware client from 9840 across a
>network
>With a directly attached tape and an  AIX client you ought to get better.
>John
>
>
>
>
>
>John Bremer <[EMAIL PROTECTED]> on 02/07/2002 11:07:01 PM
>
>Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
>To:   [EMAIL PROTECTED]
>cc:(bcc: John Naylor/HAV/SSE)
>Subject:  restoring backupsets
>
>
>
>*SMers,
>
>We're trying to restore a backupset from 9840 media.  Our tape drive is
>attached to an AIX client and we are seeing only 1-2 MB/sec data transfer
>rates.
>
>Is there a reason why we don't see tape and/or disk speeds on this
>restore?  The disk should run at 14-15 MB/sec and the SCSI 9840 at 10 MB/sec.
>
>THanks.  John Bremer
>
>
>
>
>
>
>
>
>**
>The information in this E-Mail is confidential and may be legally
>privileged. It may not represent the views of Scottish and Southern
>Energy plc.
>It is intended solely for the addressees. Access to this E-Mail by
>anyone else is unauthorised. If you are not the intended recipient,
>any disclosure, copying, distribution or any action taken or omitted
>to be taken in reliance on it, is prohibited and may be unlawful.
>Any unauthorised recipient should advise the sender immediately of
>the error in transmission.
>
>Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
>are trading names of the Scottish and Southern Energy Group.
>**

Re: client specific devices?

[Joshua S. Bassi]

One way to do this would be to add the one sole drive to a new device
class and storage pool and having that client's data associated with
that storage pool.


--
Joshua S. Bassi
Sr. Solutions Architect @ rs-unix.com
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (415) 215-0326
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Blanchette, Sherry
Sent: Friday, February 08, 2002 11:31 AM
To: [EMAIL PROTECTED]
Subject: client specific devices?

Is it possible, with TSM 4.1, to have a specific client write to a
specific
tape drive?  And to exclude all other clients from using that device?

Thanks,
Sherry Blanchette

Re: root required to kill TSM daemons?

[Joshua S. Bassi]

>From my experience working in the banking environment, the backup and
recovery group should have root or root capable privileges.  This can be
accomplished with something like sudo.


--
Joshua S. Bassi
Sr. Solutions Architect @ rs-unix.com
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (415) 215-0326
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Cheryl Miller
Sent: Friday, February 08, 2002 10:41 AM
To: [EMAIL PROTECTED]
Subject: root required to kill TSM daemons?

We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
group needs to be able to stop the TSM daemons and start the start up
script, instead of always having the system admin. do this. Right now I
am
told that there is no work around for root privileges being needed to
kill
the TSM daemons. I'm wondering how other shops get around this problem?
When
our TSM server crashes, all of the clients that are getting backed up
are
getting hung schedulers and need to be bounced to resume working. The
fact
that root privileges are needed to bounce the daemons is adding on days
to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on
most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli
had me
open an enhancement request.

Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

Re: root required to kill TSM daemons?

[Charles Anderson]

Ok,

Disclaimer #1 - I have never tried this.
Disclaimer #2 - I'm not painfully familair with solaris ( that's my guess at the os 
you're using )

BUT.. in theory ( cracks knuckles ), if your user account(s) had rw access to the 
Drives/Library ( i.e. /dev/ ), the TSM process ( i.e. daemon ) _should_ be allowed 
to run in user space, given that any port >1024 is unprivileged.  

I don't know what sort of dependancies the drivers might hold on needing root 
privileges, but even if the SysAdmin made a disk group and changed the devices to be 
owned and rw by that group, I don't see why it couldn't be done.

well, there's my 2cents.  change is expected.

-ed


Ed Anderson
Unix Systems Administrator
University of Mississippi Medical Center
[EMAIL PROTECTED]

>>> [EMAIL PROTECTED] 2002/02/08 03:16:11 PM >>>
Our company uses Powerbroker access instead of sudo and they don't want to
give us
pbrun su-root privileges. Any other ideas?

-Original Message-
From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 11:47 AM
To: [EMAIL PROTECTED]
Subject: Re: root required to kill TSM daemons?


Pl look at sudo command acts as proxy for root only for that cmd.
BALANAND

-Original Message-
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: root required to kill TSM daemons?


We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
group needs to be able to stop the TSM daemons and start the start up
script, instead of always having the system admin. do this. Right now I am
told that there is no work around for root privileges being needed to kill
the TSM daemons. I'm wondering how other shops get around this problem? When
our TSM server crashes, all of the clients that are getting backed up are
getting hung schedulers and need to be bounced to resume working. The fact
that root privileges are needed to bounce the daemons is adding on days to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli had me
open an enhancement request.

Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

Re: Sql Agent 2000 and TDP 2.2 for SQL for a cluster configuratio n.

[Del Hoobler]

> Yes, SQL Agent is the SQL Server Agent service.
> Yes, the /SQLServer option is being used in all cases which is set to the
> virtual server name.
>
> When using the SQL Server Agent and the DSM.opt has the Virtual SQL
Server
> node name we receive the follow error:
>
> NODENAME cannot be the local machine name when CLUSTERNODE is set to YES.
> Process Exit Code 418.  The step failed.
>
> The dsierror.log shows the following:
> 02/07/2002 15:05:20 ANS1155E CLUSTERNODE option is set to YES but cluster
is
> not enabled.
> Either the machine does not have cluster server installed, or the cluster
>  server is not running.

Bruce, Tony,

Try setting the following variable in
the batch file that you run right
BEFORE you kick off the tdpsqlc command.

_VIRTUAL_SERVER_NAME_=clus-server-name

where clus-server-name is the name of
your "CLUSTER virtual server" and
NOT the SQL virtual server name.
---

For example:

===

SET _VIRTUAL_SERVER_NAME_=VIRTUAL_SERVER_NAME
tdpsqlc backup * full /sqlserver=VIRTUAL_SQL_SERVER_NAME

===
Notice the values are different. One is the
virtual cluster name, and the other the
virtual SQL cluster name.

Thanks,

Del



Del Hoobler
IBM Corporation
[EMAIL PROTECTED]

"Celebrate we will. Life is short but sweet for certain..."  -- Dave

Re: root required to kill TSM daemons?

[Alex Paschal]

Haha!  I just thought of this one.  It might be morbidly attractive.

On TSM Server:
1. Create a node.  I'll use TEMPNODE.

On a workstation/server of similar OS where you have root:
2. Write the script to bounce the scheduler process (bounce.script).
3. Write and compile the C wrapper that runs the script to bounce the
scheduler (bounce.wrapper).
4. SUID on that wrapper so it runs as root.
5. Back up wrapper and script as TEMPNODE.

On TSM Server:
6. Create a CMD client schedule.
   cmd="dsmc -virtualnodename=tempnode -password=tempnodepw restore
/wherever/bounce.*"
7. Associate all appropriate nodes with this schedule.
8. After all nodes restore these files, shouldn't take more than longest
schedule poll period, they should all have bounce.script and SUID
bounce.wrapper.
9. Telnet/rlogin/ssh in and run the SUID wrapper whenever you like.

Note, I haven't tried this, and I'm not even sure if TSM restores the SUID
bit, but it might be worth a try seeing as how it keeps other security
attributes and you don't have any other options.

Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail


-Original Message-
From: Alex Paschal
Sent: Friday, February 08, 2002 1:23 PM
To: 'ADSM: Dist Stor Manager'
Subject: RE: root required to kill TSM daemons?


WELL, if you can't use sudo, and you can't write a C wrapper for the SUID
bit, and if PowerBroker can't just allow root privilage for a single
script/command/operation, I'd say your organization really needs to rethink
the services they provide to their IT customers.

Try cron as root a script that kills the scheduler process every day at
noon.

-Original Message-
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 1:16 PM
To: [EMAIL PROTECTED]
Subject: Re: root required to kill TSM daemons?


Our company uses Powerbroker access instead of sudo and they don't want to
give us
pbrun su-root privileges. Any other ideas?

-Original Message-
From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 11:47 AM
To: [EMAIL PROTECTED]
Subject: Re: root required to kill TSM daemons?


Pl look at sudo command acts as proxy for root only for that cmd.
BALANAND

-Original Message-
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: root required to kill TSM daemons?


We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
group needs to be able to stop the TSM daemons and start the start up
script, instead of always having the system admin. do this. Right now I am
told that there is no work around for root privileges being needed to kill
the TSM daemons. I'm wondering how other shops get around this problem? When
our TSM server crashes, all of the clients that are getting backed up are
getting hung schedulers and need to be bounced to resume working. The fact
that root privileges are needed to bounce the daemons is adding on days to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli had me
open an enhancement request.

Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

Re: pL HELP .

[Haskins, Mike]

>From a TSM client session on node_A grant access to users on node_Y:
  set access b * node_Y *
Then to confirm:
  q access

On a node_Y TSM client session:
restore -fromn=node_A < file or dir/ >

-Original Message-
From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 2:50 PM
To: [EMAIL PROTECTED]
Subject: pL HELP .


All
I want to restore A nodes data on Y node belonging to same TSM server.
I know that NFS may be the solution after restoration. But can
configure this TSM for that. I did give authority access.
I tried all the sent on this mail but still in vain.
Pl help me .
Thanks to all who mailed to my question. Thanks again.
Balanand Pinni

Re: Sql Agent 2000 and TDP 2.2 for SQL for a cluster configuratio n.

[Del Hoobler]

> When using the SQL Server Agent and the DSM.opt has the Virtual SQL
Server
> node name we receive the follow error:
>
> NODENAME cannot be the local machine name when CLUSTERNODE is set to YES.
> Process Exit Code 418.  The step failed.

Bruce, Tony,

Can you tell me the exact version of TDP for SQL that you are using?

Thanks,

Del

Re: Sql Agent 2000 and TDP 2.2 for SQL for a cluster configuratio n.

[Bruce Lowrie]

Del,
Yes, SQL Agent is the SQL Server Agent service.
Yes, the /SQLServer option is being used in all cases which is set to the
virtual server name.

When using the SQL Server Agent and the DSM.opt has the Virtual SQL Server
node name we receive the follow error:

NODENAME cannot be the local machine name when CLUSTERNODE is set to YES.
Process Exit Code 418.  The step failed.

The dsierror.log shows the following:
02/07/2002 15:05:20 ANS1155E CLUSTERNODE option is set to YES but cluster is
not enabled.
Either the machine does not have cluster server installed, or the cluster
 server is not running.

But from command line and the TDP GUI it works fine.

-Original Message-
From: Del Hoobler [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 3:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Sql Agent 2000 and TDP 2.2 for SQL for a cluster
configuration.


> My SQL expert is having an issue with the SQL Agent and TDP for SQL in a
> Windows 2000 clustered environment using MSSQL 2000 . When you run a
backup
> from the SQL agent the DSM.OPT file must have the following:
>
> NODENAMECLUSTERNAME (In this case LABCDB10)
>
> CLUSTERNODE YES
>
> When run from the command line or TDP SQL GUI the opt file must have :
>
> NODENAMEVIRTUALNODENAME (Where SQL is loaded, LABVDB10)
>
> CLUSTERNODE YES


When running this in a cluster, you should be using the
exact same NODENAME in the dsm.opt file for TDP for SQL
CLI or GUI.  If you use different NODENAMEs the backups
will be going to different filespaces.
It is our recommendation that the NODENAME you use
match the virtual SQL server name. It should not be
the cluster server name.

I am not sure I understand. When you say "SQL agent" what are
you referring to?  TDP for SQL?  The MS SQL agent service?
Or, do you mean the TSM scheduler?

Are you using the "/SQLSERVER" option when using the
TDP for SQL CLI and GUI? You should be and you must
specify the virtual SQL server name on that option.

For more details see Chapter 1 and Appendix C of the
User's Guide.

Thanks,

Del



Del Hoobler
IBM Corporation
[EMAIL PROTECTED]

"Celebrate we will. Life is short but sweet for certain..."  -- Dave


This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com



This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com

Re: Backing up MS-SQL without the TDP

[Wholey, Joseph (TGA\\MLOL)]

If you have the space on the SQL server, use MS' built in feature to back it up 
locally, then back it with TSM and delete it.

-Original Message-
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 2:31 PM
To: [EMAIL PROTECTED]
Subject: Backing up MS-SQL without the TDP

Has anyone got a working procedure they use to backup a server with MS-SQL
on it, without using the TDP ?  We can't afford to by any more licenses of
the TDP.

I realize there is an SC.EXE program that can be used to shut-down and
start the SQL process.

Any help would be appreciated.

Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: [EMAIL PROTECTED]  -  voice: 804-828-4807

Re: Sql Agent 2000 and TDP 2.2 for SQL for a cluster configuration.

[Del Hoobler]

> My SQL expert is having an issue with the SQL Agent and TDP for SQL in a
> Windows 2000 clustered environment using MSSQL 2000 . When you run a
backup
> from the SQL agent the DSM.OPT file must have the following:
>
> NODENAMECLUSTERNAME (In this case LABCDB10)
>
> CLUSTERNODE YES
>
> When run from the command line or TDP SQL GUI the opt file must have :
>
> NODENAMEVIRTUALNODENAME (Where SQL is loaded, LABVDB10)
>
> CLUSTERNODE YES


When running this in a cluster, you should be using the
exact same NODENAME in the dsm.opt file for TDP for SQL
CLI or GUI.  If you use different NODENAMEs the backups
will be going to different filespaces.
It is our recommendation that the NODENAME you use
match the virtual SQL server name. It should not be
the cluster server name.

I am not sure I understand. When you say "SQL agent" what are
you referring to?  TDP for SQL?  The MS SQL agent service?
Or, do you mean the TSM scheduler?

Are you using the "/SQLSERVER" option when using the
TDP for SQL CLI and GUI? You should be and you must
specify the virtual SQL server name on that option.

For more details see Chapter 1 and Appendix C of the
User's Guide.

Thanks,

Del



Del Hoobler
IBM Corporation
[EMAIL PROTECTED]

"Celebrate we will. Life is short but sweet for certain..."  -- Dave

Re: Backing up MS-SQL without the TDP

[Zoltan Forray/AC/VCU]

This is what I am leaning towards.

However, simply stopping the service isn't enough. The tables are still
"in use".






Uwe Schreiber <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
02/08/2002 02:35 PM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: Backing up MS-SQL without the TDP


Hi,

you have the coice.

1. Make an online backup of your database to disk using the provided
machenism of SQL-Server,
and the backup will be during the normal scheduled backup.

or

2. Stop the Services for MS-SQL during a PRECOMMANDSCHEDULE. You can use
the mentioned SC.EXE tool
provided by the NT Resource Kit, scripted to stop the services.
After the offline-backup, use a POSTCOMMANDSCHEDULE. You can use the
SC.EXE tool, scripted to start the services.

Regards,
Uwe Schreiber





[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
08.02.2002 20:29
Please respond to ADSM-L


To: [EMAIL PROTECTED]
bcc:
Subject:Backing up MS-SQL without the TDP

Has anyone got a working procedure they use to backup a server with MS-SQL
on it, without using the TDP ?  We can't afford to by any more licenses of
the TDP.

I realize there is an SC.EXE program that can be used to shut-down and
start the SQL process.

Any help would be appreciated.

--
-- Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: [EMAIL PROTECTED]  -  voice: 804-828-4807

client specific devices?

[Blanchette, Sherry]

Is it possible, with TSM 4.1, to have a specific client write to a specific
tape drive?  And to exclude all other clients from using that device?

Thanks,
Sherry Blanchette

Re: Backing up MS-SQL without the TDP

[Bruce Kamp]

Why not just use SQL's backup procedure & backup to local disc & then this
will be backed up when you do your file system backups?  I do this on a
couple of my smaller DB's


Bruce Kamp
Network Analyst II
Memorial Healthcare System
P: (954) 987-2020 x6008
E: [EMAIL PROTECTED]


-Original Message-
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 2:31 PM
To: [EMAIL PROTECTED]
Subject: Backing up MS-SQL without the TDP

Has anyone got a working procedure they use to backup a server with MS-SQL
on it, without using the TDP ?  We can't afford to by any more licenses of
the TDP.

I realize there is an SC.EXE program that can be used to shut-down and
start the SQL process.

Any help would be appreciated.


Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: [EMAIL PROTECTED]  -  voice: 804-828-4807

Re: Backing up MS-SQL without the TDP

[Joe Cascanette]

You can schedule SQL to create backups of your databases to a directory before TSM 
starts it backup (TSM can pick up the backup files). You can then restore the 
databases into a fresh copy of SQL if needed. Check the Microsoft site for procedures 
for this (restore from backup). This worked fine (abit longer to restore) in your DR 
testing.

We dont use TDP for SQL, again $$$ is a factor...

Joe Cascanette
The Cumis Group Limited

-Original Message-
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 2:31 PM
To: [EMAIL PROTECTED]
Subject: Backing up MS-SQL without the TDP


Has anyone got a working procedure they use to backup a server with MS-SQL
on it, without using the TDP ?  We can't afford to by any more licenses of
the TDP.

I realize there is an SC.EXE program that can be used to shut-down and
start the SQL process.

Any help would be appreciated.

Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: [EMAIL PROTECTED]  -  voice: 804-828-4807

Re: root required to kill TSM daemons?

[DeMuse]

Some shops use a unix tool called "sudo" as alternative.


- Original Message -
From: "Thomas Denier" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 08, 2002 1:20 PM
Subject: Re: root required to kill TSM daemons?


> > We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
> > group needs to be able to stop the TSM daemons and start the start up
> > script, instead of always having the system admin. do this. Right now I
am
> > told that there is no work around for root privileges being needed to
kill
> > the TSM daemons. I'm wondering how other shops get around this problem?
When
> > our TSM server crashes, all of the clients that are getting backed up
are
> > getting hung schedulers and need to be bounced to resume working. The
fact
> > that root privileges are needed to bounce the daemons is adding on days
to
> > our resolution, since we have to open a problem ticket with the system
> > admin. group and wait for them to bounce the daemons. We have ids on
most of
> > the unix servers and could do it, if the permissions allowed.
> >
> > Any ideas?? Do any of you have a work around for this problem? Tivoli
had me
> > open an enhancement request.
>
> I either have root access or can get reasonably quick responses from
> administrators on all of my site's TSM client system. If I were in your
> position I would have the administrators install a perl or shell script
> that would kill any running 'dsmc sched' process and start a new one.
>
> The administrators would have to do one of two things with the script:
>
> 1.Make the script root owned, executable by your ID, and SUID.
>
> 2.Write a small (six lines or less, depending on one's white space
> conventions) C program that uses the 'execv' function to run the script,
> compile the program, and make the object code root owned, executable by
> your ID, and SUID.
>
> The SUID attribute causes an executable file to run with the authority of
> its owner rather than the authority of the person invoking the program.
> Many UNIX implementations still have an ancient bug that makes a script
> with the SUID attribute a serious security exposure. If your client
systems
> have this bug you will need the second approach despite its additional
> complexity.

pL HELP .

[PINNI, BALANAND (SBCSI)]

All
I want to restore A nodes data on Y node belonging to same TSM server.
I know that NFS may be the solution after restoration. But can
configure this TSM for that. I did give authority access.
I tried all the sent on this mail but still in vain.
Pl help me .
Thanks to all who mailed to my question. Thanks again.
Balanand Pinni

Re: root required to kill TSM daemons?

[PINNI, BALANAND (SBCSI)]

Pl look at sudo command acts as proxy for root only for that cmd.
BALANAND

-Original Message-
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: root required to kill TSM daemons?


We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
group needs to be able to stop the TSM daemons and start the start up
script, instead of always having the system admin. do this. Right now I am
told that there is no work around for root privileges being needed to kill
the TSM daemons. I'm wondering how other shops get around this problem? When
our TSM server crashes, all of the clients that are getting backed up are
getting hung schedulers and need to be bounced to resume working. The fact
that root privileges are needed to bounce the daemons is adding on days to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli had me
open an enhancement request.

Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

Backing up MS-SQL without the TDP

[Zoltan Forray/AC/VCU]

Has anyone got a working procedure they use to backup a server with MS-SQL
on it, without using the TDP ?  We can't afford to by any more licenses of
the TDP.

I realize there is an SC.EXE program that can be used to shut-down and
start the SQL process.

Any help would be appreciated.

Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: [EMAIL PROTECTED]  -  voice: 804-828-4807

Re: Backing up MS-SQL without the TDP

[Uwe Schreiber]

Hi,

you have the coice.

1. Make an online backup of your database to disk using the provided
machenism of SQL-Server,
and the backup will be during the normal scheduled backup.

or

2. Stop the Services for MS-SQL during a PRECOMMANDSCHEDULE. You can use
the mentioned SC.EXE tool
provided by the NT Resource Kit, scripted to stop the services.
After the offline-backup, use a POSTCOMMANDSCHEDULE. You can use the
SC.EXE tool, scripted to start the services.

Regards,
Uwe Schreiber





[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
08.02.2002 20:29
Please respond to ADSM-L


To: [EMAIL PROTECTED]
bcc:
Subject:Backing up MS-SQL without the TDP

Has anyone got a working procedure they use to backup a server with MS-SQL
on it, without using the TDP ?  We can't afford to by any more licenses of
the TDP.

I realize there is an SC.EXE program that can be used to shut-down and
start the SQL process.

Any help would be appreciated.

--
-- Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: [EMAIL PROTECTED]  -  voice: 804-828-4807

AW: TSM functions and Intranet

[Rupp Thomas (Illwerke)]

Thanks for your response!
Our TSM server is a NSM (Network Storage Manager) - actually a H50 box.
This is intended to be a black box (all upgrades are done by IBM) but I get
the impression that I should get familiar with AIX and all those other
things I
need to write CGI programs (PERL or PHP ...).

As there is a webserver running on TSM I thought I could write my QUERY and
UPDATE requests just the same way tivoli does.

I think I will try ODBC for the query part and some scripts for the update
part.

Thomas Rupp

> -Ursprüngliche Nachricht-
> Von:  Alex Paschal [SMTP:[EMAIL PROTECTED]]
> Gesendet am:  Freitag, 08. Februar 2002 20:20
> An:   [EMAIL PROTECTED]
> Betreff:  Re: TSM functions and Intranet
> 
> You could easily write simple perl cgi's that take your form data as
> input,
> construct your dsmadmc command, execute it, take the output and format it
> for display on the browser.  Or, like Lawrence posted, if you can script
> your process so that it runs the same way every day, you can just create a
> shell script cgi that simply executes that script when you click on the
> link.
> 
> Alex Paschal
> Storage Administrator
> Freightliner, LLC
> (503) 745-6850 phone/vmail
> 


--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

Re: disaster recovery

[MacMurray, Andrea (CC-ETS Ent Storage Svcs)]

We are using the IBM side in Gaithersburg and just had a very successful DR
test.
Andrea Mac Murray
Sen. Systems Administrator
ConAgra Foods, Inc.
7300 World Communication Drive
Omaha,NE 68122
Tel: (402) 577-3603
[EMAIL PROTECTED]


-Original Message-
From: Coviello, Paul [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 1:14 PM
To: [EMAIL PROTECTED]
Subject: disaster recovery


HI, we are currently putting together our disaster recovery plan.  I was
wondering what you may use as to any of the disaster services (Sungard,
IBM...) or even your own hotsite? with duplicate equipment.

thanks
Paul

Paul J Coviello
Sr Systems Analyst
Catholic Medical Center
2456 Brown Ave
Manchester, NH 03103
603 663-5326

Sql Agent 2000 and TDP 2.2 for SQL for a cluster configuration.

[Bruce Lowrie]

My SQL expert is having an issue with the SQL Agent and TDP for SQL in a
Windows 2000 clustered environment using MSSQL 2000 . When you run a backup
from the SQL agent the DSM.OPT file must have the following:

NODENAMECLUSTERNAME (In this case LABCDB10)

CLUSTERNODE YES

When run from the command line or TDP SQL GUI the opt file must have :

NODENAMEVIRTUALNODENAME (Where SQL is loaded, LABVDB10)

CLUSTERNODE YES

Anyone else having this problem?
Bruce E. Lowrie
Sr. Systems Analyst
Information Technology Services
Storage, Output, Legacy
*E-Mail: [EMAIL PROTECTED]
*Voice: (989) 496-6404
7 Fax: (989) 496-6437
*Post: 2200 W. Salzburg Rd.
*Post: Mail: CO2111
*Post: Midland, MI 48686-0994
This e-mail transmission and any files that accompany it may contain
sensitive information belonging to the sender. The information is intended
only for the use of the individual or entity named. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or the taking of any action in reliance on the contents of
this information is strictly prohibited. Dow Corning's practice statement
for digitally signed messages may be found at
http://www.dowcorning.com/dcps. If you have received this e-mail
transmission in error, please immediately notify the Security Administrator
at 



This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com

Re: dsm.opt file

[Rushforth, Tim]

To ensure that you have excluded it properly, start the TSM Gui and go to
the backup window.  Drill down to the TSM directory - the dsmsched.log file
should have an red X in it.  If it doesn't you probably have the wrong
syntax for the exclude.

If the X, is there, is this a scheduled backup and if so have you restarted
the TSM Schedule service so that it reads the updated option file?

-Original Message-
From: Aaron Bontrager [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 12:30 PM
To: [EMAIL PROTECTED]
Subject: dsm.opt file


Ok I need a little help here. I have excluded dsmsched.log in my dsm.opt. It
is still trying to backup this log. I am running TSM 4.2. on a Windows based
server.

Thanks
Aaron Bontrager

Re: root required to kill TSM daemons?

[Thomas Denier]

> We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
> group needs to be able to stop the TSM daemons and start the start up
> script, instead of always having the system admin. do this. Right now I am
> told that there is no work around for root privileges being needed to kill
> the TSM daemons. I'm wondering how other shops get around this problem? When
> our TSM server crashes, all of the clients that are getting backed up are
> getting hung schedulers and need to be bounced to resume working. The fact
> that root privileges are needed to bounce the daemons is adding on days to
> our resolution, since we have to open a problem ticket with the system
> admin. group and wait for them to bounce the daemons. We have ids on most of
> the unix servers and could do it, if the permissions allowed.
>
> Any ideas?? Do any of you have a work around for this problem? Tivoli had me
> open an enhancement request.

I either have root access or can get reasonably quick responses from
administrators on all of my site's TSM client system. If I were in your
position I would have the administrators install a perl or shell script
that would kill any running 'dsmc sched' process and start a new one.

The administrators would have to do one of two things with the script:

1.Make the script root owned, executable by your ID, and SUID.

2.Write a small (six lines or less, depending on one's white space
conventions) C program that uses the 'execv' function to run the script,
compile the program, and make the object code root owned, executable by
your ID, and SUID.

The SUID attribute causes an executable file to run with the authority of
its owner rather than the authority of the person invoking the program.
Many UNIX implementations still have an ancient bug that makes a script
with the SUID attribute a serious security exposure. If your client systems
have this bug you will need the second approach despite its additional
complexity.

Re: dsm.opt file

[Joe Cascanette]

Make sure you recycle the client services.



-Original Message-
From: Aaron Bontrager [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 1:30 PM
To: [EMAIL PROTECTED]
Subject: dsm.opt file


Ok I need a little help here. I have excluded dsmsched.log in my dsm.opt. It
is still trying to backup this log. I am running TSM 4.2. on a Windows based
server.

Thanks
Aaron Bontrager

Re: TSM functions and Intranet

[Alex Paschal]

You could easily write simple perl cgi's that take your form data as input,
construct your dsmadmc command, execute it, take the output and format it
for display on the browser.  Or, like Lawrence posted, if you can script
your process so that it runs the same way every day, you can just create a
shell script cgi that simply executes that script when you click on the
link.

Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail


-Original Message-
From: Rupp Thomas (Illwerke) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 10:36 AM
To: [EMAIL PROTECTED]
Subject: AW: TSM functions and Intranet


Sorry, I forgot to mention.
I'm running TSM 4.1.5.0 on AIX 4.3

Thomas Rupp




--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG

--

AW: TSM functions and Intranet

[Rupp Thomas (Illwerke)]

Sorry, I forgot to mention.
I'm running TSM 4.1.5.0 on AIX 4.3

Thomas Rupp



--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

disaster recovery

[Coviello, Paul]

HI, we are currently putting together our disaster recovery plan.  I was
wondering what you may use as to any of the disaster services (Sungard,
IBM...) or even your own hotsite? with duplicate equipment.

thanks
Paul

Paul J Coviello
Sr Systems Analyst
Catholic Medical Center
2456 Brown Ave
Manchester, NH 03103
603 663-5326

Re: root required to kill TSM daemons?

[Alex Paschal]

I suggest using the sudo utility to script your kill commands so they can
run as root.

Alex


-Original Message-
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 10:41 AM
To: [EMAIL PROTECTED]
Subject: root required to kill TSM daemons?


We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
group needs to be able to stop the TSM daemons and start the start up
script, instead of always having the system admin. do this. Right now I am
told that there is no work around for root privileges being needed to kill
the TSM daemons. I'm wondering how other shops get around this problem? When
our TSM server crashes, all of the clients that are getting backed up are
getting hung schedulers and need to be bounced to resume working. The fact
that root privileges are needed to bounce the daemons is adding on days to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli had me
open an enhancement request.

Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

Re: dsm.opt file

[David Longo]

Did you stop and restart the scheduler after making the change to dsm.opt?

David Longo

>>> [EMAIL PROTECTED] 02/08/02 01:29PM >>>
Ok I need a little help here. I have excluded dsmsched.log in my dsm.opt. It
is still trying to backup this log. I am running TSM 4.2. on a Windows based
server.

Thanks
Aaron Bontrager



"MMS " made the following
 annotations on 02/08/02 14:15:31
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

dsm.opt file

[Aaron Bontrager]

Ok I need a little help here. I have excluded dsmsched.log in my dsm.opt. It
is still trying to backup this log. I am running TSM 4.2. on a Windows based
server.

Thanks
Aaron Bontrager

Re: TSM functions and Intranet

[Lawrence Clark]

is your server NT or AIX?

>>> [EMAIL PROTECTED] 02/08/02 01:24PM >>>
Hi *SM-ers,

now our daily TSM operation (checkout DB backup, copy pool volumes ...) is
done
using a home grown GUI on VM/ESA.
But in a few months there will be no mainframe in this company any more.

So I'm looking to bring the daily TSM operation functions to our intranet.
The query part seems to be ease - install TSM ODBC on the intranet server
and
query the TSM DB using SQL.

But how do I implement the UPDATE part?
Is it possible to do it the way Tivoli does? Define a form in HTML and call
a function
on the server like

Is this described anywhere? Is this supported?
If not can I call DSMADMC running on the web server directly using HTML?
How do you bring TSM functions to your intranet?

I'm grateful for any replies.

Kind regards
Thomas Rupp
Vorarlberger Illwerke AG
MAIL:   [EMAIL PROTECTED] 
TEL:++43/5574/4991-251
FAX:++43/5574/4991-820-8251




--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

Re: AW: TSM functions and Intranet

[Lawrence Clark]

Hi:
On AIX, the below should provide you with away of doing tghe daily checkouts.



DSMCMD COMMAND SCRIPT FOR PASSING DSMCMD COMMANDS
dsmadmc -id=admin -pa= -displaymode=table $1


SCRIPT TO BACKUP CRITICAL TSM FILES DAILY
# =
# Back up ADSM DB and files needed for recovery
# 
echo "_\n"
echo "STARTING THE DAILY ADSM SERVER COMPONENTS BACKUP"
date
echo "_\n"
/home/root/bin/dsmcmd "disable sessions"
rm /var/adsmdbbk/*
echo "Perform full backup of ADSM database to disk /var/adsmdbbk...\n"
/home/root/bin/dsmcmd "backup db devclass=adsmdbbk type=full"
sleep 2400
echo "Current ADSM database backup:\n"
ls -la /var/adsmdbbk/*.DBB
echo "Update ADSM device config file (devconfig.info)...\n"
date
/home/root/bin/dsmcmd "backup devconfig"
echo "Update ADSM volume history file (volhistory.info)...\n"
date
/home/root/bin/dsmcmd "backup volhistory"
sleep 60
echo "Resuming client activity of the ADSM server\n"
/home/root/bin/dsmcmd "enable sessions"
echo "COPYING FILES TO ADSMDBBK DIRECTORY FOR BACKUP"
FILES="/usr/tivoli/tsm/server/bin/dsmserv.dsk \
/usr/tivoli/tsm/server/bin/dsmserv.opt\
/home/root/tsmfiles/devconfig.info  \
/home/root/tsmfiles/inclexcl.list  \
/usr/tivoli/tsm/client/ba/bin/dsm.sys \
/home/root/tsmfiles/dsm.opt  \
/home/root/tsmfiles/volhistory.info"
cp $FILES /var/adsmdbbk
/home/root/bin/backup.adsmserver.files >> /workarea/LOGS/ADSM
echo "___\n"
date
echo "END OF ADSM SERVER COMPONENT BACKUP FOR TODAY"
echo "___\n"

SCRIPT THAT DOES OFFSITE STORAGE OF TSM FILES AND CHECKOUT OF COPYPOOL  VOLUMES
#---
# Performs a backup of /var/adsmdbbk/*
# that hold ADSM file backups needed to recreate
# the ADSM server..L. Clark
# sent to /dev/rmt3 drive in 7331 8MM tape library
#---
#
DEVICE=/dev/rmt3
DRIVENUM=24
STGPOOL=OFFSITVOLS
export DEVICE DRIVENUM STGPOOL
#
#---
MoveIn ()
# Move tape to drive
{
/usr/bin/tapeutil -f /dev/smc0 move -s ${SLOT} -d ${DRIVENUM}
sleep 10
}
#---
MoveOut ()
# Unload tape and move back to slot
{
/usr/bin/tapeutil -f ${DEVICE} unload
/usr/bin/tapeutil -f /dev/smc0 move -s ${DRIVENUM} -d ${SLOT}
echo Time: `date +"%T"`
}
#---
BackupCmd ()
{
banner $TITLE
echo "==="
echo Start: `date +"%T"`
echo "===\n"
# tar -cvf /dev/rmt2.1 /workarea/ADSMBACK/*
tar -cvf /dev/rmt3.1 /var/adsmdbbk
}
#---
Offsitetape ()
# - readin tape vol input until EOF
# - issue checkout & then update to offsite
# - for each vol input
{
while read volname; do
echo "FOUND CANDIDATE FOR OFFSITE MIGRATION: "$volname
/home/root/bin/dsmcmd "CHECKO LIBV IBM3494A $volname "
/home/root/bin/dsmcmd "UPDATE VOL $volname ACC=OFFSITE"
done
}
#-
# FIRST: CAPTURE ADSM SERVER FILES TO 8MM
SLOT=20
TITLE=ADSM-SERVBK
HOST=backup
MoveIn;BackupCmd;MoveOut;echo "\nOK...\n"
#-
echo "==="
echo End: `date +"%T"`
echo "===\n"
echo "Done.  Check above for errors.\n"
echo "Then remove 8MM tape from SLOT 20.\n"
echo "WRITE DATE ON 8MM TAPE LABEL.\n"
echo "Check the tape library exit / entry port and\n"
echo "package with ADSM 3494(J) offsite data volumes.\n"
#-
# SECOND: GET LIST OF ONSITE COPY POOL VOLUMES
/home/root/bin/dsmcmd \
 "select volume_name from volumes where stgpool_name='OFFSITEVOLS' \
AND NOT access='OFFSITE'" > SQLTEST
grep "^[000]" SQLTEST > VOLLIST
#
# THIRD: CHECK CANDIDATE VOLUMES OUT
Offsitetape < VOLLIST
echo " done reading volume input"
echo " creating DRM PLAN FILE"
rm /home/root/recoveryplan/*
/home/root/bin/dsmcmd "prepare"
sleep 300
lp /home/root/recoveryplan/*
#
# FOURTH: FINISH LOG ENTRIES, APPEND DOY, PRINT
rm getday
date +%j>>getday
LOGDAY=$(>> [EMAIL PROTECTED] 02/08/02 01:35PM >>>
Sorry, I forgot to mention.
I'm running TSM 4.1.5.0 on AIX 4.3

Thomas Rupp



--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

root required to kill TSM daemons?

[Cheryl Miller]

We just converted to TSM 4.2.1.9 from NetBackup. We are finding that our
group needs to be able to stop the TSM daemons and start the start up
script, instead of always having the system admin. do this. Right now I am
told that there is no work around for root privileges being needed to kill
the TSM daemons. I'm wondering how other shops get around this problem? When
our TSM server crashes, all of the clients that are getting backed up are
getting hung schedulers and need to be bounced to resume working. The fact
that root privileges are needed to bounce the daemons is adding on days to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli had me
open an enhancement request.

Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

TSM functions and Intranet

[Rupp Thomas (Illwerke)]

Hi *SM-ers,

now our daily TSM operation (checkout DB backup, copy pool volumes ...) is
done
using a home grown GUI on VM/ESA.
But in a few months there will be no mainframe in this company any more.

So I'm looking to bring the daily TSM operation functions to our intranet.
The query part seems to be ease - install TSM ODBC on the intranet server
and
query the TSM DB using SQL.

But how do I implement the UPDATE part?
Is it possible to do it the way Tivoli does? Define a form in HTML and call
a function
on the server like

Is this described anywhere? Is this supported?
If not can I call DSMADMC running on the web server directly using HTML?
How do you bring TSM functions to your intranet?

I'm grateful for any replies.

Kind regards
Thomas Rupp
Vorarlberger Illwerke AG
MAIL:   [EMAIL PROTECTED]
TEL:++43/5574/4991-251
FAX:++43/5574/4991-820-8251




--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

Re: TSM Device Driver (Support for Unsupported Jukeboxes)

[Hunny Kershaw]

Hello Justin,

A device could work with "unofficial" support from Tivoli if the device
identification is recognized by the device driver. However, each Sony
Jukebox has its own unique identification such as "OSL-2500" or "OSL-6000".
OSL-2001 may have its own ID "OSL-2001" and therefore won't be recognized
by the TSM device driver.

Please contact Irfan Habib ([EMAIL PROTECTED]) for device support request.

Regards,

Hunny Kershaw





  Justin Derrick
   cc:
  Sent by: "ADSM:  Subject:  TSM Device Driver (Support 
for Unsupported Jukeboxes)
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  02/07/2002 09:01
  PM
  Please respond to
  "ADSM: Dist Stor
  Manager"





I've been looking for a new optical jukebox for my system at home since my
old HP unit died in the midst of an upgrade.

I was looking at an Sony OSL-2001, a nice, compact, fairly inexpensive unit
(used, of course), but it appears to be the ONLY Sony library that's
unsupported.  It uses the Sony 2.6GB drives (which ARE supported by TSM,
alone or in jukeboxes like the older 3995's) and appears to be in the same
family of jukeboxes manufactured by Sony (OSL-6000, 1, etc), but isn't
on the supported devices list.

I guess the questions are these...

Does anyone know if this device is 'unoffically' supported, ie "works, but
don't expect tech support"?

What's the criteria for device support?  I understand that Tivoli/IBM can't
be expected to buy/rent/lease/borrow/beg/steal every model of optical
jukebox ever manufactured, but it seems (from the outside, looking in
through dirty stained glass windows) that there shouldn't be an issue
supporting one more model from a supported line of products.  (Of course,
if it were simple, it would probably already be done, right?)

-JD.

Re: TDP Oracle 2.1.10 'libobk.so' problems on Oracle 8.1.7 / Solaris 2.7

[Thiha Than]

hi,

Please use TSM 4.1.2.12 API 32 bit not 64 bit.  Your problem should be
fixed by doing so.

regards,
Thiha
To: [EMAIL PROTECTED]
cc:
Subject:TDP Oracle 2.1.10 'libobk.so' problems on Oracle 8.1.7 / Solaris 2.7




We have the following configuration (all on same Sun Ultra server
hardware/OS):

Solaris 7 (64-bit kernel)
Oracle 8.1.7/RMAN (32-bit)
TSM Server  4.1.2
(new)TSM 4.1.2.12 BA Client (64-bit)
(new)TSM 4.1.2.12 API (64-bit)
(new)TDP Oracle 2.1.10 (32-bit)

We're trying to test RMAN with TDP-Oracle, but are having problems getting
Oracle/RMAN to interact with the TDP-Oracle 2.1.10 (32-bit) Media
Management Library 'libobk.so'.  RMAN fails to recognize 'SBT_TAPE'.

Both Oracle and ADSM-L have posted problem reports on this issue which
identified some Solaris OS patches.  However, all of those patches are
installed and we are still having problems.  These Solaris OS patches are
installed:  106300 106327 106980 106541 107544.  One other mentioned patch 109104 has 
been superseded & is not
installed.  There's a chance that 106980-07 is down-rev vs postings.

Our Oracle admin advised me to install the 32-bit 'libobk.so' library for
compatibility.  I might suspect 32-bit/64-bit compatibility issues, but
'aobpswd' runs successfully, opening a TSM Server (v4.1.2) session of type
'TDP Oracle SUN'.   Isn't that sufficient proof that the TDP-Oracle
library and the TSM API configuration are functioning properly together?
 If so, where does the problem (more importantly the resolution) lie?

If you can help me resolve this, rsvp.thanks

Kent Monthei
GlaxoSmithKline

Re: Testing A WIN2k Server restore

[Brown, Bud]

Have you viewed the articles Q139822 for NT and Q249694 for W2K?

Bud Brown
Information Services
Systems Administrator
303-436-5986


-Original Message-
From: Joe Cascanette [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 8:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing A WIN2k Server restore


What happens when the hardware is different then the server restoring.
Has anyone run into this?. I have playing with the Win2000 registry to
find all the hardware items (so I can delete the key after restoring the
registry and add the hardware key for the server we are using), but
still no luck. Is there any other area I need to look at?

Thanks

Joe Cacsanette
The Cumis Group Limited



-Original Message-
From: John Naylor [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 8:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing A WIN2k Server restore


When you register the test box to TSM you can give whatever name you
like
ie testbox
For recovery purposes, what you can do is change the nodename in the
dsm.opt
file on your test
machine from "testbox" to the same name as the machine you are
recovering from.
Then you will be able to recover to the testbox.
You will not be able to do any backups/restores on your production
server while
your test in in progress.






"Amini, Mehdi" <[EMAIL PROTECTED]> on 02/08/2002 01:16:21 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Testing A WIN2k Server restore



Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the
same
as the one I am trying to recover.  My problem is that the recovering
Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is
in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at
the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**








**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Re: Testing A WIN2k Server restore

[Brown, Bud]

Microsoft has an article Q249694, but they put a disclaimor in it that
it is not supported.

Bud Brown
Information Services
Systems Administrator
303-436-5986


-Original Message-
From: Ilja G. Coolen [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 8:35 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing A WIN2k Server restore


Joe,

We ran into this before.
To start of with an important notice. Microsoft does not support this,
and
claims it is not possible to restore to different hardware.
Having that said, i also want to mention that we do a periodical test at
a
disaster recovery site. At this site we do not have identical hardware,
if
possible at all.

Note:
When restoring on a server using a separate partition or install
directory,
copy the boot.ini so you can edit it after the restore, making it
matching
for the installed OS and the restored one. If the restored OS does not
boot,
you can select the recovery OS in the boot.ini to boot to the recovery
OS
and try some more actions.

One option is:
Find out witch dll's represent the drivers for the installed hardware on
the
recovery machine. The one you installed the restore OS on.
Restore the entire OS using a separate install directory or partition.
Select the driver-dll's and overwrite the restored ones in the restored
OS.
Mostly these are drivers for the diskarray's.
Try to use somewhat similar NIC's when doing this.
This seems simple, but will be quite a hassle if it turns out to be the
wrong driver. Our NT-admins tried this, and had it working in several
occasions. THIS IS VERY HARDWARE DEPENDANT!

The other option is:
At our DR site this is the prefered method.
Again, install a recovery OS on a separate partion, or in a separate
directory.
Restore the entire OS. Preserve the installed boot.ini.
Reboot after the restore, but make sure it boots in setup mode, with the
NT
setup CD-rom in the drive. Select and perform the upgrade option in the
setup menu. To get the upgrade option, the boot.ini should be at its
original location, so i'm told.
After the upgrade you can reboot, and run your prefered SP update.
THIS IS LESS HARDWARE DEPENDANT!

The second option is more work, but proved to be the more reliable one.
Again, it is not supported by anyone.

I hope your business continuity does not rely on this.
GOOD LUCK.


Ilja G. Coolen


  _

ABP / USZO
CIS / BS / TB / Storage Management
Telefoon : +31(0)45  579 7938
Fax  : +31(0)45  579 3990
Email: [EMAIL PROTECTED] 
Intranet
: Storage Web


  _

- Everybody has a photographic memory, some just don't have film. -


-Oorspronkelijk bericht-
Van: Joe Cascanette [mailto:[EMAIL PROTECTED]]
Verzonden: vrijdag 8 februari 2002 16:13
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Testing A WIN2k Server restore


What happens when the hardware is different then the server restoring.
Has
anyone run into this?. I have playing with the Win2000 registry to find
all
the hardware items (so I can delete the key after restoring the registry
and
add the hardware key for the server we are using), but still no luck. Is
there any other area I need to look at?

Thanks

Joe Cacsanette
The Cumis Group Limited



-Original Message-
From: John Naylor [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 8:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing A WIN2k Server restore


When you register the test box to TSM you can give whatever name you
like
ie testbox
For recovery purposes, what you can do is change the nodename in the
dsm.opt
file on your test
machine from "testbox" to the same name as the machine you are
recovering
from.
Then you will be able to recover to the testbox.
You will not be able to do any backups/restores on your production
server
while
your test in in progress.






"Amini, Mehdi" <[EMAIL PROTECTED]> on 02/08/2002 01:16:21 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Testing A WIN2k Server restore



Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the
same
as the one I am trying to recover.  My problem is that the recovering
Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is
in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at
the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




***

Re: Testing A WIN2k Server restore

[Joe Cascanette]

What happens when the hardware is different then the server restoring. Has anyone run 
into this?. I have playing with the Win2000 registry to find all the hardware items 
(so I can delete the key after restoring the registry and add the hardware key for the 
server we are using), but still no luck. Is there any other area I need to look at?

Thanks

Joe Cacsanette
The Cumis Group Limited



-Original Message-
From: John Naylor [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 8:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing A WIN2k Server restore


When you register the test box to TSM you can give whatever name you like
ie testbox
For recovery purposes, what you can do is change the nodename in the dsm.opt
file on your test
machine from "testbox" to the same name as the machine you are recovering from.
Then you will be able to recover to the testbox.
You will not be able to do any backups/restores on your production server while
your test in in progress.






"Amini, Mehdi" <[EMAIL PROTECTED]> on 02/08/2002 01:16:21 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Testing A WIN2k Server restore



Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**








**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Re: size of individual database/log files for TSM

[Prather, Wanda]

There is no absolute "right" answer to your question, except "it depends on
your environment".

We are also TSM 4.1.3 on AIX 4.3.3.  There is no size limit I know of to the
files that TSM uses for DB, log, and storage pool volumes; you can make them
larger than 2 GB.  However, the JFS filesystem where you are defining the
files must have the "large file enabled" attribute, otherwise AIX will not
let you create a file larger than 2 GB.

The number of files you use for the DB is mostly a performance/throughput
issue.  TSM will start multiple I/O's to your DB (and storage pool) volumes.
So it is better to have multiple files than one big file, so TSM can do
multiple operations in parallel.

However, if you have MANY files, and they are all on the same PHYSICAL disk
volumes, eventually you will actually SLOW DOWN performance because you are
causing contention at the physical device level trying to do too many I/Os
to a single device.

So I try to think of it in terms of "how many concurrent operations do I
want to occur on that device?".   But even that issue gets fuzzy if you are
using high-end RAID with CACHE in the controller, as much of the I/O becomes
asynchronous and is done to cache instead of being dependent on the physical
device rotation any more.  So, "it depends" on your environment.

For example:
One of my TSM servers has about 400 clients, it is VERY busy and does
enormous amounts of I/O; I try to watch AIX iostat sometimes and just see
how much I/O is occuring to each of my physical drives, and how much time
TSM is spending on I/O wait, and I think in those terms when I'm putting new
TSM volumes in use.

My other TSM server is NOT a very busy server, and backup throughput is just
not an issue.  On that system, I don't think twice about where I put the
files, or how many - it just doesn't matter!

Hope that helps provide some perspective...


Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert









-Original Message-
From: Yahya Ilyas [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 8:05 PM
To: [EMAIL PROTECTED]
Subject: size of individual database/log files for TSM


Hi
We are using TSM server Version 4, Release 1, Level 3.0 on AIX 4.3.3
I added another 35 GB disk to the server, and want to increase database and
log size for TSM by defining new dbv and logv volumes.  Currently all the
.dsm files for database and log are 2 GB each.  I wanted to know if I should
create files larger than 2 GB, is there a size limit to these files?  Also
having 12 - 15  files of 2 GB each is better or fewer larger size files for
database and log.
Thanks

>   -
>   Yahya Ilyas
>   Systems Programmer Sr
>   Systems Integration & Management
>   Information Technology
>   Arizona State University, Tempe, AZ 85287-0101
>
>   [EMAIL PROTECTED]
>   Phone: (480) 965-4467
>
>

Re: restoring backupsets

[Jeff Bach]

What was the Novell Client configuration?  How about a little server
information?

I would like Novell to get  3 Meg per second on restores.  10 Gigs per hour,
but they currently bite.

Jeff

> -Original Message-
> From: John Naylor [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, February 08, 2002 4:11 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: restoring backupsets
>
> Switch on perform tracing on the client.
> This will break down where the time is being spent, so you can identify
> your
> bottleneck
> I was seeing circa 3 mb. sec restoring a netware client from 9840 across a
> network
> With a directly attached tape and an  AIX client you ought to get better.
> John
>
>
>
>
>
> John Bremer <[EMAIL PROTECTED]> on 02/07/2002 11:07:01 PM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> To:   [EMAIL PROTECTED]
> cc:(bcc: John Naylor/HAV/SSE)
> Subject:  restoring backupsets
>
>
>
> *SMers,
>
> We're trying to restore a backupset from 9840 media.  Our tape drive is
> attached to an AIX client and we are seeing only 1-2 MB/sec data transfer
> rates.
>
> Is there a reason why we don't see tape and/or disk speeds on this
> restore?  The disk should run at 14-15 MB/sec and the SCSI 9840 at 10
> MB/sec.
>
> THanks.  John Bremer
>
>
>
>
>
>
>
>
> **
> The information in this E-Mail is confidential and may be legally
> privileged. It may not represent the views of Scottish and Southern
> Energy plc.
> It is intended solely for the addressees. Access to this E-Mail by
> anyone else is unauthorised. If you are not the intended recipient,
> any disclosure, copying, distribution or any action taken or omitted
> to be taken in reliance on it, is prohibited and may be unlawful.
> Any unauthorised recipient should advise the sender immediately of
> the error in transmission.
>
> Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
> are trading names of the Scottish and Southern Energy Group.
> **


**
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**

Re: 3494 through SAN Data Gateway

[Loon, E.J. van - SPLXM]

Hi Arnaud!
You are absolutely right! I removed the drives, the library and the fscsi
devices trough SMIT and I issued the disableCC command. After the SAN DG
reboot I ran cfgmgr and it redetected the drives and library without the
missing fileset error!
Thank you VERY much!!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: PAC Brion Arnaud [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 17:02
To: [EMAIL PROTECTED]
Subject: Re: 3494 through SAN Data Gateway


Hi again,

OK, you checked SetHost, but did you issue the DisableCC command and
reboot you SDG ? I found an old install doc I made during our install,
and am positively sure it's the reason of your problem !

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01   |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-Original Message-
From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 07 February, 2002 16:43
To: [EMAIL PROTECTED]
Subject: Re: 3494 through SAN Data Gateway


Hi Arnaud!
I have issued the setHost 0,"aix" before installing the SAN Data
Gateway. I checked the Fibre Channel settings through the IBM StorWatch
SAN Data Gateway Specialist: The host type is set to AIX, so that
shouldn't be the cause... Kindest regards, Eric van Loon KLM Royal Dutch
Airlines


-Original Message-
From: PAC Brion Arnaud [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 16:07
To: [EMAIL PROTECTED]
Subject: Re: 3494 through SAN Data Gateway


Hi Mr Loon,

I could be false, be I believe I remember we had the same problem, until
we updated values in the SDG, as said before :
1) disableCC
2) setHost 0, "aix"   or   setHost  0  AIX
3) setHost 1, "aix"   or   setHost  1  AIX
4) and reboot the device.
5) remove the tape drives (rmdev -dl rmt?), the fiber object (rmdev -Rdl
fcs?), and then rerun cfgmgr.



=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01   |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-Original Message-
From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 07 February, 2002 15:57
To: [EMAIL PROTECTED]
Subject: Re: 3494 through SAN Data Gateway


Hi *SM-ers!
My 3590 drives are working through the SAN Data Gateway now. The problem
wasn't related to the missing device package message, but it was a wrong
SCSI cable (one without a terminator). However, I still receive the
following message when running cfgmgr:

cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed. devices.fcp.array

I checked the AIX 4.3.3. CD, but it's not part of AIX. Could someone who
is using a SAN Data Gateway check if he/she has this fileset installed?
Maybe it is part of another fileset? I can't find anything about it, not
through IBM nor though Google. Thanks in advance! Kindest regards, Eric
van Loon KLM Royal Dutch Airlines


-Original Message-
From: Othonas Xixis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 19:47
To: [EMAIL PROTECTED]
Subject: Re: 3494 through SAN Data Gateway


Eric,
in case Adolph's recommendation don't work, or cfgmgr gives you another
error then the problem is with your 2108 SAN Data Gateway (SDG). Go into
the SDG (SAN Data Gateway) firmware and execute the following actions:
1) disableCC
2) setHost 0, "aix"   or   setHost  0  AIX
3) setHost 1, "aix"   or   setHost  1  AIX
4) and reboot the device.
5) remove the tape drives (rmdev -dl rmt?), the fiber object (rmdev -Rdl
fcs?), and then rerun cfgmgr. This action should let see the SDG
transparent to the cfgmgr routine.

Cheers.

Othonas Xixis



"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on
02/05/2002 01:00:33 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:Re: 3494 through SAN Data Gateway



Hi Adolph!
Thank you very much! I will install it tomorrow.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: Adolph Kahan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 18:54
To: [EMAIL PROTECTED]
Subject: Re: 3494 through SAN Data Gateway


This is part of AIX. It will be on the AIX install CDs.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Loon, E.J. van - SPLXM
Sent: Tuesday, February 05, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: 3494 through SAN Data Gateway

Hi *SM-ers!
I have just connected a 3494 library through a SAN Data Gateway. When I
run cfgmgr is detects the drives:

rmt5  Av

Re: Richard Sims..NOT retired...de-listed!

[Lisa Cabanas]

He hasn't retired.  Has he been de-listed???

Inquiring minds want to know


lisa


- Forwarded by Lisa Cabanas/SC/MODOT on 02/08/2002 09:28 AM -
|+>
||  [EMAIL PROTECTED]|
|||
||  02/08/2002|
||  08:21 AM  |
|||
|+>
  >|
  ||
  |  To: Lisa Cabanas/SC/MODOT@MODOT, [EMAIL PROTECTED]   |
  |  cc:   |
  |  Subject: Re: HOWTO: TSM Server Quickinst  |
  >|





>Speaking of you, you haven't been on the list for a long time.
>
>Richard, did you retire?  Or, did you just get bored of always answering the
>same questions?

Hello, Lisa -

Good to hear from another ADSMer...

I'm still here doing the same stuff.  The problem is that the ADSM-L list
won't let me participate.  :-(   Some months ago the regular flow of list
postings to me sputtered and then stopped.  I tried various listserv commands
to list things and adjust my subscription, but nothing yielded a response.
I send email to the list administrator, and that got no response.  So I'm
in limbo.  Without the regular flow of postings, meaningful participation in
the list is moot.  So in a sense I'm in forced retirement.  At my age!  :-)

In amidst all the other things I have to do, I'm making periodic stabs at
determining what is going on with ADSM-L Listserv, but it's working in the
dark, remotely.

I hope things are going well with you, and the List.

   Frustrated in Boston,

 Richard

- Forwarded by Lisa Cabanas/SC/MODOT on 02/08/2002 09:29 AM -
|+>
||  [EMAIL PROTECTED]|
|||
||  02/08/2002|
||  09:05 AM  |
|||
|+>
  >|
  ||
  |  To: Lisa Cabanas/SC/MODOT@MODOT, [EMAIL PROTECTED]   |
  |  cc:   |
  |  Subject: Re:  Richard Sims.. (was HOWTO: TSM Server Quickinst |
  >|





>Since I am not the only one who has missed you, can I share your situation with
>the list, and see if that helps get you back on !!

Lisa - I'm flattered.  Sure, give it a try.
   If nothing else, people can vote on whether
to let me back in.  ;-)

  thanks, Richard



|+>
||  Jim Kirkman   |
||  <[EMAIL PROTECTED]|
||  .EDU> |
|||
||  02/08/2002|
||  08:00 AM  |
||  Please respond|
||  to jim_kirkman|
|||
|+>
  >|
  ||
  |  To: [EMAIL PROTECTED]  |
  |  cc: (bcc: Lisa Cabanas/SC/MODOT)  |
  |  Subject: Richard Sims.. (was HOWTO: TSM Server Quickinst  |
  >|





Does anyone know what's happened to Richard? Hopefully something good,
like retirement!

I miss his informative posts.

John Naylor wrote:

> There is also Richard Sim's Functional ADSM Guide at
> http://people.bu.edu/rbs/
> Well worth a visit.
>
> **
> The information in this E-Mail is confidential and may be legally
> privileged. It may not represent the views of Scottish and Southern
> Energy plc.
> It is intended solely for the addressees. Access to this E-Mail by
> anyone else is unauthorised. If you are not the intended recipient,
> any disclosure, copying, distribution or any action taken or omitted
> to be taken in reliance on it, is prohibited and may be unlawful.
> Any unauthorised recipient should advise the sender immediately of
> the error in transmission.
>
> Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
> are trading names of the Scottish and Southern Energy Group.
> **

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hi

TDP Oracle 2.1.10 'libobk.so' problems on Oracle 8.1.7 / Solaris 2.7

[Neil Rasmussen]

Kent,

The first real obvious thing that I see is the TSM API Architecture. If
you are running 32bit TDP for Oracle then you TSM API needs to be 32bit.
However, when you run the aobpswd it uses the TSM API to comunicate with
the TSM Server to manage passwords so this indicates that they are both
the same architecture. In short, you need to go back and make sure that
Oracle and TDP for Oracle and the TSM API are all the same archetecture.
The next step is to ensure that your soft links are in order for
libobk.so. The link should look like the following:

   $ORACLE_HOME/lib/libobk.so -> /usr/lib/libobk.so
   /usr/lib/libobk.so -> /opt/tivoli/tsm/client/oracle/bin/libobk.so

If the is correct and you verify that Rman is still is not using TDP for
Oracle you might want to try running Oracle's linking process.

- Shut down all Oracle instances that use $ORACLE_HOME
- Go to the $ORACLE_HOME/lib directory. If the libobk.so file exists in
this directory, remove it.
- Go to the $ORACLE_HOME/rdbms/lib directory.
- Enter the following command to relink RMAN with TDP for Oracle:
   $ make -f ins_rdbms.mk LLIBMM=/usr/lib/libobk.so ioracle

- Verify that the relinking process has completed.


Even though the above step is not supposed to be necessary, we have found
that this works sometimes for us.


--

Date:Thu, 7 Feb 2002 12:24:14 -0500
From:Kent Monthei <[EMAIL PROTECTED]>
Subject: TDP Oracle 2.1.10 'libobk.so' problems on Oracle 8.1.7 / Solaris
2.7

We have the following configuration (all on same Sun Ultra server
hardware/OS):

Solaris 7 (64-bit kernel)
Oracle 8.1.7/RMAN (32-bit)
TSM Server  4.1.2
(new)   TSM 4.1.2.12 BA Client (64-bit)
(new)   TSM 4.1.2.12 API (64-bit)
(new)   TDP Oracle 2.1.10 (32-bit)

We're trying to test RMAN with TDP-Oracle, but are having problems getting
Oracle/RMAN to interact with the TDP-Oracle 2.1.10 (32-bit) Media
Management Library 'libobk.so'.  RMAN fails to recognize 'SBT_TAPE'.

Both Oracle and ADSM-L have posted problem reports on this issue which
identified some Solaris OS patches.  However, all of those patches are
installed and we are still having problems.  These Solaris OS patches are
installed:  106300 106327 106980 106541 107544.  One other mentioned patch
109104 has been superseded & is not
installed.  There's a chance that 106980-07 is down-rev vs postings.

Our Oracle admin advised me to install the 32-bit 'libobk.so' library for
compatibility.  I might suspect 32-bit/64-bit compatibility issues, but
'aobpswd' runs successfully, opening a TSM Server (v4.1.2) session of type
'TDP Oracle SUN'.   Isn't that sufficient proof that the TDP-Oracle
library and the TSM API configuration are functioning properly together?
If so, where does the problem (more importantly the resolution) lie?

If you can help me resolve this, rsvp.thanks

Kent Monthei
GlaxoSmithKline


Regards,

Neil Rasmussen
Software Development
TDP for Oracle
[EMAIL PROTECTED]

Re: Testing A WIN2k Server restore

[Amini, Mehdi]

If I fool the server by changing the registry as you say, and start the GUI
(from the test server)to restore the System Objects, will I get prompted on
where I want to restore it to and if not, to which system (the true server
or the recovery server) will it restore the objects?


Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879



-Original Message-
From: Adams, Matt (US - Hermitage) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 8:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing A WIN2k Server restore


You could name your test(recovery) server to something different than your
production server.
Once it comes back up, you can go into the registry and find the
"ComputerName" registry key located in:
"HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ComputerName\ActiveComputer
Name"   to the production server name.  Don't reboot.  This will fool TSM
enough to do the restore.  Now... all that being said, you are reducing the
chance of a successful restore.  I wouldn't recommend it for an actual
recovery, but it will work to do a test restore.

Best thing to do is to get the application owner on board with the testing
and explain its importance of a successful recovery of his/her application.
This might allow you to test recovery on the actual box.  Or have a second
box similar in function that is only a testing box that can be brought
offline for the recovery testing.

Just some thoughts..

Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte & Touche USA LLP
615.882.6861



-Original Message-
From: Amini, Mehdi [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 7:16 AM
To: [EMAIL PROTECTED]
Subject: Testing A WIN2k Server restore


Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**
- This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.

Re: Testing A WIN2k Server restore

[John Naylor]

When you register the test box to TSM you can give whatever name you like
ie testbox
For recovery purposes, what you can do is change the nodename in the dsm.opt
file on your test
machine from "testbox" to the same name as the machine you are recovering from.
Then you will be able to recover to the testbox.
You will not be able to do any backups/restores on your production server while
your test in in progress.






"Amini, Mehdi" <[EMAIL PROTECTED]> on 02/08/2002 01:16:21 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Testing A WIN2k Server restore



Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**








**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Richard Sims.. (was HOWTO: TSM Server Quickinst

[Jim Kirkman]

Does anyone know what's happened to Richard? Hopefully something good,
like retirement!

I miss his informative posts.

John Naylor wrote:

> There is also Richard Sim's Functional ADSM Guide at
> http://people.bu.edu/rbs/
> Well worth a visit.
>
> **
> The information in this E-Mail is confidential and may be legally
> privileged. It may not represent the views of Scottish and Southern
> Energy plc.
> It is intended solely for the addressees. Access to this E-Mail by
> anyone else is unauthorised. If you are not the intended recipient,
> any disclosure, copying, distribution or any action taken or omitted
> to be taken in reliance on it, is prohibited and may be unlawful.
> Any unauthorised recipient should advise the sender immediately of
> the error in transmission.
>
> Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
> are trading names of the Scottish and Southern Energy Group.
> **

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884

Re: 3494 through SAN Data Gateway

[Fred Johanson]

Eric,

My AIX guy agrees with Arnaud.  You didn't say whether you'd run his
step1.  That may be the key.  Certainly worked for us.


At 04:43 PM 2/7/2002 +0100, you wrote:
>Hi Arnaud!
>I have issued the setHost 0,"aix" before installing the SAN Data Gateway. I
>checked the Fibre Channel settings through the IBM StorWatch SAN Data
>Gateway Specialist: The host type is set to AIX, so that shouldn't be the
>cause...
>Kindest regards,
>Eric van Loon
>KLM Royal Dutch Airlines
>
>
>-Original Message-
>From: PAC Brion Arnaud [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, February 07, 2002 16:07
>To: [EMAIL PROTECTED]
>Subject: Re: 3494 through SAN Data Gateway
>
>
>Hi Mr Loon,
>
>I could be false, be I believe I remember we had the same problem, until
>we updated values in the SDG, as said before :
>1) disableCC
>2) setHost 0, "aix"   or   setHost  0  AIX
>3) setHost 1, "aix"   or   setHost  1  AIX
>4) and reboot the device.
>5) remove the tape drives (rmdev -dl rmt?), the fiber object (rmdev -Rdl
>fcs?), and then rerun cfgmgr.
>
>
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>| Arnaud Brion, Panalpina Management Ltd., IT Group |
>| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
>| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01   |
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
>
>-Original Message-
>From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, 07 February, 2002 15:57
>To: [EMAIL PROTECTED]
>Subject: Re: 3494 through SAN Data Gateway
>
>
>Hi *SM-ers!
>My 3590 drives are working through the SAN Data Gateway now. The problem
>wasn't related to the missing device package message, but it was a wrong
>SCSI cable (one without a terminator). However, I still receive the
>following message when running cfgmgr:
>
>cfgmgr: 0514-621 WARNING: The following device packages are required for
>device support but are not currently installed. devices.fcp.array
>
>I checked the AIX 4.3.3. CD, but it's not part of AIX. Could someone who
>is using a SAN Data Gateway check if he/she has this fileset installed?
>Maybe it is part of another fileset? I can't find anything about it, not
>through IBM nor though Google. Thanks in advance! Kindest regards, Eric
>van Loon KLM Royal Dutch Airlines
>
>
>-Original Message-
>From: Othonas Xixis [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, February 05, 2002 19:47
>To: [EMAIL PROTECTED]
>Subject: Re: 3494 through SAN Data Gateway
>
>
>Eric,
>in case Adolph's recommendation don't work, or cfgmgr gives you another
>error then the problem is with your 2108 SAN Data Gateway (SDG). Go into
>the SDG (SAN Data Gateway) firmware and execute the following actions:
>1) disableCC
>2) setHost 0, "aix"   or   setHost  0  AIX
>3) setHost 1, "aix"   or   setHost  1  AIX
>4) and reboot the device.
>5) remove the tape drives (rmdev -dl rmt?), the fiber object (rmdev -Rdl
>fcs?), and then rerun cfgmgr. This action should let see the SDG
>transparent to the cfgmgr routine.
>
>Cheers.
>
>Othonas Xixis
>
>
>
>"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on
>02/05/2002 01:00:33 PM
>
>Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
>Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
>
>To:[EMAIL PROTECTED]
>cc:
>Subject:Re: 3494 through SAN Data Gateway
>
>
>
>Hi Adolph!
>Thank you very much! I will install it tomorrow.
>Kindest regards,
>Eric van Loon
>KLM Royal Dutch Airlines
>
>
>-Original Message-
>From: Adolph Kahan [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, February 05, 2002 18:54
>To: [EMAIL PROTECTED]
>Subject: Re: 3494 through SAN Data Gateway
>
>
>This is part of AIX. It will be on the AIX install CDs.
>
>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
>Loon, E.J. van - SPLXM
>Sent: Tuesday, February 05, 2002 12:41 PM
>To: [EMAIL PROTECTED]
>Subject: 3494 through SAN Data Gateway
>
>Hi *SM-ers!
>I have just connected a 3494 library through a SAN Data Gateway. When I
>run cfgmgr is detects the drives:
>
>rmt5  Available 10-68-01 IBM 3590 Tape Drive and Medium Changer
>(FCP)
>rmt6  Available 10-68-01-4,0 IBM 3590 Tape Drive and Medium Changer
>(FCP)
>
>But it also returns the following error:
>
>cfgmgr: 0514-621 WARNING: The following device packages are required for
>device support but are not currently installed. devices.fcp.array
>
>This driver, is it a AIX driver or is it part of the TSM devices
>package? Thanks in advance!! Kindest regards, Eric van Loon KLM Royal
>Dutch Airlines
>
>
>**
>For information, services and offers, please visit our web site:
>http://www.klm.com. This e-mail and any attachment may contain
>confidential and privileged material intended for the addressee only. If
>you are not the addressee, you are notified that no part of the e-mail
>or any attachment may be disclosed, copied or distributed, and that any
>othe

Re: Richard Sims..NOT retired...de-listed!

[Henk ten Have]

On 08-Feb-02 Lisa Cabanas wrote:
> He hasn't retired.  Has he been de-listed???
>
> Inquiring minds want to know


Date: Fri, 8 Feb 2002 10:09:46 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re:  FW: Richard Sims.. (was HOWTO: TSM Server Quickinst

>I'm not the only person on the list who niticed this!
>Still having problems gettting on the list?

Gosh... I'm missed!  It was worth getting up this morning!  :-)

I've kept trying various things to prod the listserver, but it still
won't send me a reply.  Lisa also emailed me asking where I've been.
She may post an explanation.  I joked that, if nothing else, people
can vote on whether to let me back in.  ;-)

  We'll see what happens,


Well, my question is: "What will happen?"

Cheers,
Henk.

Re: LTO strange behaviour

[James Thompson]

What you really need to find out is how fast are you sending data to the LTO
tape drives.  The tape drives can only go as fast as the data stream you
send to them.  Or as fast as the destination can accept on a restore.  If
you are only sending 2.5 MB/sec to the tape drives, then don't complain when
the tape drives run at 2.5 MB/sec.

You state that you are doing a backup.  What size and how many files are you
sending.  If this is a LAN backup, how much bandwidth does your TSM server's
network have?  If this is a backup from the TSM server's local storage, what
type is it?

If you have lots of small files, or your are bandwidth limited because of
your network.  You should send the backup to disk storage, then migrate off
to tape.

Check the following settings and try setting them to these values.

TSM Server:

TXNGroupmax 256
MOVESizethresh 500
MOVEBatchsize 1000

TSM Client:

TXNBytelimit 2097152

Also upgrade to the latest level of microcode.  And if all else fails,  open
a support call with IBM and have them assist you.

James Thompson

_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx

Re: Richard Sims.. (was HOWTO: TSM Server Quickinst

[Henk ten Have]

On 08-Feb-02 Jim Kirkman wrote:
> Does anyone know what's happened to Richard? Hopefully something good,
> like retirement!

  I emailed him a month ago and asked him where he was / what he was
  doing. Still the same he told me, but he had problems reaching this
  list (I think for at least 5 month now).

> I miss his informative posts.

  We all do.

  Cheers,
  Henk.

Re: Testing A WIN2k Server restore

[Adams, Matt (US - Hermitage)]

One thing I neglected to add..(important however)

Once the restore is complete and you reboot, then you will attempt to have
two servers on the network with same name and SID...not a good thing.  You
really need to convince the application/server owner to allow you to bring
it offline temporarily by disconnecting the network cable at the recover
server reboot time to avoid this.  Then check the success of the recovery.

Again, stress the importance of testing... you don't want to trouble shoot..
and they will not want to wait if a real recovery needs to take place and
you are working out the kinks... And trust me... there will be kinks.

Matt


-Original Message-
From: Adams, Matt (US - Hermitage)
Sent: Friday, February 08, 2002 7:44 AM
To: 'ADSM: Dist Stor Manager'
Subject: RE: Testing A WIN2k Server restore


You could name your test(recovery) server to something different than your
production server.
Once it comes back up, you can go into the registry and find the
"ComputerName" registry key located in:
"HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ComputerName\ActiveComputer
Name"   to the production server name.  Don't reboot.  This will fool TSM
enough to do the restore.  Now... all that being said, you are reducing the
chance of a successful restore.  I wouldn't recommend it for an actual
recovery, but it will work to do a test restore.

Best thing to do is to get the application owner on board with the testing
and explain its importance of a successful recovery of his/her application.
This might allow you to test recovery on the actual box.  Or have a second
box similar in function that is only a testing box that can be brought
offline for the recovery testing.

Just some thoughts..

Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte & Touche USA LLP
615.882.6861



-Original Message-
From: Amini, Mehdi [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 7:16 AM
To: [EMAIL PROTECTED]
Subject: Testing A WIN2k Server restore


Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**
- This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.

Re: Testing A WIN2k Server restore

[Ilja G. Coolen]

Joe,

We ran into this before.
To start of with an important notice. Microsoft does not support this, and
claims it is not possible to restore to different hardware.
Having that said, i also want to mention that we do a periodical test at a
disaster recovery site. At this site we do not have identical hardware, if
possible at all.

Note:
When restoring on a server using a separate partition or install directory,
copy the boot.ini so you can edit it after the restore, making it matching
for the installed OS and the restored one. If the restored OS does not boot,
you can select the recovery OS in the boot.ini to boot to the recovery OS
and try some more actions.

One option is:
Find out witch dll's represent the drivers for the installed hardware on the
recovery machine. The one you installed the restore OS on.
Restore the entire OS using a separate install directory or partition.
Select the driver-dll's and overwrite the restored ones in the restored OS.
Mostly these are drivers for the diskarray's.
Try to use somewhat similar NIC's when doing this.
This seems simple, but will be quite a hassle if it turns out to be the
wrong driver. Our NT-admins tried this, and had it working in several
occasions. THIS IS VERY HARDWARE DEPENDANT!

The other option is:
At our DR site this is the prefered method.
Again, install a recovery OS on a separate partion, or in a separate
directory.
Restore the entire OS. Preserve the installed boot.ini.
Reboot after the restore, but make sure it boots in setup mode, with the NT
setup CD-rom in the drive. Select and perform the upgrade option in the
setup menu. To get the upgrade option, the boot.ini should be at its
original location, so i'm told.
After the upgrade you can reboot, and run your prefered SP update.
THIS IS LESS HARDWARE DEPENDANT!

The second option is more work, but proved to be the more reliable one.
Again, it is not supported by anyone.

I hope your business continuity does not rely on this.
GOOD LUCK.


Ilja G. Coolen


  _

ABP / USZO
CIS / BS / TB / Storage Management
Telefoon : +31(0)45  579 7938
Fax  : +31(0)45  579 3990
Email: [EMAIL PROTECTED] 
Intranet
: Storage Web


  _

- Everybody has a photographic memory, some just don't have film. -


-Oorspronkelijk bericht-
Van: Joe Cascanette [mailto:[EMAIL PROTECTED]]
Verzonden: vrijdag 8 februari 2002 16:13
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Testing A WIN2k Server restore


What happens when the hardware is different then the server restoring. Has
anyone run into this?. I have playing with the Win2000 registry to find all
the hardware items (so I can delete the key after restoring the registry and
add the hardware key for the server we are using), but still no luck. Is
there any other area I need to look at?

Thanks

Joe Cacsanette
The Cumis Group Limited



-Original Message-
From: John Naylor [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 8:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing A WIN2k Server restore


When you register the test box to TSM you can give whatever name you like
ie testbox
For recovery purposes, what you can do is change the nodename in the dsm.opt
file on your test
machine from "testbox" to the same name as the machine you are recovering
from.
Then you will be able to recover to the testbox.
You will not be able to do any backups/restores on your production server
while
your test in in progress.






"Amini, Mehdi" <[EMAIL PROTECTED]> on 02/08/2002 01:16:21 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Testing A WIN2k Server restore



Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


***

Re: Testing A WIN2k Server restore

[Remeta, Mark]

Put the test server on it's own network. Install second nic card in tsm
server and use it to connect to the test server...

Mark


-Original Message-
From: Amini, Mehdi [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 8:16 AM
To: [EMAIL PROTECTED]
Subject: Testing A WIN2k Server restore


Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: Testing A WIN2k Server restore

[MORGAN TONY]

Hi Mehdi,

What are you trying to restore... is it just files, or is it a TDP process?

You have to be aware that the nodename in you dsm.opt file can be anything,
as long as it is registered on the Tivoli server. If you are restoring
Exchange you need to set up a VLAN, its probably the same for other TDP's.

If its just files...  Change the nodename parameter in DSM.OPT and then
reset the password using DSMC. From the web interface you can then do a
restore as the original server.
Don't use "restore to original location" - It will get confused!!  Always
set a directory for the restore and (it should be neccessary) move the files
later.

When you have finished.  I find it best to reset the client passwords on the
clients and the server... just to be sure!! (I use password generate)

The process seems scary first time you do it, but it really is simple!!!

Good Luck

Tony


-Original Message-
From: Amini, Mehdi [mailto:[EMAIL PROTECTED]]
Sent: 08 February 2002 13:16
To: [EMAIL PROTECTED]
Subject: Testing A WIN2k Server restore


Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**



This e-mail and any files transmitted with it, are confidential and
intended solely for the use of the addressee. The content of this
e-mail may have been changed without the consent of the originator.
The information supplied must be viewed in this context. If you have
received this e-mail in error please notify our Helpdesk by
telephone on +44 (0) 20-7444-8444. Any use, dissemination,
forwarding, printing, or copying of this e-mail or its attachments is
strictly prohibited.

Re: Testing A WIN2k Server restore

[Ilja G. Coolen]

Mehdi,

Usually the redbooks give a great representation of reality, but like you
discovered yourself, Microsoft disagrees on some things.
It is not required that give the recovery server the same name, as long as
you specify the proper servername when restoring. We do it like this almost
all the time. You have to be carefull with restoring a server while the
originating server is still live. Make sure you unplug the network-cable
after the restore, but before the boot sequence is initiated when you do a
reboot. You will have duplicate servers and duplicate ip addresses on the
network if you don't. When rebooted, rename the server and change the IP
address if applicable, and plug the network. Now you should have a clone of
the originating server, but using a different servername.

The problem with giving the recovery server the same name is even worse if
you decide to put it in the same nt-domain. You have to remove the computer
entry from the domain, after the restore is complete, and re-join the domain
after the reboot, resulting in an additional reboot. This is because the SID
of the recovery computer will be different that the original SID of the
originating server. This of course is not smart if the original server is
still live.


Ilja G. Coolen


  _

ABP / USZO
CIS / BS / TB / Storage Management
Telefoon : +31(0)45  579 7938
Fax  : +31(0)45  579 3990
Email: [EMAIL PROTECTED] 
Intranet
: Storage Web


  _

- Everybody has a photographic memory, some just don't have film. -


-Oorspronkelijk bericht-
Van: Amini, Mehdi [mailto:[EMAIL PROTECTED]]
Verzonden: vrijdag 8 februari 2002 14:16
Aan: [EMAIL PROTECTED]
Onderwerp: Testing A WIN2k Server restore


Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**

Re: Testing A WIN2k Server restore

[Adams, Matt (US - Hermitage)]

You could name your test(recovery) server to something different than your
production server.
Once it comes back up, you can go into the registry and find the
"ComputerName" registry key located in:
"HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ComputerName\ActiveComputer
Name"   to the production server name.  Don't reboot.  This will fool TSM
enough to do the restore.  Now... all that being said, you are reducing the
chance of a successful restore.  I wouldn't recommend it for an actual
recovery, but it will work to do a test restore.

Best thing to do is to get the application owner on board with the testing
and explain its importance of a successful recovery of his/her application.
This might allow you to test recovery on the actual box.  Or have a second
box similar in function that is only a testing box that can be brought
offline for the recovery testing.

Just some thoughts..

Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte & Touche USA LLP
615.882.6861



-Original Message-
From: Amini, Mehdi [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 7:16 AM
To: [EMAIL PROTECTED]
Subject: Testing A WIN2k Server restore


Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**
- This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.

UNSUBSCRIBE

[Angel Gomez]

[EMAIL PROTECTED]

Re: Most stable client level for Netware

[Jim Kirkman]

We've had good results with the 4.1.3 client. on NW 5.1. In the NW 4.11 
environment.we've run 4.1.1_18 for quite a while.





Steve Schaub wrote:

> We just upgraded out AIX 4.3.3 server (3466-C00) to TSM 4.1.1.0 and are getting 
>ready to roll out new client code for our WinNT, Netware & HP-UX boxes.  Our biggest 
>problem is all the Netware abends (4.11 & 5.1) we get every night which hang the tsm 
>session and usually require a reboot.  Yes, we have kept TSA up to date.
>
> Can anyone point to the Netware tsm client release that is most stable?
>
> Steve Schaub
> Haworth, Inc
> email: [EMAIL PROTECTED]
>
> No trees were killed in the sending of this message. However a large
> number of electrons were terribly inconvenienced.

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884

Testing A WIN2k Server restore

[Amini, Mehdi]

Hi All,

I have finally found a server that I can do a test restore.

According to the Redbook SG24-6141-00 I have to Name the computer the same
as the one I am trying to recover.  My problem is that the recovering Server
is still in production and I  would like to do a test recovery of this
server.  I have installed Minimum OS on this second machine, and it is in
its own work Group.  But when I try to name the Server the same as the
recovering server, I get a message that a duplicate name found on the
Network.

How can I name the second server as the same as the first server and at the
same time be able to see the TSM Server without connecting the our main
Network?

Any help would be greatly appreciated.

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**

Re: Most stable client level for Netware

[John Naylor]

Well our netware 4.11 boxes are on Version 3, Release 7, Level 2.0.
I know this is out of support and we will have to upgrade to 4 something at some
stage, but it currently
works well for us.





Steve Schaub <[EMAIL PROTECTED]> on 02/08/2002 12:09:06 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Most stable client level for Netware



We just upgraded out AIX 4.3.3 server (3466-C00) to TSM 4.1.1.0 and are getting
ready to roll out new client code for our WinNT, Netware & HP-UX boxes.  Our
biggest problem is all the Netware abends (4.11 & 5.1) we get every night which
hang the tsm session and usually require a reboot.  Yes, we have kept TSA up to
date.

Can anyone point to the Netware tsm client release that is most stable?

Steve Schaub
Haworth, Inc
email: [EMAIL PROTECTED]

No trees were killed in the sending of this message. However a large
number of electrons were terribly inconvenienced.








**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Re: HOWTO: TSM Server Quickinst

[Jason Morgan]

In addition to the BACKUP DB, I would recommend a BACKUP VOLHIST and a
BACKUP DEVCONFIG.

Regards Jason






Farren Minns <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08/02/2002 10:38:56

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:
Subject:  Re: HOWTO: TSM Server Quickinst


I agree, super.

Just what newbies like me need.

Many thanks to you.

Farren Minns






Darren Campbell <[EMAIL PROTECTED]>@VM.MARIST.EDU> on
08/02/2002 00:36:05

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:
Subject:  Re: HOWTO: TSM Server Quickinst


Now, that is the most useful whippet of info. I've seen here!


-Original Message-
From: Josh Davis [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 7:41 AM
To: [EMAIL PROTECTED]
Subject: HOWTO: TSM Server Quickinst


I whipped this up because I run into so many people who want to figure
it out on their own, but really are just lost in the slew of new
concepts.  Here is a basic list of things to do when setting up your tsm
server the first time.  Suggestions and corrections are welcome.

-Josh


---

Basic In-Order TSM Server Setup Checklist
-

Physical Installation:
   Install physical devices
   Power on system
   Install o/s maintenance
   Install tsm server and drivers
   Define devices to the O/S
  349x, 357x, 358x and 359x use Atape/IBMTAPE/lmcpd
  all others use TSM drivers

Make a larger database and log:
   define dbvolume(make space)
   define dbcopy  (mirror elsewhere)
   extend db  (tell tsm to use the new space)
   define logv(make space)
   define logc(mirror elsewhere)
   extend log (tell tsm to use the new space)
   define spacetrigger(auto-grow db and log)
   define dbbackuptrigger (only if SET LOGMODE ROLLFORWARD)

Ensure proper licensing:
   register license   (see the server/bin directory)

Storage setup inside TSM:
   define library  (top level of tape storage)
   define devclass (points to a library)
   define drive(points to a library)
   define stg  (points to a device class)
   define vol  (points to a devclass and storage pool)
   label libvol(prepares a tape for TSM use)
   checkin libv(makes tape show up in Q LIBVOL)

For Policy/Node Information:
   define domain   (top level of policy information)
   define policyset(contained within a policy domain)
   define mgmtclass(contained within policyset)
   define copygroup T=BACK (contained within a management class)
   define copygroup T=ARCH (contained within a management class)
   activate policy (only one policyset active per domain)
   register node   (belongs to a policy domain)

Typical Storage Pool Hierarchy:
   Copygroup "destination" is disk pool
   Disk pool "NEXT" is tape pool
   An extra tape pool of type "COPYPOOL"

Other Important Things to Look Into:
   Administrator's Guide, Working With Network of TSM Servers
  Virtual Volumes
  Library Sharing
   Administrator's Guide, Chapter 1: Introduction
  Overview of storage hierarchy and TSM concepts
   Administrator's Guide, Protecting The Server
  Protection and recovery of the system
   Administrator's Guide, Disaster Recovery Manager
  Integrated, licensed tool for server protection
   DEFINE SCHED T=C
  client backup schedules
   DEFINE SCHED T=A
  server administrative schedules (don't overlap these)
 BACKUP STG (sync up copy pool)
 UPDATE STG RECLAIM=50 (reclaim free space from tapes)
 UPDATE STG RECLAIM=100 (turn off reclaimation)
 UPDATE STG HI=0 LO=0  (migrate the disk pool to tape)
 UPDATE STG HI=90 LO=70  (migrate only during overflow)
 BACKUP DB (TSM database is critical to server function)

In all procedures WATCH FOR ERRORS.

If you have questions, see http://www.tivoli.com for Documentation.
   TSM Administrator's Guide is procedural information
   TSM Administrator's Reference is command syntax
   TSM Messages Guide is decyphering for ANR/ANS messages

If you can't figure it out
   http://www.adsm.org - ADSM User's Group (searchable)
   http://www.tivoli.com - Online Knowledge Base
   IBM support: 800-237-5511 x 8

--


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.

Most stable client level for Netware

[Steve Schaub]

We just upgraded out AIX 4.3.3 server (3466-C00) to TSM 4.1.1.0 and are getting ready 
to roll out new client code for our WinNT, Netware & HP-UX boxes.  Our biggest problem 
is all the Netware abends (4.11 & 5.1) we get every night which hang the tsm session 
and usually require a reboot.  Yes, we have kept TSA up to date.

Can anyone point to the Netware tsm client release that is most stable? 

Steve Schaub
Haworth, Inc
email: [EMAIL PROTECTED]

No trees were killed in the sending of this message. However a large
number of electrons were terribly inconvenienced.

Re: HOWTO: TSM Server Quickinst

[John Naylor]

There is also Richard Sim's Functional ADSM Guide at
http://people.bu.edu/rbs/
Well worth a visit.




**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Poor BRMS performance

[Tomáš Hrouda]

Hi all,

we marked dramatic decreasing of BRMS backup performance after upgrading
OS/400. There was implemented OS/400 upgrade from 4.5 to 5.1 version
including of cumulativ PTF package C1302510. No other changes was made on
AS/400. Backup is performed by BRMS connected through 100Mbit Ethernet to
W2K TSM server.

Any comments and/or solutions would be greatly appreciated.

Toma9 Hrouda
Storage Specialist
HTD s.r.o. Praha
[EMAIL PROTECTED]
tel. +420 (2) 6791 3157
fax. +420 (2) 6791 3162

Re: HOWTO: TSM Server Quickinst

[Farren Minns]

I agree, super.

Just what newbies like me need.

Many thanks to you.

Farren Minns






Darren Campbell <[EMAIL PROTECTED]>@VM.MARIST.EDU> on
08/02/2002 00:36:05

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:
Subject:  Re: HOWTO: TSM Server Quickinst


Now, that is the most useful whippet of info. I've seen here!


-Original Message-
From: Josh Davis [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 7:41 AM
To: [EMAIL PROTECTED]
Subject: HOWTO: TSM Server Quickinst


I whipped this up because I run into so many people who want to figure
it out on their own, but really are just lost in the slew of new
concepts.  Here is a basic list of things to do when setting up your tsm
server the first time.  Suggestions and corrections are welcome.

-Josh


---

Basic In-Order TSM Server Setup Checklist
-

Physical Installation:
   Install physical devices
   Power on system
   Install o/s maintenance
   Install tsm server and drivers
   Define devices to the O/S
  349x, 357x, 358x and 359x use Atape/IBMTAPE/lmcpd
  all others use TSM drivers

Make a larger database and log:
   define dbvolume(make space)
   define dbcopy  (mirror elsewhere)
   extend db  (tell tsm to use the new space)
   define logv(make space)
   define logc(mirror elsewhere)
   extend log (tell tsm to use the new space)
   define spacetrigger(auto-grow db and log)
   define dbbackuptrigger (only if SET LOGMODE ROLLFORWARD)

Ensure proper licensing:
   register license   (see the server/bin directory)

Storage setup inside TSM:
   define library  (top level of tape storage)
   define devclass (points to a library)
   define drive(points to a library)
   define stg  (points to a device class)
   define vol  (points to a devclass and storage pool)
   label libvol(prepares a tape for TSM use)
   checkin libv(makes tape show up in Q LIBVOL)

For Policy/Node Information:
   define domain   (top level of policy information)
   define policyset(contained within a policy domain)
   define mgmtclass(contained within policyset)
   define copygroup T=BACK (contained within a management class)
   define copygroup T=ARCH (contained within a management class)
   activate policy (only one policyset active per domain)
   register node   (belongs to a policy domain)

Typical Storage Pool Hierarchy:
   Copygroup "destination" is disk pool
   Disk pool "NEXT" is tape pool
   An extra tape pool of type "COPYPOOL"

Other Important Things to Look Into:
   Administrator's Guide, Working With Network of TSM Servers
  Virtual Volumes
  Library Sharing
   Administrator's Guide, Chapter 1: Introduction
  Overview of storage hierarchy and TSM concepts
   Administrator's Guide, Protecting The Server
  Protection and recovery of the system
   Administrator's Guide, Disaster Recovery Manager
  Integrated, licensed tool for server protection
   DEFINE SCHED T=C
  client backup schedules
   DEFINE SCHED T=A
  server administrative schedules (don't overlap these)
 BACKUP STG (sync up copy pool)
 UPDATE STG RECLAIM=50 (reclaim free space from tapes)
 UPDATE STG RECLAIM=100 (turn off reclaimation)
 UPDATE STG HI=0 LO=0  (migrate the disk pool to tape)
 UPDATE STG HI=90 LO=70  (migrate only during overflow)
 BACKUP DB (TSM database is critical to server function)

In all procedures WATCH FOR ERRORS.

If you have questions, see http://www.tivoli.com for Documentation.
   TSM Administrator's Guide is procedural information
   TSM Administrator's Reference is command syntax
   TSM Messages Guide is decyphering for ANR/ANS messages

If you can't figure it out
   http://www.adsm.org - ADSM User's Group (searchable)
   http://www.tivoli.com - Online Knowledge Base
   IBM support: 800-237-5511 x 8

--

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.

UNSUBSCRIBE

[Udo Winter]

Mit freundlichen Grüßen

Udo Winter

adcon Gesellschaft für
EDV-Dienstleistung / Beratung mbH
An der Goymark 23
44263 Dortmund

Re: restoring backupsets

[John Naylor]

Switch on perform tracing on the client.
This will break down where the time is being spent, so you can identify your
bottleneck
I was seeing circa 3 mb. sec restoring a netware client from 9840 across a
network
With a directly attached tape and an  AIX client you ought to get better.
John





John Bremer <[EMAIL PROTECTED]> on 02/07/2002 11:07:01 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  restoring backupsets



*SMers,

We're trying to restore a backupset from 9840 media.  Our tape drive is
attached to an AIX client and we are seeing only 1-2 MB/sec data transfer
rates.

Is there a reason why we don't see tape and/or disk speeds on this
restore?  The disk should run at 14-15 MB/sec and the SCSI 9840 at 10 MB/sec.

THanks.  John Bremer








**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**