Re: restore question

2011-05-11 Thread Huebschman, George J.
It sounds as though an older version of a file was restored, then later
a newer version of the same file was attempted.
Were you doing a Point in Time restore?


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Jeannie Bruno
Sent: Wednesday, May 11, 2011 10:21 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] restore question

Hello.  Wondering if anyone else has ever seen this scenario:

We had a 2003 windows server that died last week.   Got a new 2008
server this week.  Did the restore for the 'user' drive for all their
data.  (Used the TSM gui to do the restore.  TSM client version 6.1.2).
But during the restore about 4 hours into it, we got the prompt to
'replace the existing file?' message for one of the files that was being
restored.

Now because this is a brand new server that never had any user data on
it, why would we get prompted this message?

Before we started the restore, we did not choose any of the restore
options for the replacing,etc, because it was a brand new server, i
didn't think this was necessary to do.

anyone know why this happened??
thanks.


Jeannie Bruno
Systems Analyst
jbr...@cenhud.com
284 South Ave.
Poughkeepsie, NY 12601
845-486-5780

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.

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.


Re: restore question

2011-05-11 Thread Prather, Wanda
Happens rarely, but I've seen it before.  Freaked me out.

Has to do with how Windows creates the under-the-covers 8.3 DOS file names.
TSM backs up and catalogs the filenames with the long-name version, but when it 
restores the file, NTFS will still create the 8.3 filenames by default.

Here's how it can happen:
Suppose you have files called 
whoop~1.txt 
whoopee2001.txt

If whoopee2001.txt gets restored first (totally by accident), NTFS will create 
the short name whoop~1.txt for it. Then when it tries to restore whoop~1.txt, 
you get the error message you saw, i.e. a file name clash.  (And as I recall, 
the error message may use the long file name, so it's not necessarily apparent 
what the problem is.)

You have to have files of just the right names, just the right length names, in 
the same directory, and an accident of restore order to make it happen, so you 
rarely see it.  (It's most likely to occur in directories where files are 
generated by a software package where some developer has brilliantly decided to 
use a lot of ~ in the generated filenames, so you may be able to identify 
exactly which directory has the issue.)

Simple solutions: 

-If it only happens on 1 or 2 files, be confident that TSM is OK, write the 
file name down.  After you've finished the big restore, go back and find those 
files in TSM and restore them to different directories, then drag them back to 
where they belong.  

-If it happens a lot and you are nervous about the results, or your restore 
needs to run a long time unattended, you can disable Windows NTFS 8.3 name 
creation, run your restore, then re-enable the NTFS 8.3 name creation.  (The 
downside of that is if you have users that for some reason regularly refer to 
the short 8.3 form of the file name -- again most likely program developers -- 
they may have some patching to do after the restore.)

Here are references that may explain it better and help you determine if this 
is your problem.  The MS article has instructions for turning off 8.3 filename 
creation:  
  
https://www-304.ibm.com/support/docview.wss?uid=swg21304777
https://www-304.ibm.com/support/docview.wss?uid=swg1IC45443
http://support.microsoft.com/kb/121007



http://support.microsoft.com/kb/121007

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Jeannie Bruno
Sent: Wednesday, May 11, 2011 10:21 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] restore question

Hello.  Wondering if anyone else has ever seen this scenario:

We had a 2003 windows server that died last week.   Got a new 2008 server this 
week.  Did the restore for the 'user' drive for all their data.  (Used the TSM 
gui to do the restore.  TSM client version 6.1.2).
But during the restore about 4 hours into it, we got the prompt to 'replace the 
existing file?' message for one of the files that was being restored.

Now because this is a brand new server that never had any user data on it, why 
would we get prompted this message?

Before we started the restore, we did not choose any of the restore options for 
the replacing,etc, because it was a brand new server, i didn't think this was 
necessary to do.

anyone know why this happened??  
thanks.


Jeannie Bruno   
Systems Analyst
jbr...@cenhud.com
284 South Ave.
Poughkeepsie, NY 12601
845-486-5780
 
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: restore question

