I also wanted to add that pretty soon you will be able to do synthetic backups
at your DR site which is a huge bonus.. You can now assemble full backups from
data that already exists on the replicated target.
+--
|This was sent
You want to use OST without a doubt.. With optimized deduped replication you
end up pushing almost nothing across the wire.. With VTL its a full rehydration
on the source end before it gets replicated. I just spent several months
testing this on Data Domain and Quantum DXi. The only caveat is Da
I'm fairly certain that there are no real problems about having multiple LSUs,
certainly as far as dedupe goes - I am quite sure that dedupe is global to all
the LSUs.
The 'some advanced NetBackup features' is really saying that due to the
limitations of the current OST specification, each LSU
According to the OST / Boost admin guide
(http://www.emc.com/collateral/software/white-papers/h7296-data-domain-boost-openstorage-wp.pdf)
having multiple LSU's may impact some advanced Netbackup features like media
server load balancing and capacity reporting. We are seeing equally impressive
thanks, we created multiple lsu's for the same exact reason to keep an eye on
ratios of different os's and db's thinking that dedupe and compression would be
done across all the data ingested so the existence of multiple lsu's wouldn't
matter. i'm hoping this is the case
+
We misread the guides when setting up our new dd670's about 6 months ago and
currently have 9 active LSU's. Prior to using OST on our old DD's we had
multiple directories under /backup so we could easily keep tabs on the
compression and replication performance of the different apps or systems w
Can someone tell me if the number of LSUs configured on a system effects dedupe
ratio and overall performance of the DD box? i see that in best practices it
is recommended that one LSU is created per Netbackup environment. i do have
more than LSU configured in one NB environment but i wonder i
