Wanda,
Thanks for your cogent analysis. Always appreciated.
We're trying to decide if we need to offer a Data Domain sort of thing
to our customers. In the very specific case you describe, perhaps.
I am 100% with you on the "why replicate backup" when you can more
easily replicate data?! We
Good afternoon.
Somebody can help me?
Gracias
RMAN> run {
2> allocate channel oem_sbt_backup1 type 'SBT_TAPE' format '%U' parms
'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
backup incremental level 1 cumulative database;
3> 4> backup archivelog all not backed up;
5>
Kelly,
I have more than 1 customer considering a de-dup VTL product.
It's true that for regular file systems, TSM doesn't redump unchanged
files, so people aren't getting AS LARGE a reduction in data stored (of
that type) as would a user of an old style full dump- incremental -
incremental - full
At 03:40 PM 8/29/2007, Kelly Lipp wrote:
Help me get it because aside from the typical "I gotta have it
because the trade rags tell me I gotta have it", I don't get it!
Kelly,
I think you are correct in that TSM already gives you some of the
benefits that a more traditional backup product woul
You're correct, in that there are products that can provide a more global
repository. We used the Dilligent VTFOpen in a 2node cluster and achieved
a 1200MBS write speed! Impressive, so if you don't need the de-dup the
VtfOpen product really screams.
In one of a few large Data Centers we see 25TB
I'd like to steer this around a bit. Our sales folks are saying they
are losing TSM opportunities to de-dup vendors. What specific business
problem are customers trying to solve with de-dup?
I'm thinking the following:
1. Reduce the amount of disk/tape required to storage backups.
Especially im
It seems to be connected with a larger SAN issue. It looks like the SAN
momentarily disconnects, the original backup session quits, and the
control session doesn't know about the reconnected backup session. So I
remain on the sidelines until the larger SAN issue is resolved.
Fred Johanson
TSM
>As de-dup, from what I have read, compares across all files
>on a "system" (server, disk storage or whatever), it seems
>to me that this will be an enormous resource hog
Exactly. To make sure everyone understands, the "system," is the
intelligent disk target, not a host you're backing up. A de-
De-dupe comes in two flavors:
1. Target de-dupe
2. Source de-dupe
Target de-dupe is de-dupe inside a VTL/IDT (intelligent disk target).
You send it regular TSM backups and it finds the duplicate data within
it. A good vendor of this type should give you all the benefits of
de-dupe without any per
Whenever I've installed a STORServer at a customer site I've advocated
the following:
The next time a new piece of server hardware shows up in your site,
steal it for a couple of weeks. Use it as a test bed. Try some
restores, try some backups, get to know your environment.
Customers always wan
First, I would say the only thing that this post says is the Diligent
had a better de-dupe ratio with this customer's data -- not that
Diligent's de-dupe is better overall. The different vendors use VERY
DIFFERENT ways to scan the incoming data and identify redundant pieces
of data. Those differ
The compression challenge is more related to creating unique backup
objects that can not be de-duped. Compression does cause a CPU
performance hit on the client. Performace related experience with
Dilkligent Protectier running on a Sunv40 with 4xDaul Core Procs and 32GB
memory we see a max of 250
I have been hearing bits and pieces about this de-dup thing.
Several things have me wondering , as folks on this list also
testify.
One thing I haven't heard about is performance. Even with TSM
clients,there is the thing not do "compression" on the client
due to performance issues. That is just
Any idea why Diligent's dedup ratio is better? What's different
about the dedup algorithm that makes it work better?
At 06:29 PM 8/28/2007, Curtis Preston wrote:
That sounds about right. Data Domain's a good product with a lot of
happy customers, but TSM customers who are only backing up file
I'm just looking at the image backup now. This may well be the way to
go.
Would you believe -- we are JUST getting a Windows test environment set
up here. We've had several rounds of admins who couldn't see the value
and weren't interested in doing the work, just to have a test-bed.
Current staff
Always test first, but:
1) Since the 5.3 (or maybe it was 5.2, don't remember) Windows client, you
can do online image backups. The MS VSS facility (if it's having a good
day) is used to snapshot the volume.
2) I don't think there is a problem with restoring an image to a different
host, if you
Thanks everybody for your advices !
The purpose is to backup virtual machine with large disk space and databases.
The backup window is very short (when there is backup window) ; some virtual
machine will be running on 24/7 basis.
First I thought, classicly, to install nodes, tdp and so on virtua
Hello,
I would suggest you review an excellent Tivoli Field Guide titled
"Using IBM Tivoli Storage Manager for Backup and Restore on the VMware
Service Console"
which is available on our support pages at below url :
http://www-1.ibm.com/support/docview.wss?uid=swg27009931
It discusses such backup
On Wednesday 29 August 2007, Wojtek Pięcek wrote:
> > For backup of the vmdk files, I adapted my custom script for ESC 2.x to
> > 3.x (in stead of redo logs you have to snapshot) so I can online backup
> > the vmdk files. Works flawless.
> > For a all-in-one backup script, google for vmbk.
>
> Why
On 8/29/07, Stef Coene <[EMAIL PROTECTED]> wrote:
> On Wednesday 29 August 2007, Richard van Denzel wrote:
> > Hello Pierre,
> >
> > It depends on wether your ESX Server will be 2.x or 3.x.
> > The consolidated backup is for 2.x only. On ESX 3.x servers the way VM's
> > are deployed is completely c
On Wednesday 29 August 2007, Richard van Denzel wrote:
> Hello Pierre,
>
> It depends on wether your ESX Server will be 2.x or 3.x.
> The consolidated backup is for 2.x only. On ESX 3.x servers the way VM's
> are deployed is completely changed and there is AFAIK no way to backup
> the VMDK files.
I
Hello Pierre,
It depends on wether your ESX Server will be 2.x or 3.x.
The consolidated backup is for 2.x only. On ESX 3.x servers the way VM's
are deployed is completely changed and there is AFAIK no way to backup
the VMDK files.
Met vriendelijke groet, with kind regards,
Richard van Denzel.
-
Hello,
I am studying solutions for backup of a future installation of windows
guest on VMWARE ESX.
What are the best practices ?
Context :
1 VMWARE ESX Host
Up to 6 windows 2003 with up to 6 To
GigaEthernet
Some of the guests will manage large databases.
I saw that VMWARE consolidated backup ca
What is the output of command q volh t=dbb please ?
> -Message d'origine-
> De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De
> la part de Gill, Geoffrey L.
> Envoyé : mardi 28 août 2007 17:34
> À : ADSM-L@VM.MARIST.EDU
> Objet : Re: [ADSM-L] delete volhist dbb
>
> > The switch
24 matches
Mail list logo