2011-05-11 Thread Jeannie Bruno

thanks!
Our tech support didn't write down the file name and I believe it was only 1
file, but I will ask if he happens to remember the name.
And I will check out those sites.

- Original Message -
From: Prather, Wanda wprat...@icfi.com
To: ADSM-L@VM.MARIST.EDU
Sent: Wednesday, May 11, 2011 12:32 PM
Subject: Re: [ADSM-L] restore question


Happens rarely, but I've seen it before.  Freaked me out.

Has to do with how Windows creates the under-the-covers 8.3 DOS file names.
TSM backs up and catalogs the filenames with the long-name version, but when
it restores the file, NTFS will still create the 8.3 filenames by default.

Here's how it can happen:
Suppose you have files called
whoop~1.txt
whoopee2001.txt

If whoopee2001.txt gets restored first (totally by accident), NTFS will
create the short name whoop~1.txt for it. Then when it tries to restore
whoop~1.txt, you get the error message you saw, i.e. a file name clash.
(And as I recall, the error message may use the long file name, so it's not
necessarily apparent what the problem is.)

You have to have files of just the right names, just the right length names,
in the same directory, and an accident of restore order to make it happen,
so you rarely see it.  (It's most likely to occur in directories where files
are generated by a software package where some developer has brilliantly
decided to use a lot of ~ in the generated filenames, so you may be able to
identify exactly which directory has the issue.)

Simple solutions:

-If it only happens on 1 or 2 files, be confident that TSM is OK, write the
file name down.  After you've finished the big restore, go back and find
those files in TSM and restore them to different directories, then drag them
back to where they belong.

-If it happens a lot and you are nervous about the results, or your restore
needs to run a long time unattended, you can disable Windows NTFS 8.3 name
creation, run your restore, then re-enable the NTFS 8.3 name creation.  (The
downside of that is if you have users that for some reason regularly refer
to the short 8.3 form of the file name -- again most likely program
developers -- they may have some patching to do after the restore.)

Here are references that may explain it better and help you determine if
this is your problem.  The MS article has instructions for turning off 8.3
filename creation:

https://www-304.ibm.com/support/docview.wss?uid=swg21304777
https://www-304.ibm.com/support/docview.wss?uid=swg1IC45443
http://support.microsoft.com/kb/121007



http://support.microsoft.com/kb/121007

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Jeannie Bruno
Sent: Wednesday, May 11, 2011 10:21 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] restore question

Hello.  Wondering if anyone else has ever seen this scenario:

We had a 2003 windows server that died last week.   Got a new 2008 server
this week.  Did the restore for the 'user' drive for all their data.  (Used
the TSM gui to do the restore.  TSM client version 6.1.2).
But during the restore about 4 hours into it, we got the prompt to 'replace
the existing file?' message for one of the files that was being restored.

Now because this is a brand new server that never had any user data on it,
why would we get prompted this message?

Before we started the restore, we did not choose any of the restore options
for the replacing,etc, because it was a brand new server, i didn't think
this was necessary to do.

anyone know why this happened??
thanks.


Jeannie Bruno
Systems Analyst
jbr...@cenhud.com
284 South Ave.
Poughkeepsie, NY 12601
845-486-5780

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: Restore question

2010-06-15 Thread Skylar Thompson

I think you'll want to look at GRANT PROXYNODE, using it to grant
access to the powered-off node's (say NODE_A) backups to another system
that's still online (NODE_B). After running that command on the TSM
server, you would login to NODE_B and do dsmc restore -asnode=NODE_A
/path/to/file.

On 06/15/10 07:01, Avy Wong wrote:

Hello,
Is it possible to restore a file from the backups of a box that is
powered off? The old node is still registered on tivoli, it has not been
removed yet and subsequently all its backups. They want the file to be
restored into the new box.  I appreciate your help.


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976


The information contained in this message may be privileged and confidential 
and protected from disclosure. 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, you are hereby notified that any 
dissemination, distribution, or copy of this communication is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by replying to the message and deleting it from your computer.



