Fw: Can 64bit TSM client on 64 bit os overcome backing up large filesytems??

2006-06-26 Thread Pete Tanenhaus
The basic problem is the limit of addressable virtual memory available to
a Win32 process.

The virtual address space of a Win32 process is 4 gigabytes (2 ^ 32).

By default, only 2 gigabytes of this address space may be allocated as
virtual memory
(the limit can be increased to 3 gigabytes by using the /3GIG boot.ini
setting).

TSM full incremental backup requires loading the entire list of active
objects for a file system
from the TSM server into memory,  and then loading each local directory
branch into memory
one at a time in order to perform the backup.

A large enough file system (the exact number of objects depends a few
variables such as
the length of file names and the directory depth) will eventually cause
the TSM client process
to  run out off addressable memory and not to be able to complete the
backup.

The MemoryEfficient client option somewhat mitigates the process memory
utilization by loading
active files from the server a directory at a time (instead of loading the
entire filespace at once).

Functions such as Incremental By Date and Journal Based Backup are only
available after an
initial  full  incremental backup has completed.

The virtual address space of a Win64 process is much larger (2 ^ 64) than
that of a Win32 process,
so to answer your question, upgrading to Win64 and installing the Win64
TSM client would solve
the problem of running out of memory.

Development is also working on a disk caching solution in a future release
which minimizes
the amount of virtual memory required during a backup and should allow
most file systems
to backed up regardless of size (the trade off of course being that the
backup may take longer
to complete).

Hope this answers your questions 




Pete Tanenhaus
Tivoli Storage Manager Client Development
email: [EMAIL PROTECTED]
tieline: 320.8778, external: 607.754.4213

"Those who refuse to challenge authority are condemned to conform to it"


-- Forwarded by Pete Tanenhaus/San Jose/IBM on
06/26/2006 06:25 PM ---
Please respond to "ADSM: Dist Stor Manager" 
Sent by:"ADSM: Dist Stor Manager" 
To: ADSM-L@VM.MARIST.EDU
cc:
Subject:Can 64bit TSM client on 64 bit os overcome backing up
large filesytems??


I am having problems backing up a large filesystem on a win2003k server.
The backup is failing because its running out of memory which IBM says
is because of the 32bit os limitation.  Tried journaling but the server
is very busy and continuously gets buffer overflows and the journal
fails and I have tried tuning it as well but it still fails.  I have not
tried the image snapshot backup but I don't trust doing it on a 1 TB
windows filesystem.  So I was thinking of upgrading the server to
win2003k 64bit and loading the tsm 64bit client to backup the server to
overcome the 32 bit limitations.



Do any of you guys see a problem with that or will I still have the same
problems as before?


**EMAIL DISCLAIMER***

This email and any files transmitted with it may be confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.  If you are not the intended recipient or the individual
responsible for delivering the e-mail to the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is strictly prohibited.  If you have received
this
e-mail in error, please delete it and notify the sender or contact Health
Information Management 312.413.4947.


Can 64bit TSM client on 64 bit os overcome backing up large filesytems??

2006-06-26 Thread Dearman, Richard
I am having problems backing up a large filesystem on a win2003k server.
The backup is failing because its running out of memory which IBM says
is because of the 32bit os limitation.  Tried journaling but the server
is very busy and continuously gets buffer overflows and the journal
fails and I have tried tuning it as well but it still fails.  I have not
tried the image snapshot backup but I don't trust doing it on a 1 TB
windows filesystem.  So I was thinking of upgrading the server to
win2003k 64bit and loading the tsm 64bit client to backup the server to
overcome the 32 bit limitations. 

 

Do any of you guys see a problem with that or will I still have the same
problems as before?


**EMAIL DISCLAIMER***

This email and any files transmitted with it may be confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.  If you are not the intended recipient or the individual
responsible for delivering the e-mail to the intended recipient, any 
disclosure, copying, distribution or any action taken or omitted to be 
taken in reliance on it, is strictly prohibited.  If you have received this
e-mail in error, please delete it and notify the sender or contact Health 
Information Management 312.413.4947.

 


Re: Réf. : Re: [ADSM-L] tape content with backup date

2006-06-26 Thread Jeremy Cloward
Salut Vincent, 
 there is a way to access the SQL tables, 
 you need the interface called ODBC, you can use that , with MS excell to
