ADSM-L

Re: Advantages of having backup by versioning...

2006-07-17 05:49:02
Subject: Re: Advantages of having backup by versioning...
From: "Bernaldo de Quiros, Iban 1" <iban.bernaldodequiros AT SUN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 17 Jul 2006 10:47:16 +0100
Thanks !!

If I have well understood...

the principal advantages are:

1- To do the same job, the number of drives to use, is less than doing a 
traditional backup method.

2- quickly restore

3- saving in media  

But do we have a best practices document that explain these three factors ¿?

thank you for your help !!

Regards,

Ibán Bernaldo de Quirós Márquez 
Technical Specialist 
cell: + 34 659 01 91 12 
Sun Microsystems Iberia



-----Original Message-----
From: ADSM: Dist Stor Manager on behalf of Andy Huebner
Sent: Fri 14/07/2006 16:10
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Advantages of having backup by versioning...
 
My 2 cents worth. (Actual exchange rate will vary)

Using TSM's method of data storage we have about 3 bytes of data on tape for 
every byte on a server.  When we used a traditional backup method, we had 
almost 9 bytes of data on tape for every byte on a server.  The available dates 
to recover to are about the same.  We realized a real savings in media.

Moving from a weekly full to the always incremental allowed us to have fewer 
tape drives to complete the same work.  Our full backups required nearly 24 
hours to complete, we no longer have to plan for a large weekend run.

Doing a restore with a traditional backup method means you restore a full 
backup then up to 6 incremental backups, this can result in the same file being 
written 7 times.  TSM will restore each object only once.  If TSM is properly 
used this can save a great deal of time during the restore, if it is not 
properly setup it can cost a great deal of time due to tape mount waits.

The downside is we no longer have 9 copies of an object on tape, we only have 
two, so in theory the odds of losing an object due to bad tapes is larger, but 
it is still a number starting with a dot and some zeros.

Andy Huebner

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Bernaldo de Quiros, Iban 1
Sent: Friday, July 14, 2006 5:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Advantages of having backup by versioning...

Hi everyone there !!

Could someone explain me the principal advantages of having the backup 
organised by versions...¿?

Is it really an advantage to others backup softwares such as Veritas or Legato 
¿?

Thanks In Advance,

Regards,


         Iban Bernaldo De Quiros Y Marquez 
Technical Specialist

Sun Microsystems, Inc.
Serrano Galvache, 56
Madrid 28033 ES
Phone +34 91 767 6233
Mobile + 34 659 01 91 12
Email Iban.Bernaldodequiros AT Sun DOT COM

         

-----Mensaje original-----
De: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] En nombre de 
Yiannakis Vakis
Enviado el: viernes, 14 de julio de 2006 12:16
Para: ADSM-L AT VM.MARIST DOT EDU
Asunto: [ADSM-L] Retention of backup versions

I'm sure this question has been asked many times but I want to be sure what is 
going on:

A mgnt class has been defined so that 5 versions of a file are kept, with a 
retention of 30 days.
A file that is changed daily is backed up for 5 consecutive days. The next 
backup is taken 3 months later.
What happens to the inactive files?
Thanks
Yiannakis


Yiannakis Vakis
Storage and Database Administration
Systems Support Group, I.T.Division
Tel. +357-22-848523
Mob. +357-99-414788
Fax. +357-22-337770


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.

<Prev in Thread] Current Thread [Next in Thread>