This is a multi-part message in MIME format.
--------------000106060605060908000304
Content-Type: multipart/alternative;
boundary="------------050309010502030400060903"
--------------050309010502030400060903
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Ed is correct.
Multiple Policies can be written to the same DSSU, however, the contents
of a DSSU can only be copied to a single "Volume Pool". So you going to
need at least a unique DSSU for each Volume Pool you want staged.
In my environment, I have 5 Volume Pools.
The first is a NAS, and can feed the LTO3 drives a full speed. (So it
didn't make sense to stage them)
The 2nd, 3rd, and 4th, are databases held on three different servers,
and are backed up across a gigabit backbone. Each of these have their
own DSSU on the media server. Which is then copied it's own Volume Pool
in the PTL.
The 5th covers everything else. Nearly a dozen policies that backed up
to two DSSU's, which feed a single Volume Pool.
Ed Wilts wrote:
> On Thu, Apr 27, 2006 at 05:17:41PM -0400, Matthew Stier wrote:
>
>> DSSU's do have their weaknesses. You are typically stuck with one-to-one
>> ration between DSSU's and policies. This fit my needs, but for those
>> with a multitude of policies to manage, I can see them having problems.
>>
>
> We have a lot of policies using the same DSSUs and have not run into any
> issues with doing this. The only time we have dedicated DSSUs is for
> databases and that's to guarantee that their last backup is on DSSU for
> a restore.
>
> .../Ed
>
>
--------------050309010502030400060903
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ed is correct. <br>
<br>
Multiple Policies can be written to the same DSSU, however, the
contents of a DSSU can only be copied to a single "Volume Pool". So
you going to need at least a unique DSSU for each Volume Pool you want
staged.<br>
<br>
In my environment, I have 5 Volume Pools. <br>
<br>
The first is a NAS, and can feed the LTO3 drives a full speed. (So it
didn't make sense to stage them)<br>
<br>
The 2nd, 3rd, and 4th, are databases held on three different servers,
and are backed up across a gigabit backbone. Each of these have their
own DSSU on the media server. Which is then copied it's own Volume Pool
in the PTL.<br>
<br>
The 5th covers everything else. Nearly a dozen policies that backed up
to two DSSU's, which feed a single Volume Pool.<br>
<br>
<br>
<br>
Ed Wilts wrote:
<blockquote cite="mid20060428153312.GA19450 AT www.ewilts DOT org" type="cite">
<pre wrap="">On Thu, Apr 27, 2006 at 05:17:41PM -0400, Matthew Stier wrote:
</pre>
<blockquote type="cite">
<pre wrap="">DSSU's do have their weaknesses. You are typically stuck with
one-to-one
ration between DSSU's and policies. This fit my needs, but for those
with a multitude of policies to manage, I can see them having problems.
</pre>
</blockquote>
<pre wrap=""><!---->
We have a lot of policies using the same DSSUs and have not run into any
issues with doing this. The only time we have dedicated DSSUs is for
databases and that's to guarantee that their last backup is on DSSU for
a restore.
.../Ed
</pre>
</blockquote>
</body>
</html>
--------------050309010502030400060903--
--------------000106060605060908000304
Content-Type: text/x-vcard; charset=utf-8;
name="Matthew.Stier.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="Matthew.Stier.vcf"
begin:vcard
fn:Matthew Stier
n:Stier;Matthew
org:Fujitsu Network Communications;CAE
adr:Sixth Floor;;Two Blue Hill Plaza;Pearl River;NY;10965;USA
email;internet:Matthew.Stier AT us.fujitsu DOT com
title:Principal Engineer
tel;work:845-731-2097
tel;fax:845-731-2011
tel;cell:845-893-0575
x-mozilla-html:TRUE
version:2.1
end:vcard
--------------000106060605060908000304--
|