go and poll the database for pretty much anything. 
I have to use it cause my Version of ADSM is on a VM server that has
not been updated since 96, ODBC is a lifesaver. 
 Au tous, 
 Jeremy 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, June 26, 2006 11:13 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Réf. : Re: [ADSM-L] tape content with backup date

Thank's Alexander for your help

Do you know a solution to have direct access to the TSM tables, or do I
have to forget it ?

Any IBM tech guy around here to confirm if it is or not possible to get
the results ?

Regards

Vince





Alexander Verkooijen <[EMAIL PROTECTED]> Envoyé par : "ADSM: Dist Stor
Manager" 
26/06/06 16:02
Veuillez répondre à "ADSM: Dist Stor Manager"

 
Pour :  ADSM-L@VM.MARIST.EDU
cc :(ccc : Vincent RATAJSZCZAK/INFOGER/GRT/FR)
Objet : Re: [ADSM-L] tape content with backup date


If you had access to the *real* tables that reside in the TSM databse
then, yes, it would be possible. Since the SQL interface only provides
access to *pseudo* tables I don't think it's possible.

Please correct me if I'm wrong. In the
past there have been times when I could have used a list like this.

Regards,

Alexander


Alexander Verkooijen
Senior Systems Programmer
High Performance Computing
SARA Computing & Networking Services
 

> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf 
> Of Vincent RATAJSZCZAK
> Sent: donderdag 22 juni 2006 18:07
> To: ADSM-L@VM.MARIST.EDU
> Subject: tape content with backup date
> 
> Dear lovely TSM World,
> 
> I have a special request for you...
> 
> I would like to list the content of a specific tape (destroyed) with a 
> column with the backuped date of the objet.
> 
> ==>   "Q content XXX" is poor
> 
> ==>   "select * from contents where volume_name=" give me
> Node_name/File_name, but no backuped date
> 
> ==>  "select * from backups" give me Node_name/File_name and backuped 
> date, but no tape affectation
> 
> 
> Between the 2nd and 3rd, I can't find a common field to join the 
> tables
> 
> 
> Anyone could help me please ?
> 
> Do you think it's possible ?
> 
> The restore GUI show you the file name and backuped date, so I think 
> YES, but
> 
> Thank's
> 
> Vince
> 


Re: Sleeping Macs and Failed TSM Backups

2006-06-26 Thread Paul Zarnowski

I think the encryption is keyed to the hostname, not the
nodename.  This is based on empirical observation.  On MacOS X, the
/etc/hostconfig file is set to +automatic+ (or something close to
that).  This indicates that the hostname should be set
automatically.  If the IP address is set via DHCP, then the hostname
will indeed change as the IP address changes.  But what makes things
even worse is that if there is no network connectivity, then the
hostname will change to what is specified in the "file sharing"
setup, which is even different.  I think what may be going on is that
if you lose network connectivity, then the hostname can change to the
"file sharing" name.  (No, I haven't verified this).  When the
hostname changes, and TSM attempts to connect to the server, if the
hostname is different than what was used to encrypt the password then
TSM will nicely delete the TSM.PWD file for you.  This leads to user
headache and confusion.

The "workaround" that IBM has documented is to add a "sleep 60"
command to the startup script that starts the scheduler
service.  This simply gives MacOS a chance to complete startup
activity and set the hostname based on the IP address before TSM
scheduler starts up.  If the hostname changes after this, it doesn't help.

I think a better workaround may be to change the /etc/hostconfig file
to hardcode a hostname, making it independent of DHCP.  I talked to
someone at Apple about this at a conference I recently attended, and
they didn't see a problem with doing this.

If someone wants to explore this in more detail, I'd be happy to hear
your results.

BTW, I think this problem may actually exist on some other Unix
systems - it's just that MacOS is the most likely variant of Unix to
exist on a travelling Laptop, and thus most likely to run into this.

..Paul

At 08:09 AM 6/26/2006, Richard Sims wrote:

I wonder if what's happening is that these personal computers are
gaining their network access via DHCP, wherein their network identity
is dynamic and can change upon renegotiation, as when the dormant
computer is awakened after some time.  As I understand TSM client
password encryption (per IBM Technote 1224568 et al), it is keyed to
the TSM client nodename; and, as the Nodename option doc says, where
no Nodename is set, the hostname determines the client identity for a
TSM session; and where the hostname changes with network position,
you have problems.  Thus, I wonder if these Macs lack a definite
Nodename defined in their client options (/Library/Preferences/Tivoli
Storage Manager/TSM System Preferences)?

It may well be more complex than that, but this is one area to inspect.

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



--
Paul ZarnowskiPh: 607-255-4757
Manager, Storage Services Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]


