Re: the purpose of "file" device class

[Mehdi Salehi]

Hi,
What is the technical limitation of DISK in which something like reclamation
is no possible? We have filesystem fragmentation (in OS), FILE reclamation
but nothing for DISK pools. Why?

RPFiles are not being deleted

[John D. Schneider]

Greetings,
   We are running TSM 5.4.3.0 on a bunch of remote Windows TSM servers. 
Every day running their run of the Daily processing, they do a "PREPARE
DEVCL=MDCTSM02_CLASS" to send their prepare output to another TSM server
called "mdctsm02", which is in a distant city. This city is the DR site
for these remote sites.  It is also running 5.4.3.0, under AIX 5.3ML6.
   One thing I just noticed is that TSM does not seem to be removing old
versions of the RPFiles.  Please look at the output below:

tsm: HTSP-TSM1_SERVER1>q rpfile devcl=mdctsm02_class

Recovery Plan File Name   Node Name   Device Class
Name
  -- 

MDCTSM02.20070804.070832  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20080611.064125  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20080612.064036  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090412.063058  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090818.064350  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090819.064419  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090820.064440  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090821.070724  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090822.064907  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090823.070331  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090824.064010  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090825.064900  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090826.064517  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090827.064811  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090828.065536  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090829.064838  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090830.063943  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090831.064027  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090901.064827  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090902.064823  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090903.064508  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090904.065014  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090905.065024  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090906.064003  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090907.064032  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090908.064453  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090909.064551  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090910.064847  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090911.065003  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090912.064854  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090913.064845  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090914.064819  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090915.064653  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090916.065214  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090917.064727  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090918.064940  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090919.064905  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090920.064241  HTSP-TSM1_SERVER1   MDCTSM02_CLASS
MDCTSM02.20090921.064327  HTSP-TSM1_SERVER1   MDCTSM02_CLASS

tsm: HTSP-TSM1_SERVER1>q drmstatus

  Recovery Plan Prefix:
  Plan Instructions Prefix:
Replacement Volume Postfix: @
 Primary Storage Pools: TAPEPOOL
Copy Storage Pools: COPYPOOL
   Not Mountable Location Name: NOTMOUNTABLE
  Courier Name: COURIER
   Vault Site Name: VAULT
  DB Backup Series Expiration Days: 5 Day(s)
Recovery Plan File Expiration Days: 5 Day(s)
  Check Label?: No
 Process FILE Device Type?: No
 Command File Name:


tsm: HTSP-TSM1_SERVER1>
tsm: HTSP-TSM1_SERVER1>delete volhist todate=-14 type=rpfile

Do you wish to proceed? (Yes (Y)/No (N)) y
ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
successfully deleted.


Even when I manually issue a 'delete volhist' command, the old plan
files are not being deleted.  At first I thought that I was
misunderstanding the action for 'delete vohist type=rpfile', but I also
issued the same command from the target server mdctsm02, and I got the
same result.  They are not being deleted. 

Can anyone explain to me what I am doing wrong?

Best Regards,
 
 John D. Schneider
 The Computer Coaching Community, LLC
 Office: (314) 635-5424 / Toll Free: (866) 796-9226
 Cell: (314) 750-8721

Re: RHEL5-2.6.18.96 - Lin_tape 1.24-Sandiscovery wont work

[David E Ehresman]

I don't know but . . .

I was just looking at the lin_tape downloads and there is a 
lin_tape-1.27.0-1.src.rpm.bin dated 09/03/2009.

David



>>> janecb01  9/17/2009 3:42 PM >>>
Hi,

I have compiled the latest Lin_tape and installed lin_taped on my Linux RHEL5 
server.. I am using a Netapp Nearstor VTL emulating IBM LTO4 drives. 
Sandiscovery will not work, and at best will crash the system every few hours 
or so unless it is turned off - / or set to PASSIVE. When I scan the system, 
the drives are dicovered and connected to the lin_tape driver:
lin_tape: detected device at host 1, channel 0, id 0, lun 1
IBM ULTRIUM-TD4 022C
lin_tape: successfully attached IBMtape0
lin_tape: detected device at host 1, channel 0, id 0, lun 2
IBM ULTRIUM-TD4 022C
lin_tape: successfully attached IBMtape1
lin_tape: detected device at host 1, channel 0, id 0, lun 3

