Migrate by date?

[Christian Svensson]

Hi everyone,

Has anyone implementing IBM CommonStore for Mail before and let the CommonStore 
save the data striate in to TSM Disk Storage Pool?

And then somehow start a migration that is migrating from Disk to Tape and only 
migrating data that is older than number of days/months or years?

 

I never heard that you can migrate data by date from one storage pool to 
another storage pool, but the IBM Consulting person that is setting up the 
CommonStore solution told me that other TSM Admin has done this before.

 

We are using TSM Server 5.4.0.3 on a Windows Server 2003 x86.

Client version I have no idea. But the version of client is the version that 
comes with the latest version of CommonStore.

 

Thanks for your help.

 

Many thanks

Christian

 

 

Best Regards / Med Vänlig Hälsning

Christian Svensson

Products Specialist 

Cristie Nordic AB
Gamla Värmdövägen 4, SE-13137, Nacka, Sweden
( Office: +46 8 718 4330
6 Support: +1-866-832-2267
) Cell: +46 70 325 1577
8 [EMAIL PROTECTED]  
F Visit Us@ http://www.cristie.com

 

Re: Migrate by date?

[Remco Post]

Christian Svensson wrote:
> Hi everyone,
> 
> Has anyone implementing IBM CommonStore for Mail before and let the
> CommonStore save the data striate in to TSM Disk Storage Pool?
> 
> And then somehow start a migration that is migrating from Disk to
> Tape and only migrating data that is older than number of days/months
> or years?
> 

look into tht migdelay and migcontinue attributes for a stgpool.

> 
> 
> I never heard that you can migrate data by date from one storage pool
> to another storage pool, but the IBM Consulting person that is
> setting up the CommonStore solution told me that other TSM Admin has
> done this before.
> 
> 
> 
> We are using TSM Server 5.4.0.3 on a Windows Server 2003 x86.
> 
> Client version I have no idea. But the version of client is the
> version that comes with the latest version of CommonStore.
> 
> 
> 
> Thanks for your help.
> 
> 
> 
> Many thanks
> 
> Christian
> 
> 
> 
> 
> 
> Best Regards / Med Vänlig Hälsning
> 
> Christian Svensson
> 
> Products Specialist
> 
> Cristie Nordic AB Gamla Värmdövägen 4, SE-13137, Nacka, Sweden (
> Office: +46 8 718 4330 6 Support: +1-866-832-2267 ) Cell: +46 70 325
> 1577 8 [EMAIL PROTECTED]
>  F Visit Us@
> http://www.cristie.com
> 
> 


-- 
Met vriendelijke groeten,

Remco Post

SARA - Reken- en Netwerkdiensten  http://www.sara.nl
High Performance Computing  Tel. +31 20 592 3000Fax. +31 20 668 3167
PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16  B3F6 048A 02BF DC93 94EC

"I really didn't foresee the Internet. But then, neither did the
computer industry. Not that that tells us very much of course - the
computer industry didn't even foresee that the century was going to
end." -- Douglas Adams

NetApp CIFS Restore causes crashdumps

[Herrmann, Boris]

Hi All,
 
almost every time, when we restore files from our NetApp System via CIFS
we get a crashdump. 
We've opened an IBM PMR Case. IBM told us to install the newest patch
level 5.4.1.2 for this Windows Client (WIN 2003). Unfortunately the
error happend again and again (see dsmcrash.log). Our Windows Admins are
driving crazy. Until today IBM has no solution for our problem.
Have anyone else a similiar problems?
 
DSMCRASH.LOG shows:
 


2007/10/24 15:42:15
IBM Tivoli Storage Manager
Version: 5.4.1.02  
Build date:  Tue Jul 10 15:35:02 2007
 
dsm.exe caused exception C005 (EXCEPTION_ACCESS_VIOLATION) at
001B:7C350428
 
Register dump:
EAX=  EBX=0013EBCC  ECX=0013DF6C  EDX=  ESI=0139FB7C
EDI=00036A70  EBP=00037D30  ESP=0013DD40  EIP=7C350428  FLG=00010202
CS=001B   DS=0023  SS=0023  ES=0023   FS=003B  GS=
 
Crash dump successfully written to file
'C:\Tivoli\TSM\baclient\dsmcrash.dmp'
 
Stack Trace:
001B:7C350428 (0x 0x 0x 0x0001) MSVCR71.dll,
wcscpy()+8 bytes
 
 
 


2007/10/24 15:44:46
IBM Tivoli Storage Manager
Version: 5.4.1.02  
Build date:  Tue Jul 10 15:35:02 2007
 
