Re: Move Nodedata starts and ends without doing anything

[Jurjen Oskam]

On Tue, Nov 11, 2003 at 02:01:33PM -0500, Richard Sims wrote:

> That obviously precludes Access=Offsite.  And wouldn't it be nice if the
> programmers put out some kind of message when the function ends up copying
> none of the data that the customer requested?  (Come on, IBM - that's not
> "enterprise" level programming.)

You wouldn't believe how much effort it took to get APAR IC36499 opened
(which addresses this issue).

How it finally got opened: I nailed them with the fact that even a MOVE
NODEDATA on a *non-existant* filespace reported success with 0 bytes moved.
At first support even classified this as "works as designed": "Since
there wasn't any data to be moved, moving 0 bytes is success". After I
asked them to fix the DELETE FILESPACE command (which *does* give an error
on a non-existant filespace), support instead finally opened the APAR for
MOVE NODEDATA.

Once the APAR was opened, a programmer apparently took advantage of it to
also include the reporting of off-site volumes.

--
Jurjen Oskam

PGP Key available at http://www.stupendous.org/

Re: V5.1.8.0 server on z/OS

[Stumpf, Joachim]

Hi,

at the moment we are migrating from 5.1.6.3 to 5.2.1.1 on z/OS (But we are not 
migrating to 5.1.8 first).
After upgradedb of the first server we had a huge problem with the performance and IBM 
told us to ZAP our DSMSERV module in the linklib (APAR PQ80211).
Now everything works fine and I can upgrade the rest of our TSM-Servers ;-)

regards
Joachim Stumpf

- Original-Nachricht folgt -

I was planning to upgrade my z/OS server to 5.1.7 when 5.1.8 came out (I
want to go to 5.2.x but need to figure out what I need to do to get the
tapes since the ftp site only seems to include patches to 5.2.x).

I have installed this upgrade to my test server and so far so good !

Anyone performed this update, already ?

Any problems jumping from 5.1.6.4 to 5.1.8.0 ? (yes, I realize an
UPGRADEDB is required !) ?  When I upgraded my test server, I jumped from
5.1.6.4 to 5.1.7.0 and then to 5.1.8.0.

Antwort: Re: Move Nodedata starts and ends without doing anything

[Markus Veit]

I agree,
a move data works on offsite tapes, the primary stgpool volumes are used, just
as space reclamaition.

I had a call open with TSM support were space reclamation always failed on
several volumes with a database error.
The funny thing was when you did a move data on the offsite pool it was
successfull, but the next time a backup storagepool was run on the primary
storagepool, TSM wanted to backup that file to the copypool. 

The problem only dissapeared after the files on these volumes expired, so what
went wrong could not be traced back by 2nd level TSM support

Mit freundlichen Grüßen / Best Regards

Markus Veit





   
   
   
An: [EMAIL PROTECTED]
Kopie: 
Thema:   Re: Move Nodedata starts and 
ends without doing anything
   
  [EMAIL PROTECTED]   
  Received :  11.11.2003   
  21:17
  Bitte antworten an "ADSM:
  Dist Stor Manager"   
   




I concur.  I have done MOVE DATA on copypool tapes.  TSM simply recopies
the original onto new copypool tapes since it knows the real "copy pool
tapes" are offsite !





Richard Sims <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/11/2003 02:05 PM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: Move Nodedata starts and ends without doing anything


>Don't think you can do a move nodedata for a copy pool.  Must be done on
=
>a primary pool.

Says the reference manual:
"The data can be located in either a primary or copy storage pool."
The problem with the attempted operation was Offsitedness and TSM
documentation and programming shortcomings.

   Richard Sims, BU

cleanup backupgroups and expire inventory

[Frank Mueller]

Hi *,

I need your help!!!

We have 2 TSM-server, both on AIX 4.3.3. The first Server is on TSM V
4.2.2.6 and second Server is on TSM V 4.2.4.0. On both server are librarys
attached.
Three steps to backup the clients.
1. backup the client to SSA-disks on the first server
2. migrate this data to the first library
3. backup stg for copy data from the first library to the second library on
the second TS-server

Now I have a big problem with the space on the second server. I can delete
some data on the first server and run exp inventory and I get more space in
the library. It runs fine. But I get no space on the second server and now
the library is full.

