[prev in list] [next in list] [prev in thread] [next in thread] 

List:       adsm-l
Subject:    AW: Newbie question about version numbers and amount of backups
From:       Salak Juraj <J.Salak () ASAMER ! AT>
Date:       2007-07-31 11:32:25
Message-ID: 47CE942B4E710145A27E5339D5B34E014B06F5 () aohexchange01 ! asamer ! holding ! ah
[Download RAW message or body]

As Richard told, you can use TSM archives.

But you can scrutinise the statament about TSM only beeing able to store 5 to 7 file \
version only. This limitation is not a TSM technical limitation, TSM can store even \
unlimited amount of backup versions. 5 to 7 versions is merely a policy which your \
TSM administrator set-up using such values. she does have simple possibility to \
create another policy (called management class / backup copy group) And she can even \
apply it to your files only, leaving all other files with 5-7 backup versions. Sure, \
you must be able to define your files by either unique location and/or name pattern \
for this purpose.

If this policy change and consequent the slightly risen complexity of your TSM \
configuration and the higher demand on TSM Hardware ressources pays for your business \
requirement, only you and your TSM guy can decide.

It seem you are telling about 75 SQL server backups, 
in this case SQL backup agent should be considered.


best
Juraj




-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von \
                miggiddymatt
Gesendet: Montag, 30. Juli 2007 21:49
An: ADSM-L@VM.MARIST.EDU
Betreff: Newbie question about version numbers and amount of backups

I haven't actually used TSM very much (my organization has an employee that just \
works with TSM), but I was wondering what solutions there were for implementing \
something similar to a grandfather/father/son rotation scheme for keeping files that \
my organization backs up.

I've asked our TSM person for suggestions, but she's telling me that our only option \
is to save 5 or 7 copies of a file.   We don't have agents or the like for SQL \
servers, so currently we do a dump every night that gets backed up by TSM.   For many \
of my systems, this means we only have a backup of 5 or 7 days.

Currently my only option is to append the date onto the dump which forces TSM to keep \
it as a seperate file each day.  Is there any way to just keep different dates of the \
same file without me having to go back to my 75 SQL servers and change the job so \
that the date is on the end of each filename?  Thanks in advance for the help.

+----------------------------------------------------------------------
> This was sent by matt.self@msj.org via Backup Central.
> Forward SPAM to abuse@backupcentral.com.
+----------------------------------------------------------------------
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn \
Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, \
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das \
unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not \
the intended recipient (or have received this e-mail in error) please notify the \
sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or \
distribution of the material in this e-mail is strictly forbidden.


[prev in list] [next in list] [prev in thread] [next in thread]