--
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S048, (206)-685-7354
-- University of Washington School of Medicine


Re: Restore question

2010-06-15 Thread Thorneycroft, Doug
You can start dsm or dsmc using the virtualnodename option to run as the
powered off node
dsmc -virtualnodename=Nodename -password=password

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Avy Wong
Sent: Tuesday, June 15, 2010 7:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Restore question

Hello,
   Is it possible to restore a file from the backups of a box that
is
powered off? The old node is still registered on tivoli, it has not been
removed yet and subsequently all its backups. They want the file to be
restored into the new box.  I appreciate your help.


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976


The information contained in this message may be privileged and
confidential and protected from disclosure. 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, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.


Re: Restore question

2010-06-15 Thread Schneider, Jim
I have found it easier to start a command line or gui session using the
'virtualnodename' parameter.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Skylar Thompson
Sent: Tuesday, June 15, 2010 9:06 AM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Restore question

I think you'll want to look at GRANT PROXYNODE, using it to grant
access to the powered-off node's (say NODE_A) backups to another system
that's still online (NODE_B). After running that command on the TSM
server, you would login to NODE_B and do dsmc restore -asnode=NODE_A
/path/to/file.

On 06/15/10 07:01, Avy Wong wrote:
 Hello,
 Is it possible to restore a file from the backups of a box
that is
 powered off? The old node is still registered on tivoli, it has not
been
 removed yet and subsequently all its backups. They want the file to be
 restored into the new box.  I appreciate your help.


 Avy Wong
 Business Continuity Administrator
 Mohegan Sun
 1 Mohegan Sun Blvd
 Uncasville, CT 06382
 (860)862-8164
 (cell) (860)961-6976


 The information contained in this message may be privileged and
confidential and protected from disclosure. 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, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.


--
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S048, (206)-685-7354
-- University of Washington School of Medicine


Re: Restore question

2010-06-15 Thread Avy Wong
Thanks Skyler and Doug for your suggestions. I did a grant proxynode, then
simply change the nodename in the dsmopt to point to the target node, then
I see all the backups of the target node. Thanks both for helping.

i.e
grant proxynode target=nascluster agent=moe,joe

Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976




 Thorneycroft,
 Doug
 dthorneycr...@la  To
 CSD.ORG  ADSM-L@VM.MARIST.EDU
 Sent by: ADSM:cc
 Dist Stor
 Manager  Subject
 ads...@vm.marist Re: [ADSM-L] Restore question
 .EDU


 06/15/2010 10:12
 AM


 Please respond to
 ADSM: Dist Stor
 Manager
 ads...@vm.marist
   .EDU






You can start dsm or dsmc using the virtualnodename option to run as the
powered off node
dsmc -virtualnodename=Nodename -password=password

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Avy Wong
Sent: Tuesday, June 15, 2010 7:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Restore question

Hello,
   Is it possible to restore a file from the backups of a box that
is
powered off? The old node is still registered on tivoli, it has not been
removed yet and subsequently all its backups. They want the file to be
restored into the new box.  I appreciate your help.


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976


The information contained in this message may be privileged and
confidential and protected from disclosure. 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, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.




The information contained in this message may be privileged and confidential 
and protected from disclosure. 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, you are hereby notified that any 
dissemination, distribution, or copy of this communication is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by replying to the message and deleting it from your computer.


Re: Restore question

2010-06-15 Thread Richard Sims
It's a Bad Idea to change your nodename in the options file, as that can have 
side effects.
To perform cross-node operations, follow the instructions provided in the 
client manual.

  Richard Sims


Re: Restore question

2010-06-15 Thread Avy Wong
Just curious Richard, what are the side effects? It is a one time thing and
at the time I was working with and IBM with a PMR number, she did give me a
document to follow it, but also suggests a quick way to do it is put the
nodename to point to the target node on the dsm.opt, of course whatever it
was, make sure changing it back.

Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976


The information contained in this message may be privileged and confidential 
and protected from disclosure. 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, you are hereby notified that any 
dissemination, distribution, or copy of this communication is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by replying to the message and deleting it from your computer.