dsm.exe caused exception C005 (EXCEPTION_ACCESS_VIOLATION) at
001B:7C350428
 
Register dump:
EAX=  EBX=0013E2A4  ECX=0013D644  EDX=  ESI=0139A604
EDI=013B38A0  EBP=00037D30  ESP=0013D418  EIP=7C350428  FLG=00010202
CS=001B   DS=0023  SS=0023  ES=0023   FS=003B  GS=
 
Crash dump successfully written to file
'C:\Tivoli\TSM\baclient\dsmcrash.dmp'
 
Stack Trace:
001B:7C350428 (0x 0x 0x 0x0001) MSVCR71.dll,
wcscpy()+8 bytes
 
With kind regards,
Boris Herrmann

Wrong devc in q pro output

[David E Ehresman]

TSM 4.3.4.0 running on AIX 5.3.06.03

I have five devclasses pointing to five difference tape libraries.  When I am 
doing backup storagepool and have more processes running than I have mount 
points and I do a Query Process, one or more of the processes say they are 
waiting on mount points.  There are mount points available in the devclass for 
the primary storage pool but not in the devclass for the copy pool.  But the 
output of the  Q PRO says it is waiting on mount points in the primary devc, 
not the copy devc leading to some confusion until I figured out what was going 
on.  Has anyone else seen this?  Is there a fix?

David Ehresman

Re: NetApp CIFS Restore causes crashdumps

[Andrew Raibeck]

The problem has been reproduced in the lab, so we have a better
understanding of the problem. An APAR will be taken. I do not know when a
fix will be made available. Once the APAR is opened, you can track it
through your PMR if you wish.

Use the command line client as a workaround, as it is my understanding the
crash does not occur there.

Regards,

Andy

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

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 10/25/2007
02:31:05 AM:

> Hi All,
>
> almost every time, when we restore files from our NetApp System via CIFS
> we get a crashdump.
> We've opened an IBM PMR Case. IBM told us to install the newest patch
> level 5.4.1.2 for this Windows Client (WIN 2003). Unfortunately the
> error happend again and again (see dsmcrash.log). Our Windows Admins are
> driving crazy. Until today IBM has no solution for our problem.
> Have anyone else a similiar problems?
>
> DSMCRASH.LOG shows:
>
> 
> 
> 2007/10/24 15:42:15
> IBM Tivoli Storage Manager
> Version: 5.4.1.02
> Build date:  Tue Jul 10 15:35:02 2007
>
> dsm.exe caused exception C005 (EXCEPTION_ACCESS_VIOLATION) at
> 001B:7C350428
>
> Register dump:
> EAX=  EBX=0013EBCC  ECX=0013DF6C  EDX=  ESI=0139FB7C
> EDI=00036A70  EBP=00037D30  ESP=0013DD40  EIP=7C350428  FLG=00010202
> CS=001B   DS=0023  SS=0023  ES=0023   FS=003B  GS=
>
> Crash dump successfully written to file
> 'C:\Tivoli\TSM\baclient\dsmcrash.dmp'
>
> Stack Trace:
> 001B:7C350428 (0x 0x 0x 0x0001) MSVCR71.dll,
> wcscpy()+8 bytes
>
>
>
> 
> 
> 2007/10/24 15:44:46
> IBM Tivoli Storage Manager
> Version: 5.4.1.02
> Build date:  Tue Jul 10 15:35:02 2007
>
> dsm.exe caused exception C005 (EXCEPTION_ACCESS_VIOLATION) at
> 001B:7C350428
>
> Register dump:
> EAX=  EBX=0013E2A4  ECX=0013D644  EDX=  ESI=0139A604
> EDI=013B38A0  EBP=00037D30  ESP=0013D418  EIP=7C350428  FLG=00010202
> CS=001B   DS=0023  SS=0023  ES=0023   FS=003B  GS=
>
> Crash dump successfully written to file
> 'C:\Tivoli\TSM\baclient\dsmcrash.dmp'
>
> Stack Trace:
> 001B:7C350428 (0x 0x 0x 0x0001) MSVCR71.dll,
> wcscpy()+8 bytes
>
> With kind regards,
> Boris Herrmann

Re: Wrong devc in q pro output

[Richard Sims]

On Oct 25, 2007, at 10:00 AM, David E Ehresman wrote:


TSM 4.3.4.0 running on AIX 5.3.06.03

I have five devclasses pointing to five difference tape libraries.
When I am doing backup storagepool and have more processes running
than I have mount points and I do a Query Process, one or more of
the processes say they are waiting on mount points.  There are
mount points available in the devclass for the primary storage pool
but not in the devclass for the copy pool.  But the output of the
Q PRO says it is waiting on mount points in the primary devc, not
the copy devc leading to some confusion until I figured out what
was going on.  Has anyone else seen this?  Is there a fix?


David -

Misidentification of the shortfall device class in the "Waiting for
mount point" line of Query PRocess output is a defect which persists
into at least TSM 5.2, from my experience.

   Richard Sims

TSM API error

[Avy Wong]

Hello,

I encounter error, " Error: 9 establishing TSM API session .
Unknown TSM API error. " when I update/reinstall TSM scheduler. The
services kicks off on the client side no problem, but  when I kick off a
session from the TSM server to NodeXXX, there is no response. I see
"new_ImageObject plugin could not be initialized rc 106," error in the
dsmerror.log. Before I go and do a reboot, I thought I'll ask around to see
if anyone has the same problem before and if there is a fix for that. Many
thanks.

dsmerror.log:
10/25/2007 14:26:33 ANS1814E Unable to start the scheduled event
'0200_SQL_AMBK'
10/25/2007 14:26:33 ANS1815E Either the window has elapsed or the schedule
has been deleted
10/25/2007 14:28:33 ANS1909E The scheduled command failed.
10/25/2007 14:28:33 ANS1512E Scheduled event '0200_SQL_AMBK' failed.
Return code = 1.
10/25/2007 14:32:36 new_ImageObject: plugin could not be initialized rc 106


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

Re: Scheduling a full archive of data once/month

[Dave Mussulman]

On Mon, Oct 22, 2007 at 09:49:00AM -0500, Joni Moyer wrote:
> I have just received the task of scheduling an archive of all data from
> several windows servers the first Saturday of every month for 7 years.
> What is the best method of accomplishing this?  I would like to do this
> from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server.  Any
> suggestions are greatly appreciated!

I'd probably do this as backupsets in 5.4.  They're easy to generate
from the server, work from data already on the server, have their own
retention times different from the incremental values, are file-level
browsable in a ToC that lives in file space (not TSM DB-space) -- which
means you could offload them to tape, or leave the ToC on a disk/file
stgpool for quick access.  Backupsets have worked well as a point in
time archive on a few nodes of mine.

Dave

ESL-712

[Kevin Boatright]

I have a IBM p570 running AIX 5.3.04.  Is there any issues attaching a HP 
ESL-712 for TSM?  If not, is there any particular driver required?  Steps to 
accomplish this?
 
Thanks
Kevin

Need advice on a long term TSM storage solution

[Nicholas Rodolfich]

Hello All,

Thanks for your help!!

Our TSM server resides on an LPAR with 2 processing units and 12Gb of
RAM. We use an IBM 3584 library with an expansion cabinet and 16 drives
(8-LTO1 and 8-LTO2) We have 16 LTO3 drive on order to upgrade our
drives. Our database is at 80Gb so I think I am ready for a new
instance.

We have a HIPAA requirement to keep certain data for 3 years and other
data for 7 years.

What is the best storage solution for this type of requirement?

 I plan to manage the HIPAA data with multiple domains, management
classes, etc but I am not sure what storage medium to use. It seem no
matter which cartridge technology we use that it will end up being a
bunch of work over the years following the tape technology curve. Should
I be looking at something optical or electronic?

Additionally, does it make sense to incarnate another TSM instance?

Thanks for your patience and help!!

Nicholas



IMPORTANT NOTICE:  This message and any included attachments are from East 
Jefferson General Hospital, and is intended only for the addressee(s), and may 
include Protected Health (PHI) or other confidential information.  If you are 
the intended recipient, you are obligated to maintain it in a secure and 
confidential manner and re-disclosure without additional consent or as 
permitted by law is prohibited.   If you are not the intended recipient, use of 
this information is strictly prohibited and may be unlawful.  Please promptly 
reply to the sender by email and delete this message from your computer. East 
Jefferson General Hospital greatly appreciates your cooperation.

FW: [ADSM-L] Wladimir Benavides Unsuscribe

[Wladimir Benavides]

Wladimir Benavides.
Especialista Software IBM
mailto: [EMAIL PROTECTED]
Tels: (593) 02 2550535 Ext 110
Fax: 02 2908203
Celular: 098325596
Dirección: Av. 12 de Octubre 1753 y Cordero
www.binaria.com.ec


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas 
Rodolfich
Sent: Thursday, October 25, 2007 5:08 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Need advice on a long term TSM storage solution

Hello All,

Thanks for your help!!