I search in this mailing lists and find some hint s for
1. audtit db fix=yes
2. claenup backupsgroups


Can this help??


Best regards,
Frank Mueller

unsubscribe

[Holly Peppers]

Holly L. Peppers
Coca Cola Enterprises
[EMAIL PROTECTED]
(770) 829-7179
*

This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is confidential and
privileged and exempt from disclosure under applicable law.  If the reader
of this message is not the intended recipient, you are hereby notified that
any dissemination, distribution, or copying of this communication is
strictly prohibited.  If you have received this communication in error,
please contact the sender immediately and delete it from your system.
Thank
you
*

Re: Firmware upgrade on 3583 library

[Coats, Jack]

I just know if you call IBM for support they want you on the 'latest' before
they will even talk with you more than superficially. :( ... at least that
is
my experience.

-Original Message-
From: Graham Trigge [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 9:04 PM
To: [EMAIL PROTECTED]
Subject: Firmware upgrade on 3583 library
[snip]
I cannot find any definitive information regarding firmware revisions on
3583 libraries running on TSM 4.2.3.0 on AIX 3.4. Is there a particular
revision of firmware which needs to be loaded, or can I load the latest
firmware that I can lay my hands on (this is for the library and LTO1
drives)? If anyone can point me to the answer, I would be grateful.
[snip]

Re: client restore fails trying to replace files that don't exist

[Prather, Wanda]

Roger,

I don't know anything about Windows ME.  You may have a bug.

But I have seen something like this on Win2K; the symtom is that you get
prompted for permission to overwrite a file, even when you are restoring
into a previously empty directory.

When I have seen this on Win2K, it has been a problem with 8.3 filenames.
When TSM does restores, it recreates every file, so each long file name gets
a reconstructed 8.3 filename, which may be DIFFERENT from its original 8.3
filename.

If the system has 8.3 filenames turned on, there is a Windows rule that says
how the 8.3 filename gets constructed.

And, you can have "clashes", where 2 files with different long file names
map back into the same 8.3 filename.  The first one restores OK, the second
one TSM tries to restore results in a prompt to overwrite.  It isn't obvious
what is happening, because TSM gives you the error on the LONG file name,
not the 8.3 one.

It is most likely to happen with long filenames that begin with identical
chars and end in very similar characters, for example:

very.long. my file name is a mess.urk
very.long. my file name is a [EMAIL PROTECTED]
very.long. my file name is a mess.xurk


The fix for this (again on Win2K) is a registry hack that TURNS OFF the
creation of the 8.3 filename - you can find it in Microsoft's knowledge base
(search on 8.3).

Turn off the 8.3 filenames, finish the restore, then turn them back on
again.

There is no TSM fix that prevents this behavior, because there is no Windows
fix for it.  You can reproduce the same behavior with XCOPY, not just with
TSM.

Again, this may not be your problem.
But it's something to look at.

Wanda





-Original Message-
From: Roger Deschner [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 6:29 PM
To: [EMAIL PROTECTED]
Subject: client restore fails trying to replace files that don't exist


I'm having a client problem that has gotten me stumped. (And that takes
some doing.)

The client node is Windows ME. The hard drive crashed, they got a new
one, and reinstalled WinME from the original install CD. They started
with an old V3.7 client program when this issue first started, but I
since upgraded them to the latest WinME client, V5.1.6. It didn't help.
(Our server is AIX TSM 5.1.6.5)

The owner of this node decided against doing a total full "bare metal"
restore, and is instead restoring whole directories containing his
documents.

On several occasions, restores are failing like this:

They open the GUI client, and navigate to a directory they want to
restore. They click on it, and click Restore. They leave the default
"Original Location" selected. It begins to issue a series of
"File/Directory already exists" and "File is read/only" error messages.
No matter how many times you tell it that it's OK to Replace, and "Apply
action to all remaining files", it gets stuck asking this question on
the SAME FILE over and over.

I was called to this person's office to diagnose it. They are doing
nothing wrong that I can see. The files and directories being complained
about indeed do not exist yet. I looked carefully in Windows Explorer,
after being sure to turn on Windows Explorer's options to show hidden
files, and show known file types.

I have seen this kind of thing once before, long long ago, and I thought
it was fixed several releases ago. Both client and server are now
up-to-date. Has anybody else seen this?

Roger Deschner  University of Illinois at Chicago [EMAIL PROTECTED]

Re: Is HSM supported on Windows

[Prather, Wanda]

There is a third-party product that provides the Windows HSM support, so it
isn't in the IBM manual.

It's Diskextender.
Invented by OTG, bought by Legato, bought by EMC (sigh).

But still available and supported.  It is a special build of OTG that
installs with the TSM client on Windows.

At our local User Group meeting, the one person who was using it, liked it.

If you search the archives of the list, you will find some pros and cons.

- Go to: search.adsm.org
-search the 2003 archives with the keyword OTG.




-Original Message-
From: Richard Sims [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 7:37 AM
To: [EMAIL PROTECTED]
Subject: Re: Is HSM supported on Windows


>Is Tivoli Hierarchical Storage Management supported on
>windows platform. Probably not. I just want to make
>sure.
>I think it is supported on Unix. Thanks.

The beginning of each manual summarizes the platforms on which
the involved software runs.  For reference, utilize web page
 http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
where you would choose "IBM Tivoli Storage Manager for Space Management"
(the current name of the product - despite what it says on the backside
of the cover page).

   Richard Sims   http://people.bu.edu/rbs

TSM, Veritas and SAP

[Gill, Geoffrey L.]

I know there have been questions about how Veritas compares to TSM but I
can't seem to find anything with SAP specifically in the mix. Has anyone out
there used Veritas to back up SAP data? Do they have a similar setup as TSM
as it relates to the TDP for R/3? The reason I ask is because someone here
has tried, from what I can gather, some sort of power grab and wants to move
this in here to backup the SAP data and take it off TSM.



I would like to see if there are any horror stories, or possibly even good
ones, dealing with this.



Thanks,

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

Need experiences with TSM 5.2.x upgrade on z/OS

[Joe Howell]

We're preparing to upgrade our TSM 5.1.6 server to 5.2.x.  We run on z/OS and have 
seen the writeup on apar PQ80211.  IBM recommends either coming up to TSM 5.1.7.3 and 
running CLEANUP BACKUPGROUPS prior to beginning the upgrade to 5.2.x, or upgrading 
straight to 5.2.1.3 (which doesn't seem to be available yet - don't you just love 
being on the edge?) to get the fix for the apar.  There's also a zap available to fix 
the problem with CLEANUP BACKUPGROUPS.  Has anyone been through this?  What seems to 
be the cleanest way to deal with this issue?




Joe Howell
Shelter Insurance Companies
Columbia, MO

-
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard

export/import

[Joni Moyer]

Hello all!

I am just trying to get a better idea of how export/import data between 2
tsm os/390 servers works.  I know that in order to do this I will have to
create server to server communication.  I will then export the data for
certain nodes onto virtual memory.  What virtual memory is used?  How does
tsm know where to put this information?  When tsm exports data, does it
just make a copy of the information from the originator and then import the
copy onto the new server(location) or does it delete the information off of
the originating server?

Also, do I have to have the exact same management classes defined on the
server that will import the data or can I reassign a new management class
name to the files and directories?  If I don't have the same management
class defined will it get the default management class for that policy
domain?  Do I have to have the same policy domain and policy set as well?
I want it changed when I move them from test to production, but I wasn't
exactly sure how this would work...

Thanks for any input you might have on this topic!


***
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603 **New as of 11/1/03
Fax:(717)302-5974
[EMAIL PROTECTED]
***

Re: export/import

[Prather, Wanda]

If you're just trying to move some client data from one TSM server to
another, you also have the alternative of just using a tape!

Run EXPORT on the first TSM server, write the data to a tape.
Run IMPORT on the second TSM server, specify the volser of that tape.

That's all there is to it!
It's much faster than using server-to-server communication, because with
server-to-server, you have to transmit the data via TCP-IP.

The only reason you MUST use server-to-server for export/import, is if you
have no compatible media that both servers can read/write.



-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 1:00 PM
To: [EMAIL PROTECTED]
Subject: export/import


Hello all!

I am just trying to get a better idea of how export/import data between 2
tsm os/390 servers works.  I know that in order to do this I will have to
create server to server communication.  I will then export the data for
certain nodes onto virtual memory.  What virtual memory is used?  How does
tsm know where to put this information?  When tsm exports data, does it
just make a copy of the information from the originator and then import the
copy onto the new server(location) or does it delete the information off of
the originating server?

Also, do I have to have the exact same management classes defined on the
server that will import the data or can I reassign a new management class
name to the files and directories?  If I don't have the same management
class defined will it get the default management class for that policy
domain?  Do I have to have the same policy domain and policy set as well?
I want it changed when I move them from test to production, but I wasn't
exactly sure how this would work...

Thanks for any input you might have on this topic!


***
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603 **New as of 11/1/03
Fax:(717)302-5974
[EMAIL PROTECTED]
***

Re: export/import

[Joni Moyer]

I can write to tape, but since this concerns tsm on the mainframe and the
stk silos are run with tms, I don't think that I can remove one tape from
the test silo arena and have it read in the production tms.  The production
tms won't recognize the tape volser and I don't think this will work...

Also, is the data deleted from the original tsm server or is it just a
copy?  I don't want to lose important data while trying to do this.

Thanks!


***
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603 **New as of 11/1/03
Fax:(717)302-5974
[EMAIL PROTECTED]
***



 "Prather, Wanda"
 <[EMAIL PROTECTED]
 UAPL.EDU>  To
 Sent by: "ADSM:   [EMAIL PROTECTED]
 Dist Stor  cc
 Manager"
 <[EMAIL PROTECTED] Subject
 .EDU> Re: export/import


 11/12/2003 01:29
 PM


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






If you're just trying to move some client data from one TSM server to
another, you also have the alternative of just using a tape!

Run EXPORT on the first TSM server, write the data to a tape.
Run IMPORT on the second TSM server, specify the volser of that tape.

That's all there is to it!
It's much faster than using server-to-server communication, because with
server-to-server, you have to transmit the data via TCP-IP.

The only reason you MUST use server-to-server for export/import, is if you
have no compatible media that both servers can read/write.



-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 1:00 PM
To: [EMAIL PROTECTED]
Subject: export/import


Hello all!

I am just trying to get a better idea of how export/import data between 2
tsm os/390 servers works.  I know that in order to do this I will have to
create server to server communication.  I will then export the data for
certain nodes onto virtual memory.  What virtual memory is used?  How does
tsm know where to put this information?  When tsm exports data, does it
just make a copy of the information from the originator and then import the
copy onto the new server(location) or does it delete the information off of
the originating server?

Also, do I have to have the exact same management classes defined on the
server that will import the data or can I reassign a new management class
name to the files and directories?  If I don't have the same management
class defined will it get the default management class for that policy
domain?  Do I have to have the same policy domain and policy set as well?
I want it changed when I move them from test to production, but I wasn't
exactly sure how this would work...

Thanks for any input you might have on this topic!


***
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603 **New as of 11/1/03
Fax:(717)302-5974
[EMAIL PROTECTED]
***

Urgent Requirement For Tivoli Consultant

[Ari Banerjee]

Hi,

We have some urgent requirement for

TAM and TIM Architects.

These are contract positions for a duration of 9-12 months in NJ,
Chicago and Texas

Please send Resume, contact details and per hour rate.

Thanks




http://www.db-solution.com 

_

Note: Under Bill s.1618 Title III passed by the 105th U.S. Congress this
mail can not be considered spam as long as we include contact
information and a remove link for removal from our mailing list. To be
removed from our mailing list reply with "remove" and include your
"original email address/addresses" in the subject heading. Include
complete address/addresses where our mail is received. We will
immediately update it accordingly. We apologize for the  Inconvenience
if any caused.


Databased Solutions Inc.

__

TSM, Active Directory, Example dsm.opt File

[Paul Strobeck]

Greetings

We are currently getting ready to move over to Windows 2K...We will be
using TSM to backup 4 DC's...what are the recommended include/excludes?
Can anyone provide a sample dsm.opt file for Windows 2K DC using AD?

Specifically--are folks who are using TSM to backup Windows 2K using it
to backup the Active Directory?

Any help is most appreciated.

...Paul

[EMAIL PROTECTED]

Re: export/import

[Prather, Wanda]

It's a copy.

-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 2:01 PM
To: [EMAIL PROTECTED]
Subject: Re: export/import


I can write to tape, but since this concerns tsm on the mainframe and the
stk silos are run with tms, I don't think that I can remove one tape from
the test silo arena and have it read in the production tms.  The production
tms won't recognize the tape volser and I don't think this will work...

Also, is the data deleted from the original tsm server or is it just a
copy?  I don't want to lose important data while trying to do this.

Thanks!


***
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603 **New as of 11/1/03
Fax:(717)302-5974
[EMAIL PROTECTED]
***



 "Prather, Wanda"
 <[EMAIL PROTECTED]
 UAPL.EDU>  To
 Sent by: "ADSM:   [EMAIL PROTECTED]
 Dist Stor  cc
 Manager"
 <[EMAIL PROTECTED] Subject
 .EDU> Re: export/import


 11/12/2003 01:29
 PM


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






If you're just trying to move some client data from one TSM server to
another, you also have the alternative of just using a tape!

Run EXPORT on the first TSM server, write the data to a tape.
Run IMPORT on the second TSM server, specify the volser of that tape.

That's all there is to it!
It's much faster than using server-to-server communication, because with
server-to-server, you have to transmit the data via TCP-IP.

The only reason you MUST use server-to-server for export/import, is if you
have no compatible media that both servers can read/write.



-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 1:00 PM
To: [EMAIL PROTECTED]
Subject: export/import


Hello all!

I am just trying to get a better idea of how export/import data between 2
tsm os/390 servers works.  I know that in order to do this I will have to
create server to server communication.  I will then export the data for
certain nodes onto virtual memory.  What virtual memory is used?  How does
tsm know where to put this information?  When tsm exports data, does it
just make a copy of the information from the originator and then import the
copy onto the new server(location) or does it delete the information off of
the originating server?

Also, do I have to have the exact same management classes defined on the
server that will import the data or can I reassign a new management class
name to the files and directories?  If I don't have the same management
class defined will it get the default management class for that policy
domain?  Do I have to have the same policy domain and policy set as well?
I want it changed when I move them from test to production, but I wasn't
exactly sure how this would work...

Thanks for any input you might have on this topic!


***
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603 **New as of 11/1/03
Fax:(717)302-5974
[EMAIL PROTECTED]
***

Re: client restore fails trying to replace files that don't exist

[Roger Deschner]

H. Very interesting! Thanks, Wanda - this actually gives me
something to go on. All WinME systems use 8.3 filenames deep down
inside, because WinME was still built on a MS/DOS kernel. (Last of that
species!)

This might also explain why a circumvention we tried worked: Restore to
C:\abacadabra didn't work. So I tried a restore to a different location
C:\temp which worked. Then to my surprise, I was able to successfully
rename C:\temp to C:\abacadabra. The reason it worked was that rename
correctly chose a different 8.3 name for C:\abacadabra than for possibly
existing directory C:\abacadabrashazam. Now I need to go check this
client and see if he also has C:\abacadabrashazam on his computer, and
look and see what 8.3 names already exist that might cause a collision.

If this is true, then a full "bare metal" restore should also work OK.
Then all files are restored at once, and even if the new 8.3 names are
different, at least there will not be collisions because each long name
will map to a unique 8.3 name.

The problem arises when the client does piecemeal restores - and then
goes back in for more. I have always regarded the piecemeal restore
method to be the worst for resynchronization issues, and now I have
another reason to discourage it.

I don't know if this business of collision in the 8.3 namespace will be
it, but this certainly gives me something to go on to try to find it.

Thanks a lot!

Roger Deschner  University of Illinois at Chicago [EMAIL PROTECTED]


On Wed, 12 Nov 2003, Prather, Wanda wrote:

>Roger,
>
>I don't know anything about Windows ME.  You may have a bug.
>
>But I have seen something like this on Win2K; the symtom is that you get
>prompted for permission to overwrite a file, even when you are restoring
>into a previously empty directory.
>
>When I have seen this on Win2K, it has been a problem with 8.3 filenames.
>When TSM does restores, it recreates every file, so each long file name gets
>a reconstructed 8.3 filename, which may be DIFFERENT from its original 8.3
>filename.
>
>If the system has 8.3 filenames turned on, there is a Windows rule that says
>how the 8.3 filename gets constructed.
>
>And, you can have "clashes", where 2 files with different long file names
>map back into the same 8.3 filename.  The first one restores OK, the second
>one TSM tries to restore results in a prompt to overwrite.  It isn't obvious
>what is happening, because TSM gives you the error on the LONG file name,
>not the 8.3 one.
>
>It is most likely to happen with long filenames that begin with identical
>chars and end in very similar characters, for example:
>
>very.long. my file name is a mess.urk
>very.long. my file name is a [EMAIL PROTECTED]
>very.long. my file name is a mess.xurk
>
>
>The fix for this (again on Win2K) is a registry hack that TURNS OFF the
>creation of the 8.3 filename - you can find it in Microsoft's knowledge base
>(search on 8.3).
>
>Turn off the 8.3 filenames, finish the restore, then turn them back on
>again.
>
>There is no TSM fix that prevents this behavior, because there is no Windows
>fix for it.  You can reproduce the same behavior with XCOPY, not just with
>TSM.
>
>Again, this may not be your problem.
>But it's something to look at.
>
>Wanda
>
>
>
>
>
>-Original Message-
>From: Roger Deschner [mailto:[EMAIL PROTECTED]
>Sent: Monday, November 10, 2003 6:29 PM
>To: [EMAIL PROTECTED]
>Subject: client restore fails trying to replace files that don't exist
>
>
>I'm having a client problem that has gotten me stumped. (And that takes
>some doing.)
>
>The client node is Windows ME. The hard drive crashed, they got a new
>one, and reinstalled WinME from the original install CD. They started
>with an old V3.7 client program when this issue first started, but I
>since upgraded them to the latest WinME client, V5.1.6. It didn't help.
>(Our server is AIX TSM 5.1.6.5)
>
>The owner of this node decided against doing a total full "bare metal"
>restore, and is instead restoring whole directories containing his
>documents.
>
>On several occasions, restores are failing like this:
>
>They open the GUI client, and navigate to a directory they want to
>restore. They click on it, and click Restore. They leave the default
>"Original Location" selected. It begins to issue a series of
>"File/Directory already exists" and "File is read/only" error messages.
>No matter how many times you tell it that it's OK to Replace, and "Apply
>action to all remaining files", it gets stuck asking this question on
>the SAME FILE over and over.
>
>I was called to this person's office to diagnose it. They are doing
>nothing wrong that I can see. The files and directories being complained
>about indeed do not exist yet. I looked carefully in Windows Explorer,
>after being sure to turn on Windows Explorer's options to show hidden
>files, and show known file types.
>
>I have seen this kind of thing once before, long long ago, and I thought
>it was fixed several releases ago. Both client and s

Anyone done BMR on Linux??

[Bill Boyer]

Anyone care to share any experiences on doing Linux BMR?

I've read through the redbook "Disaster Recovery Strategies using TSM" as
well as the Linux-Complete-Backup-and-Recovery-Howto. I have AIX background,
and trying to equate things...is the stage-1 backup where you tar the system
like doing the mksysb on AIX? Except it's not bootable. How often would you
need to do this stage-1 backup? If it's not as often as my incremental
backups with TSM, then the restore with TSM would then have to include the
system files to pick up any changesright?

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

Re: TSM, Active Directory, Example dsm.opt File

[Khan, Khalid B.]

Check the guide on "Deploying Tivoli Storage Manager for Windows 2000" it will detail 
an example of the dsm.opt. Which is where I built my from.

Here is my dsm.opt from one of the DC with AD running:

TCPSERVERADDRESS A.B.C.D
PASSWORDACCESS GENERATE
SCHEDMODE POLLING
SCHEDLOGR 20 D
ERRORLOGR 20 D
COMPression ON
TXNBYTELIMIT 25600
QUERYSCHEDPERIOD 6
DOMAIN  ALL-LOCAL
COMPRESSALWAYS YES

EXCLUDE "C:\I386\...\*" 
EXCLUDE "C:\DOCUMENTS AND SETTINGS\...\*" 
Exclude "*:\pagefile.sys"
Exclude *:\...\SYSTEM32\CONFIG\...\*
Exclude *:\...\SYSTEM32\CONFIG\...\*.*
Exclude *:\...\Profiles\...\ntuser.dat* 
Exclude *:\...\system32\Perflib*.dat
EXCLUDE "C:\WINNT\system32\CPL.CFG"
EXCLUDE "C:\WINNT\system32\*.dat"
EXCLUDE *.dmp
EXCLUDE *.tmp
EXCLUDE *.msg
EXCLUDE "*:\WINNT\DEBUG\*.*"
Exclude.dir "*:\...\NTDS"
Exclude.dir "C:\Documents and Settings"
Exclude.dir C:\temp
Exclude.dir D:\Temp
Exclude.dir E:\Temp
Exclude.dir D:\Spool
Exclude.dir F:\Temp
Exclude.dir F:\I386
Exclude.dir *:\...\system32\wins
Exclude.dir *:\...\system32\LServer
Exclude.dir *:\...\system32\dhcp
Exclude.dir *:\...\system32\config
Exclude.dir *:\...\ntfrs\jet
Exclude.dir "*:\System Volume Information"
Exclude.dir "*:\...\Temporary Internet Files"
Exclude.dir *:\Recycled
Exclude.dir *:\Recycler
INCLUDE *.pst   PST
INCLUDE "*:\ADSM.SYS\...\*"

I hope this helps.

Khalid Khan
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Strobeck
Sent: Wednesday, November 12, 2003 2:41 PM
To: [EMAIL PROTECTED]
Subject: TSM, Active Directory, Example dsm.opt File

Greetings

We are currently getting ready to move over to Windows 2K...We will be
using TSM to backup 4 DC's...what are the recommended include/excludes?
Can anyone provide a sample dsm.opt file for Windows 2K DC using AD?

Specifically--are folks who are using TSM to backup Windows 2K using it
to backup the Active Directory?

Any help is most appreciated.

...Paul

[EMAIL PROTECTED]

Re: Anyone done BMR on Linux??

[Lloyd Dieter]

You may want to have a peek at Mondo:

http://www.mondorescue.org

Once you get it set up, that will give you your "mksysb-style" bootable
media.  It's pretty useful for getting a Linux box back quickly.

I don't recommend it by itself, however...I use it as a quick method to
get the box back to where I can restore from TSM...and whatever you do,
test it before you bet the farm on it.  It tends to be very finicky about
certain things.  And just because it works OK on one
kernel/release/update, don't assume that it's OK forevermore.

-Lloyd


On Wed, 12 Nov 2003 14:42:30 -0500
Bill Boyer <[EMAIL PROTECTED]> wrote thusly:

> Anyone care to share any experiences on doing Linux BMR?
>
> I've read through the redbook "Disaster Recovery Strategies using TSM"
> as well as the Linux-Complete-Backup-and-Recovery-Howto. I have AIX
> background, and trying to equate things...is the stage-1 backup where
> you tar the system like doing the mksysb on AIX? Except it's not
> bootable. How often would you need to do this stage-1 backup? If it's
> not as often as my incremental backups with TSM, then the restore with
> TSM would then have to include the system files to pick up any
> changesright?
>
> Bill Boyer
> "Some days you are the bug, some days you are the windshield." - ??
>


--
-
Lloyd Dieter-   Senior Technology Consultant
 Registered Linux User 285528
   Synergy, Inc.   http://www.synergyinc.cc   [EMAIL PROTECTED]
 Main:585-389-1260fax:585-389-1267
-

Re: Urgent Requirement For Tivoli Consultant

[Mark Mooney]

Can you contact me at [EMAIL PROTECTED] with your specific
requirements please.

Thanks,
Mooney

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Ari Banerjee
Sent: Wednesday, November 12, 2003 12:58
To: [EMAIL PROTECTED]
Subject: Urgent Requirement For Tivoli Consultant

Hi,

We have some urgent requirement for

TAM and TIM Architects.

These are contract positions for a duration of 9-12 months in NJ,
Chicago and Texas

Please send Resume, contact details and per hour rate.

Thanks




http://www.db-solution.com 

_

Note: Under Bill s.1618 Title III passed by the 105th U.S. Congress this
mail can not be considered spam as long as we include contact
information and a remove link for removal from our mailing list. To be
removed from our mailing list reply with "remove" and include your
"original email address/addresses" in the subject heading. Include
complete address/addresses where our mail is received. We will
immediately update it accordingly. We apologize for the  Inconvenience
if any caused.


Databased Solutions Inc.

__