but as soon as tapes start loading we get various errors:
lin_tape: IBMtape2051868 tape_logsense_page() unable to do log sense
lin_tape: IBMtape2051868 tape_logsense_page() unable to do log sense
lin_tape: IBMChgr1-80401 changer_check_result() sensekey: 6 asc: 28 ascq: 0
lin_tape: IBMtape19b4fb0 tape_set_all_parms() unable to change recovery 
timeouts

The crashing has become very annoying - IBM recommends a QLogic hba driver that 
is not supported by QLogic or RHEL5 (8.01.06) We have 8.02.23 - but that might 
not be related.

IBM has been studying the information for a while now.. but this is getting 
very frustrated. The lin_tape compiled without error for my kernel.

Sandiscovery will not adjust the devices as it does on AIX perfectly..

Any suggestions or help would be greatly appreciated.

Jane

+--
|This was sent by jane_c_bamber...@keybank.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: ANR8214E Session open with xx.xx.xx.xx failed due to connection refusal

[Efim]

It looks like problem with correct node parameters in TSM server. Of course
you can change HL and LL address in node definition, but often in doesn't
help.
Try to change in dsm.opt option to schedmode polling and run "shot" backup
(sel c:\autoexec.bat) using clientaction.
After backup successful completed , change it back to schedmode prompted.
(the best way to do this - use clopset).
Don't forget restart TSM scheduler after each change if you don't use CAD or
cloptset.
--
Efim

Re: the purpose of "file" device class

[Shawn Drew]

I resisted including this, because only one session can actually write to
the volume, but many can read from it.  This is mainly for restore
performance.
It still doesn't address the queueing issue.  For sequential files,
multi-session write access would introduce multi-plexed data streams.  I
much prefer migration from random access disk if the alternative is
long-term storage in a multi-plexed format.  (bad netbackup memories)

Backing up directly to sequential devices makes sense for large
files/nodes.  However, we have hundreds of machines that only back up a
few GB per night.  Random access disk is best for this.  The "Max size
threshold"  is ideal for controlling this.

I really believe the disk and file devices are complements and not
competitors.  I bet IBM is developing file devices heavily because it is
relatively new and not mature. I don't believe they are trying to supplant
disk devices. The real file-device competitor is VTL and those are the
features that IBM is pursuing (deduplication, etc)
I don't think random-access disk is going anywhere.

Regards,
Shawn

Shawn Drew





Internet
t...@networkc.co.uk

Sent by: ADSM-L@VM.MARIST.EDU
09/21/2009 11:51 AM
Please respond to
ADSM-L@VM.MARIST.EDU


To
ADSM-L
cc

Subject
Re: [ADSM-L] the purpose of "file" device class






Just to be uber-picky, FILE volumes now do allow multiple
sessions/processes
to read/write concurrently to a single FILE volume from TSM 5.5 onwards
(
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmms

munn.doc/anrsgd5515.htm#wq28).

The big picture as I've read it is that IBM are perhaps angling the
user-base towards using FILE volumes, and that new developments would be
implemented against FILE technology rather than DISK. That being said,
it's
fair to say that many people are simply more comfortable with the ease,
simplicity and habit of implementing and managing DISK volumes.

/DMc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Shawn Drew
Sent: 21 September 2009 15:58
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] the purpose of "file" device class

Disk Based (Random access) lets you have several sessions all sending data
to it.  This removes the need to queue backups like all the competitors.
But it will fragment as data expires and there is no defrag for random
access.

File devices (Sequential access) do also fragment over time, just like
tape, but you are able to run reclamation on them.  But sequential access
would cause queuing.
They each have different pro's and con's which make them suited for
different tasks.  (long term vs short term storage)

Regards,
Shawn

Shawn Drew


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or
partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that
certain
functions and services for BNP Paribas may be performed by BNP Paribas
RCC,
Inc.

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.109/2384 - Release Date:
09/20/09
06:22:00

Re: the purpose of "file" device class

[Kelly Lipp]

During Oxford 2005, IBM stated that the File Device Class is the strategic data 
structure.  One can see this in action with the dedup functionality in V6.

Our products use DISK for cachepool usually deployed on JBOD arranged FAST disk 
(SAS or FC at 15K) as the initial target for client backups, particularly for 
large numbers of clients with small data movement.

File Device class is used for large amounts of storage (since we can have 
reclamation there).  Our pools are targeted by clients moving a lot of data 
daily, or are the target of migration from the cachepool.

I think both are still valid for the reasons already described but in the long 
run DISK may go the way of the dinosaur.

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of David 
McClelland
Sent: Monday, September 21, 2009 9:52 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] the purpose of "file" device class

Just to be uber-picky, FILE volumes now do allow multiple sessions/processes
to read/write concurrently to a single FILE volume from TSM 5.5 onwards
(http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmms
munn.doc/anrsgd5515.htm#wq28).

The big picture as I've read it is that IBM are perhaps angling the
user-base towards using FILE volumes, and that new developments would be
implemented against FILE technology rather than DISK. That being said, it's
fair to say that many people are simply more comfortable with the ease,
simplicity and habit of implementing and managing DISK volumes.

/DMc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Shawn Drew
Sent: 21 September 2009 15:58
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] the purpose of "file" device class

Disk Based (Random access) lets you have several sessions all sending data
to it.  This removes the need to queue backups like all the competitors.
But it will fragment as data expires and there is no defrag for random
access.

File devices (Sequential access) do also fragment over time, just like
tape, but you are able to run reclamation on them.  But sequential access
would cause queuing.
They each have different pro's and con's which make them suited for
different tasks.  (long term vs short term storage)

Regards,
Shawn

Shawn Drew


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that
certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC,
Inc.

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.109/2384 - Release Date: 09/20/09
06:22:00

Re: the purpose of "file" device class

[David McClelland]

Just to be uber-picky, FILE volumes now do allow multiple sessions/processes
to read/write concurrently to a single FILE volume from TSM 5.5 onwards
(http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmms
munn.doc/anrsgd5515.htm#wq28).

The big picture as I've read it is that IBM are perhaps angling the
user-base towards using FILE volumes, and that new developments would be
implemented against FILE technology rather than DISK. That being said, it's
fair to say that many people are simply more comfortable with the ease,
simplicity and habit of implementing and managing DISK volumes.

/DMc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Shawn Drew
Sent: 21 September 2009 15:58
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] the purpose of "file" device class

Disk Based (Random access) lets you have several sessions all sending data
to it.  This removes the need to queue backups like all the competitors.
But it will fragment as data expires and there is no defrag for random
access.

File devices (Sequential access) do also fragment over time, just like
tape, but you are able to run reclamation on them.  But sequential access
would cause queuing.
They each have different pro's and con's which make them suited for
different tasks.  (long term vs short term storage)

Regards,
Shawn

Shawn Drew


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that
certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC,
Inc.

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.109/2384 - Release Date: 09/20/09
06:22:00

Re: the purpose of "file" device class

[Mehdi Salehi]

Thanks so much

Re: the purpose of "file" device class

[Shawn Drew]

Disk Based (Random access) lets you have several sessions all sending data
to it.  This removes the need to queue backups like all the competitors.
But it will fragment as data expires and there is no defrag for random
access.

File devices (Sequential access) do also fragment over time, just like
tape, but you are able to run reclamation on them.  But sequential access
would cause queuing.
They each have different pro's and con's which make them suited for
different tasks.  (long term vs short term storage)

Regards,
Shawn

Shawn Drew


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

Re: VCB Documentation?

[Remco Post]

On 21 sep 2009, at 15:57, Wanda Prather wrote:


You'll find good planning info and detailed setup instructions in
the TSM
5.4-5.5 Technical Guide redbook, SG24-7447, chapter 24.  Download from
www.redbooks.ibm.com.



speaking of redbooks, has anybody heard of the 6.1 redbook? I know
there was an internship for it, I've just not heard of any results

--

Met vriendelijke groeten/Kind regards,

Remco Post

Re: Server systemstate restore

[Huebner,Andy,FORT WORTH,IT]

Oddly we ran into something very similar last week.  Check for the existence of 
patch KB940349.  This is a VSS patch that changes the format of the XML that 
VSS uses.  The target OS will need it installed if the source did.

Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Tim 
Brown
Sent: Monday, September 21, 2009 7:12 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Server systemstate restore

Error during restore of Windows systemstate
Any ideas what causes this.

We are in the process of restoring a server, the C: drive was restored first
then an attempt was made to restore the system state. We also have copy of the
systemstate produced via NTBACKUP.

09/21/2009 07:59:00 ANS5250E An unexpected error was encountered.
   TSM function name : VssRequestor::initializeForRestore
   TSM function  : InitializeForRestore() from file 
'\\modi\c$\adsm.sys\vss_staging\MODI\10.1.10.8\20090830203047\TSM_Backup.xml' 
returned VSS_E_INVALID_XML_DOCUMENT
   TSM return code   : 4341
   TSM file  : vssreq.cpp (5391)
09/21/2009 07:59:00 ANS5250E An unexpected error was encountered.
   TSM function name : vssInitRestSpec
   TSM function  : InitializeVss() returned '4341'
   TSM return code   : 4341
   TSM file  : vssrest.cpp (723)
09/21/2009 07:59:00 ANS1949E Microsoft volume shadow copy snapshot 
initialization failed.

Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com 
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255


This message contains confidential information and is only for the intended 
recipient.  If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, please notify the sender immediately by replying to this note and 
deleting all copies and attachments.  Thank you.


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.

Re: VCB Documentation?

[Wanda Prather]

You'll find good planning info and detailed setup instructions in the TSM
5.4-5.5 Technical Guide redbook, SG24-7447, chapter 24.  Download from
www.redbooks.ibm.com.

Note however that it only covers the TSM 5.5 functions, which did not fully
support fullvm backups.
The 6.1 client includes support for fullvm backups, so you want to use the
6.1 client (works fine with 5.5 server), and there is a bit more info about
that function in the 6.1 Windows client manual, chap. 4 (just search on
VCB).

W

On Mon, Sep 21, 2009 at 5:12 AM, Christian Svensson <
christian.svens...@cristie.se> wrote:

> Hi,
> Does anyone know any good documentation how to setup and design a VCB/TSM
> backup?
> I search around on IBM website and did only find a really small redbook
> about it. :(
>
>
>
> Best Regards
> Christian Svensson
>
> Cell: +46-70-325 1577
> E-mail: christian.svens...@cristie.se
> Skype: cristie.christian.svensson

Re: Server systemstate restore

[Andrew Raibeck]

Go to the URL in my sig (which you should have bookmarked) and try a
search. The VSS_E_INVALID_XML_DOCUMENT is a good place to start. :-)

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/i...@ibmus
Internet e-mail: stor...@us.ibm.com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html


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

"ADSM: Dist Stor Manager"  wrote on 09/21/2009
08:12:06 AM:

> [image removed]
>
> Server systemstate restore
>
> Tim Brown
>
> to:
>
> ADSM-L
>
> 09/21/2009 08:11 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" 
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Error during restore of Windows systemstate
> Any ideas what causes this.
>
> We are in the process of restoring a server, the C: drive was restored
first
> then an attempt was made to restore the system state. We also have copy
of the
> systemstate produced via NTBACKUP.
>
> 09/21/2009 07:59:00 ANS5250E An unexpected error was encountered.
>TSM function name : VssRequestor::initializeForRestore
>TSM function  : InitializeForRestore() from file '\\modi\c$
> \adsm.sys\vss_staging\MODI\10.1.10.8\20090830203047\TSM_Backup.xml'
> returned VSS_E_INVALID_XML_DOCUMENT
>TSM return code   : 4341
>TSM file  : vssreq.cpp (5391)
> 09/21/2009 07:59:00 ANS5250E An unexpected error was encountered.
>TSM function name : vssInitRestSpec
>TSM function  : InitializeVss() returned '4341'
>TSM return code   : 4341
>TSM file  : vssrest.cpp (723)
> 09/21/2009 07:59:00 ANS1949E Microsoft volume shadow copy snapshot
> initialization failed.
>
> Tim Brown
> Systems Specialist - Project Leader
> Central Hudson Gas & Electric
> 284 South Ave
> Poughkeepsie, NY 12601
> Email: tbr...@cenhud.com 
> Phone: 845-486-5643
> Fax: 845-486-5921
> Cell: 845-235-4255
>
>
> This message contains confidential information and is only for the
> intended recipient.  If the reader of this message is not the
> intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, please notify the
> sender immediately by replying to this note and deleting all copies
> and attachments.  Thank you.