Re: Restore question

2010-06-15 Thread Richard Sims
On Jun 15, 2010, at 1:13 PM, Avy Wong wrote:

 Just curious Richard, what are the side effects? It is a one time thing and
 at the time I was working with and IBM with a PMR number, she did give me a
 document to follow it, but also suggests a quick way to do it is put the
 nodename to point to the target node on the dsm.opt, of course whatever it
 was, make sure changing it back.

A TSM Support representative should not suggest doing things like that.  The 
effects are summarized in ADSM QuickFacts.
Remember that the TSM server tracks the network address used by a client, which 
at a minimum can obliterate prior record of where on the network a client was.  
The nodename is also used for storing the access password on the client.  Given 
that all systems these days are multi-user, it's all too easy for some other 
person on the system to perform a backup while the other nodename is in place, 
with all the obvious ramifications.  Someone trying to retrieve or restore data 
while the other nodename is in place is going to run into problems.  A 
happenstance backup from a node-appropriated client whose software happened to 
at a higher level that the original nodename can render storage pool data no 
longer accessible to the original nodename.
This is why VIRTUALNodename is provided.

Richard Simshttp://people.bu.edu/rbs/


Re: Restore question

2010-06-15 Thread Avy Wong
OK Richard. I will dig deep and learn more about this. Thanks.

Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976


The information contained in this message may be privileged and confidential 
and protected from disclosure. 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, you are hereby notified that any 
dissemination, distribution, or copy of this communication is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by replying to the message and deleting it from your computer.


Re: Restore Question

2009-02-06 Thread Otto Chvosta

Andrew Raibeck schrieb:

Craig, I recommend you take a look at this flash that went out around end
of October last year, to see if it applies:

http://www.ibm.com/support/docview.wss?uid=swg21322625

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/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 ADSM-L@VM.MARIST.EDU wrote on 02/04/2009
10:36:38 PM:



[image removed]

Restore Question

Craig Ross

to:

ADSM-L

02/04/2009 10:37 PM

Sent by:

ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU

Please respond to ADSM: Dist Stor Manager

I have an annoying issue.
I have never encountered this before.

I have 6 files, three the same, all deactivated.

TSM client states the files are this large.  Which is correct.

tsm q backup -ina D:\data\SHARED\Systems Operating Centre\Systems
Management C
entre\Server Team - Unix\password-safe-db\*
   SizeBackup DateMgmt Class A/I
File
   ----- ---

 *9,224 * *B*  09-01-2009 21:37:40 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.ibak
*13,784 * *B*  13-01-2009 21:24:00 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.ibak
* 9,224*  *B*  09-01-2009 21:37:40 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3
*13,784*  *B*  13-01-2009 21:24:00 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3
*48*  *B*  09-01-2009 21:37:41 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3.plk
*48*  *B*  16-01-2009 22:10:24 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3.plk


Problem is once the files are restored the files are all either 0 K or 1


KB


in size.  empty files

Restore complete with no error.
There are no errors in Act log for the backup run at these times.

Has anyone ever seen these behavior before???

Thanks everyone.

Craig





Unfortunately the only way to find out which objects are affected ist to
check the logs to find objects that growed during compression and
restore/retrieve them to a different location to see the actual filesize
! And that for all client levels since 5.4.2.0 (rel. March 2008) up to
5.5.1.0

Maybe hard work if you're looking for possible affected objects and an
inactive  good copy of them.

We randomly tested out some growing objects backed up whith different
client levels and found NO bad copies. But I'm sure bad copies are out
there ...

Regards,
Otto


Re: Restore Question

2009-02-05 Thread Andrew Raibeck
Craig, I recommend you take a look at this flash that went out around end
of October last year, to see if it applies:

http://www.ibm.com/support/docview.wss?uid=swg21322625

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/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 ADSM-L@VM.MARIST.EDU wrote on 02/04/2009
10:36:38 PM:

 [image removed]

 Restore Question

 Craig Ross

 to:

 ADSM-L

 02/04/2009 10:37 PM

 Sent by:

 ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU

 Please respond to ADSM: Dist Stor Manager

 I have an annoying issue.
 I have never encountered this before.

 I have 6 files, three the same, all deactivated.

 TSM client states the files are this large.  Which is correct.

 tsm q backup -ina D:\data\SHARED\Systems Operating Centre\Systems
 Management C
 entre\Server Team - Unix\password-safe-db\*
SizeBackup DateMgmt Class A/I
 File
----- ---
 
  *9,224 * *B*  09-01-2009 21:37:40 DEFAULT
 I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
 Centre\Server
  Team - Unix\Password-Safe-DB\prod_unix.ibak
 *13,784 * *B*  13-01-2009 21:24:00 DEFAULT
 I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
 Centre\Server
  Team - Unix\Password-Safe-DB\prod_unix.ibak
 * 9,224*  *B*  09-01-2009 21:37:40 DEFAULT
 I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
 Centre\Server
  Team - Unix\Password-Safe-DB\prod_unix.psafe3
 *13,784*  *B*  13-01-2009 21:24:00 DEFAULT
 I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
 Centre\Server
  Team - Unix\Password-Safe-DB\prod_unix.psafe3
 *48*  *B*  09-01-2009 21:37:41 DEFAULT
 I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
 Centre\Server
  Team - Unix\Password-Safe-DB\prod_unix.psafe3.plk
 *48*  *B*  16-01-2009 22:10:24 DEFAULT
 I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
 Centre\Server
  Team - Unix\Password-Safe-DB\prod_unix.psafe3.plk


 Problem is once the files are restored the files are all either 0 K or 1
KB
 in size.  empty files

 Restore complete with no error.
 There are no errors in Act log for the backup run at these times.

 Has anyone ever seen these behavior before???

 Thanks everyone.

 Craig


Re: Restore Question

2009-02-05 Thread Craig TSM

Hi Andy,

I am currently at home so I cannot 100% confirm my compression settings,
but those symptoms read exactly what I am seeing.
Andy thanks for the detail.

These kind of 'features' really start to hurt customers.

Cheers   (I think)


Andrew Raibeck wrote:

Craig, I recommend you take a look at this flash that went out around end
of October last year, to see if it applies:

http://www.ibm.com/support/docview.wss?uid=swg21322625

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/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 ADSM-L@VM.MARIST.EDU wrote on 02/04/2009
10:36:38 PM:



[image removed]

Restore Question

Craig Ross

to:

ADSM-L

02/04/2009 10:37 PM

Sent by:

ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU

Please respond to ADSM: Dist Stor Manager

I have an annoying issue.
I have never encountered this before.

I have 6 files, three the same, all deactivated.

TSM client states the files are this large.  Which is correct.

tsm q backup -ina D:\data\SHARED\Systems Operating Centre\Systems
Management C
entre\Server Team - Unix\password-safe-db\*
   SizeBackup DateMgmt Class A/I
File
   ----- ---

 *9,224 * *B*  09-01-2009 21:37:40 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.ibak
*13,784 * *B*  13-01-2009 21:24:00 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.ibak
* 9,224*  *B*  09-01-2009 21:37:40 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3
*13,784*  *B*  13-01-2009 21:24:00 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3
*48*  *B*  09-01-2009 21:37:41 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3.plk
*48*  *B*  16-01-2009 22:10:24 DEFAULT
I  \\blah\d$\data\SHARED\Systems Operating Centre\Systems Management
Centre\Server
 Team - Unix\Password-Safe-DB\prod_unix.psafe3.plk


Problem is once the files are restored the files are all either 0 K or 1


KB


in size.  empty files

Restore complete with no error.
There are no errors in Act log for the backup run at these times.

Has anyone ever seen these behavior before???

Thanks everyone.

Craig






Re: Restore question TSM for mail Lotus Domino Window V5.4

