We are actually using a version control program called Continuus and moving
to CVS in the future.
My question was more how daily backups are handled in terms of file changes
.. If you keep 5 copies of a file , is that enough ? If the file is modified
in one week five times and the backup picks up all five versions, then the
oldest one will be dropped when the backup finds the file changed for the
sixth time. Then, the oldest backup of the file that I can go back to is the
next to last one dropped. Yes, I realize that it depends on company policy,
but are there any guidelines to work off of ?
Rich
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Hurst, David(LIT)
Sent: Wednesday, October 13, 2004 3:54 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Versioning
Richard
I would highly recommend using a versioning tool such as CVS for change
control . This only stores the delta's between versions making it much more
efficient in terms of storage . We use it in our software house , the
backend is based on MySql which we dump to file each night ( after doing a
DB check) we then use TSM to back it up keeping 3 most current versions of
the file and with a delete retention of 90 days , the same as we have for
all other files (Corporate standard ).
This allows the developers to implement their own number of versions and
trees on a project by project basis , and the systems guys less headaches
trying to keep everyone happy .
David Hurst
Senior Systems Engineer
-----Original Message-----
From: Richard Mochnaczewski [mailto:RichardM AT INVERA DOT COM]
Sent: 12 October 2004 19:34
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Versioning
Hi,
We are currently implementing Tivoli as our backup soltuion for all our AIX
and Windows servers. As far as versioning, is there some sort of guideline
most people are using as far as number of verisons of a specific file to
keep ? We are primarily a software production house and I'm trying to
figure out what is the mose useful versioning route to go by.
Rich
****************************************************************************
This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying
of this e-mail or the information it contains by other than an intended
recipient is unauthorized. If you received this e-mail in error, please
advise me (by return e-mail or otherwise) immediately.
Ce courriel est confidentiel et prot+AOk-g+AOk-. L'exp+AOk-diteur ne renonce pas aux
droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou
copie de ce message ou des renseignements qu'il contient par une personne
autre que le (les) destinataire(s) d+AOk-sign+AOk-(s) est interdite. Si vous recevez
ce courriel par erreur, veuillez m'en aviser imm+AOk-diatement, par retour de
courriel ou par un autre moyen.
****************************************************************************
This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying of
this e-mail or the information it contains by other than an intended recipient
is unauthorized. If you received this e-mail in error, please advise me (by
return e-mail or otherwise) immediately.
Ce courriel est confidentiel et prot+AOk-g+AOk-. L'exp+AOk-diteur ne renonce pas aux droits
et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce
message ou des renseignements qu'il contient par une personne autre que le
(les) destinataire(s) d+AOk-sign+AOk-(s) est interdite. Si vous recevez ce courriel par
erreur, veuillez m'en aviser imm+AOk-diatement, par retour de courriel ou par un
autre moyen.
|
