ADSM-L

Re: [ADSM-L] File Device class question

2009-06-19 23:36:45
Subject: Re: [ADSM-L] File Device class question
From: Rodney Luk <rluk AT SAMHEALTH DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 19 Jun 2009 20:33:28 -0700
Steven,

The data will be at an ISCSI SAN. It is a Dell MD3000i.I have about 9TB in 4 
virtual disks at RAID5 set. I am planning to have another ISCSI SAN for 
replication to the DR site when we have the budget next year. We have about 1TB 
backup data each night. 600GB is the exchange and DB server backups.

Thanks
Rodney 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Steven Langdale
Sent: Friday, June 19, 2009 10:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] File Device class question

Rodney

This will be local disk will it?  As you are trying to mitigate against 
another SAN "meltdown" - What does that mean?

Thanks

Steven Langdale
Global Information Services
EAME SAN/Storage Planning and Implementation
( Phone : +44 (0)1733 584175
( Mob: +44 (0)7876 216782
ü Conference: +44 (0)208 609 7400 Code: 331817
+ Email: steven.langdale AT cat DOT com

 



Rodney Luk <rluk AT SAMHEALTH DOT ORG> 
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
18/06/2009 19:24
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] File Device class question




Caterpillar: Confidential Green Retain Until: 18/07/2009 



Thanks for the advice, but we would like to put the onsite backup on disk 
for fast restore purpose. We had a SAN melt down last year and it took 3 
days to restore 70 VM servers. So we would really like to put the backup 
on disk. In addition, how much GB you would recommend for a FILE volume? I 
read some forum, someone recommend 25GB and some recommend 50GB.

Thanks
Rodney

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Shawn Drew
Sent: Thursday, June 18, 2009 11:14 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] File Device class question

If it is only Exchange data that is kept forever, you should just put the
exchange data in its own pool and keep checking them out for onsite
storage.
Since they don't expire, you should have to worry about reclamation.
You can leave all the other stuff in the library and let it reclaim as
needed.


Regards,
Shawn
________________________________________________
Shawn Drew





Internet
rluk AT SAMHEALTH DOT ORG

Sent by: ADSM-L AT VM.MARIST DOT EDU
06/18/2009 01:50 PM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
[ADSM-L] File Device class question






Hi,

Our 3584 library, it holds 270 tapes, is full because we keep our exchange
backup forever. I had to checkout some tapes for onsite storage. However,
we come to the point that it makes reclamation very inefficiency since
tapes are not in the library. I am thinking to create a new Domain and
move some nodes to the new domain. Create a FILE class pool on disk for
onsite restore that associate with the new domain. For now on the current
domain, our primary pool is on tapes. A copy tape pool is send to offsite
for DR.
My question is should I use the current copy tape pool or create a new
copy tape pool bind to the new domain. In addition, any suggest solution
for a situation that I have now? I am sorry I am new to TSM, I hope I
explain well the situation we have now.

Thanks
Rodney



  ________________________________
Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.



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.