2007-09-05 Thread Eduardo Esteban
The Domino server requests from the DP client the logs that it needs to
recover the database to the
specified point in time.  After each log is restored, the Domino server
applies the transactions to the
database. If you specify applylogs without a specific point in time, all
the archived logs starting from
the log that was active at the time of the backup should be restored, and
the Domino server should
recover the restored database to the current point in time.


ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 09/05/2007
05:43:30 AM:

 Here's a breakdown of the problem I'm seeing.

 Last week, 8/31, we generated enough data for 17 transaction log extent
 files and were able to successfully execute data restores against those
 files.

 Tuesday, 9/4, I generated data for extent files 18 thru 44 and archived
 those extent files, however, when I do a point in time restore against
that
 data, the Data Protection for Lotus Notes client only applies extent
files
 2 thru 17.

 If I do a restore and select 'Apply Logs' on the Activate tab, the
client
 appears to apply transaction logs 2 thru 44 (all of the log files),
 however, I still  am only observing data recovery from the 31st.  No
data
 from Tuesday appears to get restored during this operation.

 So - the question is, how can I get the data from Tuesday restored by
 applying transaction log extent files generated on that day?

 The information transmitted is intended only for the person or
 entity to which it is addressed and may contain CONFIDENTIAL
 material.  If you receive this material/information in error, please
 contact the sender and delete or destroy the material/information.


Re: Restore question

2005-10-31 Thread Stapleton, Mark
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Farren Minns
Is there a way to ascertain what tape volumes will be required for a
file/dir restore before actually running it?

This has been discussed many times; see the mailing list archives.

The short answer is no. The workaround is to make all primary pool tapes
unavailable and see which tape is called. The problem is that you only
find out the first tape needed.

--
Mark Stapleton ([EMAIL PROTECTED])
IBM Certified Advanced Deployment Professional
 Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Berbee Information Networks
Office 262.521.5627


Re: restore question

2003-08-24 Thread Andrew Raibeck
Correction/clarification:

 TSM mounts each needed tape once and only once

A colleague has pointed out that this is not always true. A tape may be
mounted more than once if it contains portions of a file where the
beginning of the file is on another tape. For example, lets say that we
have several files that span across more than one tape:

FILEA begins on TAPE01 and continues on TAPE20
FILEB begins on TAPE02 and continues on TAPE20
FILEC begins on TAPE03 and continues on TAPE20

If FILEA, FILEB, and FILEC are restored, then TAPE20 will be mounted 3
times, like this:

- Restore FILEA: mount TAPE01 then TAPE20
- Restore FILEB: mount TAPE02 then TAPE20
- Restore FILEC: mount TAPE03 then TAPE20

So while TSM does indeed work to minimize tape mounts, it is possible for
a tape to be mounted more than once.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

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




Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
08/20/2003 05:54
Please respond to ADSM: Dist Stor Manager

To: [EMAIL PROTECTED]
cc:
Subject:Re: restore question


No query restore has nothing to do with minimizing tape mounts for
restore. For a given restore, TSM mounts each needed tape once and only
once, and reads it from front to back.

The most visible benefit of no query restore is that data starts coming
back from the server sooner than it does with classic restore. With
classic restore, the client queries the server for all objects that match
the restore file specification. The server sends this information to the
client, then the client sorts it so that tape mounts will be optimized.
However, the time involved in getting the information from the server,
then sorting it (before any data is actually restored), can be quite
lengthy. No query restore lets the TSM server do the work: the client
sends the restore file specification to the server, the server figures out
the optimal tape mount order, and then starts sending the restored data to
the client. The server can do this faster, and thus the time it takes to
start actually restoring data is reduced.

In either case, for a given restore, TSM will restore the files and
directories in a manner that optimizes tape mounts. If it so happens that
a file is restored before it's parent directory is restored, then the
client will create the parent directory, restore the file, then restore
the parent directory when it encounters it in the restore sequence.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

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




