ADSM-L

Re: Starting a Copy Storage Pool for DR

1999-05-04 15:30:40
Subject: Re: Starting a Copy Storage Pool for DR
From: "Patel, Nilesh (YR2K)" <NJPatel AT EXCHANGE.ML DOT COM>
Date: Tue, 4 May 1999 15:30:40 -0400
Hi,
Laura,
Creating separate Dev Class for Copy Storage pool will be the best solution
so you can have dedicated drives availabel for copy storage pool.

Thanks,

Nilesh Patel.
Merrill Lynch
212-647-3478

> -----Original Message-----
> From: Galvin, Laura L. [SMTP:LLGalvin AT LEGGMASON DOT COM]
> Sent: Tuesday, May 04, 1999 2:50 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Starting a  Copy Storage Pool for DR
>
> I am starting an Offsite Copy Storage Pool for disaster recovery,  should
> I
> create a separate dev class for the ease of management and also so the
> primary stgpool and the offsite stgpool will not compete for scratch
> tapes?
> This way I could dedicating 2 drives to the copy stgpool, which I believe
> I
> can afford to do.  What do you think?
>
> Site information:
> ADSM server v3.1.2.13
> 28 clients
> Total physical stored in primary stgpool - 2,578,512MB
> STK 9714 - 100 Slots DLT7 tapes
>     6 - DLT7000 tape drives
>
>
> Laura Galvin
> llgalvin AT leggmason DOT com
> 410 454 3608
>
>
>
> ___________________________________________
> IMPORTANT:  The security of electronic mail  sent through the Internet is
> not guaranteed.  Legg Mason therefore recommends that you do not send
> confidential information to us via electronic mail, including social
> security numbers, account numbers, and personal identification numbers.
>
> Delivery, and timely delivery, of electronic mail is also not guaranteed.
> Legg Mason therefore recommends that you do not send time-sensitive or
> action-oriented messages to us via electronic mail, including
> authorization to  "buy" or "sell" a security or instructions to conduct
> any other financial transaction.  Such requests, orders or instructions
> will not be processed until Legg Mason can confirm your instructions or
> obtain appropriate written documentation where necessary.
<Prev in Thread] Current Thread [Next in Thread>