Réf. : Re: [ADSM-L] tape content with backup date

2006-06-26 Thread Vincent RATAJSZCZAK
Thank's Alexander for your help

Do you know a solution to have direct access to the TSM tables, or do I 
have to forget it ?

Any IBM tech guy around here to confirm if it is or not possible to get 
the results ?

Regards

Vince





Alexander Verkooijen <[EMAIL PROTECTED]>
Envoyé par : "ADSM: Dist Stor Manager" 
26/06/06 16:02
Veuillez répondre à "ADSM: Dist Stor Manager"

 
Pour :  ADSM-L@VM.MARIST.EDU
cc :(ccc : Vincent RATAJSZCZAK/INFOGER/GRT/FR)
Objet : Re: [ADSM-L] tape content with backup date


If you had access to the *real* tables that
reside in the TSM databse then, yes, it would
be possible. Since the SQL interface only
provides access to *pseudo* tables I don't
think it's possible.

Please correct me if I'm wrong. In the
past there have been times when I could have
used a list like this.

Regards,

Alexander


Alexander Verkooijen
Senior Systems Programmer
High Performance Computing
SARA Computing & Networking Services
 

> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 
> On Behalf Of Vincent RATAJSZCZAK
> Sent: donderdag 22 juni 2006 18:07
> To: ADSM-L@VM.MARIST.EDU
> Subject: tape content with backup date
> 
> Dear lovely TSM World,
> 
> I have a special request for you...
> 
> I would like to list the content of a specific tape (destroyed) with a
> column with the backuped date of the objet.
> 
> ==>   "Q content XXX" is poor
> 
> ==>   "select * from contents where volume_name=" give me
> Node_name/File_name, but no backuped date
> 
> ==>  "select * from backups" give me Node_name/File_name and backuped
> date, but no tape affectation
> 
> 
> Between the 2nd and 3rd, I can't find a common field to join 
> the tables
> 
> 
> Anyone could help me please ?
> 
> Do you think it's possible ?
> 
> The restore GUI show you the file name and backuped date, so 
> I think YES,
> but
> 
> Thank's
> 
> Vince
> 


Re: tape content with backup date

2006-06-26 Thread Alexander Verkooijen
If you had access to the *real* tables that
reside in the TSM databse then, yes, it would
be possible. Since the SQL interface only
provides access to *pseudo* tables I don't
think it's possible.

Please correct me if I'm wrong. In the
past there have been times when I could have
used a list like this.

Regards,

Alexander


Alexander Verkooijen
Senior Systems Programmer
High Performance Computing
SARA Computing & Networking Services
 

> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 
> On Behalf Of Vincent RATAJSZCZAK
> Sent: donderdag 22 juni 2006 18:07
> To: ADSM-L@VM.MARIST.EDU
> Subject: tape content with backup date
> 
> Dear lovely TSM World,
> 
> I have a special request for you...
> 
> I would like to list the content of a specific tape (destroyed) with a
> column with the backuped date of the objet.
> 
> ==>   "Q content XXX" is poor
> 
> ==>   "select * from contents where volume_name=" give me
> Node_name/File_name, but no backuped date
> 
> ==>  "select * from backups" give me Node_name/File_name and backuped
> date, but no tape affectation
> 
> 
> Between the 2nd and 3rd, I can't find a common field to join 
> the tables
> 
> 
> Anyone could help me please ?
> 
> Do you think it's possible ?
> 
> The restore GUI show you the file name and backuped date, so 
> I think YES,
> but
> 
> Thank's
> 
> Vince
> 


Re: Sleeping Macs and Failed TSM Backups

2006-06-26 Thread Richard Sims

I wonder if what's happening is that these personal computers are
gaining their network access via DHCP, wherein their network identity
is dynamic and can change upon renegotiation, as when the dormant
computer is awakened after some time.  As I understand TSM client
password encryption (per IBM Technote 1224568 et al), it is keyed to
the TSM client nodename; and, as the Nodename option doc says, where
no Nodename is set, the hostname determines the client identity for a
TSM session; and where the hostname changes with network position,
you have problems.  Thus, I wonder if these Macs lack a definite
Nodename defined in their client options (/Library/Preferences/Tivoli
Storage Manager/TSM System Preferences)?

It may well be more complex than that, but this is one area to inspect.

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