Karel Bos [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
08/20/2003 00:02
Please respond to ADSM: Dist Stor Manager

To: [EMAIL PROTECTED]
cc:
Subject:Re: restore question


Hi,

Depends (love that statement) on the type of restore. If you have a
no-query
restore, the tsm server will restore the data in a as few mounts as
possible way, if you have a query restore the client will ask the tsm
server for a object (being file or directory), so the TSM server can not
do
its thing to minimize the number of tapemounts.

From the read.me:

No query restore
When you enter an unrestricted wildcard source file specification on the
restore command and do not specify any of the options: inactive, latest,
pick, fromdate, or todate, the client uses a different method for
retrieving
files and directories from the server. This method is called no query
restore because instead of querying the server for each object to be
restored, a single restore request is sent to the server. In this case,
the
server returns the files and directories to the client without further
action by the client. The client merely accepts the data coming from the
server and restores it to the destination named on the restore command

Regard,

Karel

 -Oorspronkelijk bericht-
 Van: i love tsm [mailto:[EMAIL PROTECTED]
 Verzonden: dinsdag 19 augustus 2003 21:02
 Aan: [EMAIL PROTECTED]
 Onderwerp: restore question


 Hi all

 A basic question...

 tapes are non collocated

 if you kick off a restore of multiple directories on a win2k
 client will TSM
 mount a tape and get all the data off that tape for the directories
 concerned then move on to the next volume, or does it restore
 sequentially
 one directory at a time, i.e it could mount the same tape
 numerous times as
 it goes through thr directories.

 Many Thanks

Re: restore question

2003-08-20 Thread Karel Bos
Hi,

Depends (love that statement) on the type of restore. If you have a no-query
restore, the tsm server will restore the data in a as few mounts as
possible way, if you have a query restore the client will ask the tsm
server for a object (being file or directory), so the TSM server can not do
its thing to minimize the number of tapemounts.

From the read.me:

No query restore
When you enter an unrestricted wildcard source file specification on the
restore command and do not specify any of the options: inactive, latest,
pick, fromdate, or todate, the client uses a different method for retrieving
files and directories from the server. This method is called no query
restore because instead of querying the server for each object to be
restored, a single restore request is sent to the server. In this case, the
server returns the files and directories to the client without further
action by the client. The client merely accepts the data coming from the
server and restores it to the destination named on the restore command

Regard,

Karel

 -Oorspronkelijk bericht-
 Van: i love tsm [mailto:[EMAIL PROTECTED]
 Verzonden: dinsdag 19 augustus 2003 21:02
 Aan: [EMAIL PROTECTED]
 Onderwerp: restore question


 Hi all

 A basic question...

 tapes are non collocated

 if you kick off a restore of multiple directories on a win2k
 client will TSM
 mount a tape and get all the data off that tape for the directories
 concerned then move on to the next volume, or does it restore
 sequentially
 one directory at a time, i.e it could mount the same tape
 numerous times as
 it goes through thr directories.

 Many Thanks

 _
 Sign-up for a FREE BT Broadband connection today!
 http://www.msn.co.uk/specials/btbroadband



Re: restore question

2003-08-20 Thread Andrew Raibeck
No query restore has nothing to do with minimizing tape mounts for
restore. For a given restore, TSM mounts each needed tape once and only
once, and reads it from front to back.

The most visible benefit of no query restore is that data starts coming
back from the server sooner than it does with classic restore. With
classic restore, the client queries the server for all objects that match
the restore file specification. The server sends this information to the
client, then the client sorts it so that tape mounts will be optimized.
However, the time involved in getting the information from the server,
then sorting it (before any data is actually restored), can be quite
lengthy. No query restore lets the TSM server do the work: the client
sends the restore file specification to the server, the server figures out
the optimal tape mount order, and then starts sending the restored data to
the client. The server can do this faster, and thus the time it takes to
start actually restoring data is reduced.

In either case, for a given restore, TSM will restore the files and
directories in a manner that optimizes tape mounts. If it so happens that
a file is restored before it's parent directory is restored, then the
client will create the parent directory, restore the file, then restore
the parent directory when it encounters it in the restore sequence.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

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




Karel Bos [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
08/20/2003 00:02
Please respond to ADSM: Dist Stor Manager

To: [EMAIL PROTECTED]
cc:
Subject:Re: restore question


Hi,

Depends (love that statement) on the type of restore. If you have a
no-query
restore, the tsm server will restore the data in a as few mounts as
possible way, if you have a query restore the client will ask the tsm
server for a object (being file or directory), so the TSM server can not
do
its thing to minimize the number of tapemounts.

From the read.me:

No query restore
When you enter an unrestricted wildcard source file specification on the
restore command and do not specify any of the options: inactive, latest,
pick, fromdate, or todate, the client uses a different method for
retrieving
files and directories from the server. This method is called no query
restore because instead of querying the server for each object to be
restored, a single restore request is sent to the server. In this case,
the
server returns the files and directories to the client without further
action by the client. The client merely accepts the data coming from the
server and restores it to the destination named on the restore command

Regard,

Karel

 -Oorspronkelijk bericht-
 Van: i love tsm [mailto:[EMAIL PROTECTED]
 Verzonden: dinsdag 19 augustus 2003 21:02
 Aan: [EMAIL PROTECTED]
 Onderwerp: restore question


 Hi all

 A basic question...

 tapes are non collocated

 if you kick off a restore of multiple directories on a win2k
 client will TSM
 mount a tape and get all the data off that tape for the directories
 concerned then move on to the next volume, or does it restore
 sequentially
 one directory at a time, i.e it could mount the same tape
 numerous times as
 it goes through thr directories.

 Many Thanks

 _
 Sign-up for a FREE BT Broadband connection today!
 http://www.msn.co.uk/specials/btbroadband


Re: restore question - NTFS time stamp?

2003-06-18 Thread Andrew Raibeck
There is nothing particularly tricky about it. During the backup, we save
the timestamp information. During the restore, we create the directory,
then put the timestamp information back using Windows API function
SetFileTime().

I use PKZIP 2.52 (command line) and the -times=all option will preserve
the timestamps, i.e.:

   pkzip25 -ext -dir -times=all myfile.zip

Check the help info for your zip utility to see if it has a similar
option.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

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




Alexander Lazarevich [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
06/18/2003 06:40
Please respond to ADSM: Dist Stor Manager


To: [EMAIL PROTECTED]
cc:
Subject:restore question - NTFS time stamp?



I've got a TSM related question, but the question is really about NTFS
time stamps (creation date) for folders. The reason I'm asking this
newsgroup is because the only product out there that has the capability
I'm looking for is TSM.

What I need to be able to do is move/copy files and folders in an NTFS
filesystem, and preserve the time stamp. I've tried many things: copy,
xcopy, cygwin, winzip, pkzip, they all suffer from the same problem,
namely, that FOLDERS that are copied/moved/unzipped with these tools do
NOT preserve the original time stamp. I've asked newsgroups and gotten no
answers. I've even tried contacting 3rd party software vendors to see if
their windows/unix tools can do it, but they all tell me that it CAN'T be
done.

But that is bull, because TSM does it!!! TSM will restore files and
folders, and all the time stamps (creation dates) on the folders and
files are the original ones.

How does TSM do that? Any ideas?

Thanks in advance,

Alex
---   ---
   Alex Lazarevich | Systems Administrator | Imaging Technology Group
Beckman Institute - University of Illinois
   [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu
---   ---


Re: Restore Question??

2001-03-26 Thread Prather, Wanda

You can get that result if you are not root.

I have also had similar problems if my AIX session was running low on
available colors - if you have Netscape open, try closing it to free more X
screen resources.


-Original Message-
From: Blaine Gilbreath [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 11:09 AM
To: [EMAIL PROTECTED]
Subject: Restore Question??


I am trying to do a restore on an AIX 4.3.3 server.  When I open a dsm
graphical session and try to view the files that are available for restore I
can only see the directory structure.

When I query my file space in ADSM I see that I have 275 GB worth of data on
the particular file space that I am looking at.  Am I just way off in left
field or am I going crazy.

Regards,
Blaine