Re: ANR8214E Session open with xx.xx.xx.xx failed due to connection refusal

[Richard Sims]

Your posting doesn't specify the manner in which scheduling is
configured on that client.  If it is CAD-based, have a look at the
dsmwebcl.log for problem indications.

Beyond that, see that message number in http://people.bu.edu/rbs/ADSM.QuickFacts
 for other causes we've seen.

   Richard Sims

Server systemstate restore

[Tim Brown]

Error during restore of Windows systemstate
Any ideas what causes this.

We are in the process of restoring a server, the C: drive was restored first
then an attempt was made to restore the system state. We also have copy of the
systemstate produced via NTBACKUP.

09/21/2009 07:59:00 ANS5250E An unexpected error was encountered.
   TSM function name : VssRequestor::initializeForRestore
   TSM function  : InitializeForRestore() from file 
'\\modi\c$\adsm.sys\vss_staging\MODI\10.1.10.8\20090830203047\TSM_Backup.xml' 
returned VSS_E_INVALID_XML_DOCUMENT
   TSM return code   : 4341
   TSM file  : vssreq.cpp (5391)
09/21/2009 07:59:00 ANS5250E An unexpected error was encountered.
   TSM function name : vssInitRestSpec
   TSM function  : InitializeVss() returned '4341'
   TSM return code   : 4341
   TSM file  : vssrest.cpp (723)
09/21/2009 07:59:00 ANS1949E Microsoft volume shadow copy snapshot 
initialization failed.

Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com 
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255


This message contains confidential information and is only for the intended 
recipient.  If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, please notify the sender immediately by replying to this note and 
deleting all copies and attachments.  Thank you.

ANR8214E Session open with xx.xx.xx.xx failed due to connection refusal

[Danny Blair]

 All,

We have a node that is failing nightly with the error:
"ANR8214E Session open with xx.xx.xx.xx failed due to connection refusal"
 (this error is seen on the tivoli server)
I see nothing in the error log or the sched log. I can, however, initiate a
backup manually from the client node and it works no problem.
This node is running 5.3.2 (our server is 5.5.2). I see nothing in the event
log for the problem node and there is no firewall. The client node is a VM
server running windows server 2003, traceroute looks fine. Have you ever
seen anything like this? This happened out of the blue (nothing changed on
the server that I know of) and continues to miss over the past 2 weeks.

Thanks in advance for any advice/help/solutions!

Re: the purpose of "file" device class

[km]

On 21/09, Mehdi Salehi wrote:
> Hi,
> What is actually the different between a disk pool and a file pool? Both are
> based on disks and the latter behaves sequentially like tapes. What makes
> necessary to have these two types of pools in TSM? Couldn't IBM eliminate
> one of them and say that there is only one disk-based pool?
>
> Thanks

DISK storage pools are prone to fragmentation which FILE stgpools are
not (if you pre-allocate volumes).

DISK storagepools are therefore used as intermediary storage whereas FILE
stgpools are more of a replacement for tape to mitigate tape mount times
and number of mount points, think VTL.

I would hazard a guess that architectural differences are described more
in detail in a redbook, maybe the TSM concepts guide or the TSM technical
guide.

-km

the purpose of "file" device class

[Mehdi Salehi]

Hi,
What is actually the different between a disk pool and a file pool? Both are
based on disks and the latter behaves sequentially like tapes. What makes
necessary to have these two types of pools in TSM? Couldn't IBM eliminate
one of them and say that there is only one disk-based pool?

Thanks

VCB Documentation?

[Christian Svensson]

Hi,
Does anyone know any good documentation how to setup and design a VCB/TSM 
backup?
I search around on IBM website and did only find a really small redbook about 
it. :(



Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
Skype: cristie.christian.svensson