Our TSM server resides on an LPAR with 2 processing units and 12Gb of
RAM. We use an IBM 3584 library with an expansion cabinet and 16 drives
(8-LTO1 and 8-LTO2) We have 16 LTO3 drive on order to upgrade our
drives. Our database is at 80Gb so I think I am ready for a new
instance.

We have a HIPAA requirement to keep certain data for 3 years and other
data for 7 years.

What is the best storage solution for this type of requirement?

 I plan to manage the HIPAA data with multiple domains, management
classes, etc but I am not sure what storage medium to use. It seem no
matter which cartridge technology we use that it will end up being a
bunch of work over the years following the tape technology curve. Should
I be looking at something optical or electronic?

Additionally, does it make sense to incarnate another TSM instance?

Thanks for your patience and help!!

Nicholas



IMPORTANT NOTICE:  This message and any included attachments are from East Jeffe
rson General Hospital, and is intended only for the addressee(s), and may includ
e Protected Health (PHI) or other confidential information.  If you are the inte
nded recipient, you are obligated to maintain it in a secure and confidential ma
nner and re-disclosure without additional consent or as permitted by law is proh
ibited.   If you are not the intended recipient, use of this information is stri
ctly prohibited and may be unlawful.  Please promptly reply to the sender by ema
il and delete this message from your computer. East Jefferson General Hospital g
reatly appreciates your cooperation.



El servicio de Symantec Hosted Mail Security ha verificado que el mensaje se  
encuentra libre de Virus.

Re: Need advice on a long term TSM storage solution

[Tammy Schellenberg]

We have just recently implemented a data domain and so far we love it.
The majority of the issues we had were related to tape.  Right now we
are in the process of moving our data from tape to the DDR, once this is
complete we will be implementing the backup at our offsite disaster
recovery system.  The compression is great, operations tasks are
decreased already.  I would recommend this solution.  Tapes are very
finicky and confining.  

Tammy Schellenberg, DCIS, MCP
Systems Administrator, Information Technology

direct: 604 864 6578
email: [EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nicholas Rodolfich
Sent: Thursday, October 25, 2007 3:08 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Need advice on a long term TSM storage solution

Hello All,

Thanks for your help!!

Our TSM server resides on an LPAR with 2 processing units and 12Gb of
RAM. We use an IBM 3584 library with an expansion cabinet and 16 drives
(8-LTO1 and 8-LTO2) We have 16 LTO3 drive on order to upgrade our
drives. Our database is at 80Gb so I think I am ready for a new
instance.

We have a HIPAA requirement to keep certain data for 3 years and other
data for 7 years.

What is the best storage solution for this type of requirement?

 I plan to manage the HIPAA data with multiple domains, management
classes, etc but I am not sure what storage medium to use. It seem no
matter which cartridge technology we use that it will end up being a
bunch of work over the years following the tape technology curve. Should
I be looking at something optical or electronic?

Additionally, does it make sense to incarnate another TSM instance?

Thanks for your patience and help!!

Nicholas



IMPORTANT NOTICE:  This message and any included attachments are from
East Jefferson General Hospital, and is intended only for the
addressee(s), and may include Protected Health (PHI) or other
confidential information.  If you are the intended recipient, you are
obligated to maintain it in a secure and confidential manner and
re-disclosure without additional consent or as permitted by law is
prohibited.   If you are not the intended recipient, use of this
information is strictly prohibited and may be unlawful.  Please promptly
reply to the sender by email and delete this message from your computer.
East Jefferson General Hospital greatly appreciates your cooperation.

This email and any files transmitted with it are confidential and are intended 
solely for the use of the individual or entity to whom they are addressed.

If you are not the original recipient or the person responsible for delivering 
the email to the intended recipient, be advised that you have received this 
email in error, and that any use, dissemination, forwarding, printing, or 
copying of this email is strictly prohibited. If you receive this email in 
error, please immediately notify the sender.

Please note that this financial institution neither accepts nor discloses 
confidential member account information via email. This includes password 
related inquiries, financial transaction instructions and address changes.

Re: TSM API error

[Richard Sims]

When posting, please include your TSM level.
This may be a manifestation of APAR IC53393 (q.v.).  Best to contact
TSM Support to determine.

   Richard Sims

On Oct 25, 2007, at 3:45 PM, Avy Wong wrote:


Hello,

I encounter error, " Error: 9 establishing TSM API session .
Unknown TSM API error. " when I update/reinstall TSM scheduler. The
services kicks off on the client side no problem, but  when I kick
off a
session from the TSM server to NodeXXX, there is no response. I see
"new_ImageObject plugin could not be initialized rc 106," error in the
dsmerror.log. ...