Scott,
The /usr/openv/kms (Unix based systems) directory needs
to be on the master server only (nbkms daemon will start on the
master), but it could be activated from any media server. The master
server should be the controlling host. All other media servers will
point to the same Robot.
where i have to check this on my master or media.
Robot is configured on master and tape drives on media.
+--
|This was sent by qureshiu...@rediffmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
Hi Forum,
My env. has 1 Master on Sol 10 with 6.5.5 and 4 media server with 24 drives. I
am adding 2 more to one of my media server. I am getting the following output
from tpconfig.
r...@p100xmed04 # /opt/openv/volmgr/bin/tpconfig -l
Device Robot Drive Robot Drive Device Second
Type Num Index
These number aren't that hot compared to DataDomain from my use of it.
We are seeing 86TB of backup images occupying 4.4TB of phys disk.
On 4/1/2010 12:07 PM, Jon Bousselot wrote:
> I set it up in a small test environment, and started backing up three
> clients into a deduplication pool exclusiv
On Fri, Apr 2, 2010 at 8:29 AM, David Stanaway wrote:
>
> These number aren't that hot compared to DataDomain from my use of it.
>
> We are seeing 86TB of backup images occupying 4.4TB of phys disk.
>
It all depends on the data streams and how many generations you keep. If
you keep a year's wor
Another thing to note as with many of these types of devices (VTL's,
intelligent disk, dedup applications, etc.) using OS specific tools such
as df to determine used space will not give accurate numbers. You'll
want to measure used space from the tools provided in the application or
device. There
Nice thing about DDs are they can give you a daily email with that kind
of detail.
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mike
Andres
Sent: Friday, April 02, 2010 10:49 AM
To: Ed Wilts; Da
Update:
I have talked to both Symantec and Dell. Still trying to figure it
out... Check out the difference in the information returned from manage
drive attributes Not sure why yet It may be that the output is
different because fl1 suggests a LTO3 tape that does not support
encryptio
Dwayne,
It does not matter if software configures as LTO3 or even LTO2.
As long as you have LTO4 Tape drives and you are using LTO4 Tapes. One
more thing, you may already know it? The Volume Pool's name has to
start with ENCR_what_ever_you_like.
thx
ss
Adams, Dwayne wrote:
