Hi JFrog guys,
I have a question about the behaviour of the "Incremental" option for backups,
described at http://www.jfrog.com/confluence/display/RTF/Managing+Backups. I
had assumed that "incremental" meant the same sort of thing as incremental
backups generally do (to me): each run just adds all the new files which have
appeared since the previous run.
In particular, I would expect that
* files which were added and then deleted between backups would not be
backed up; and
* nothing would ever be deleted from the incremental backup area.
Evidence from our server over the last few days suggests I'm misunderstanding.
On Friday, an error was made in an automated build script such that an
integration repo on our main Artifactory server filled up the filestore over
the weekend. Yesterday I was on holiday but logs and discussions tell me that,
in the evening, the job was fixed and lots of unneeded builds were deleted. So
far, so good.
However, free space on our backup drive jumped up when the next backup run
happened. The other admins confirm that they didn't change anything (e.g.,
delete files from the backup disk), and our IT department didn't unexpectedly
increase the disk size on our VM.
So, the only explanation which makes sense to me is that "incremental backup"
actually means that Artifactory produces a backup which just contains the
current day's state, but does so by doing an incremental change since the
previous backup: all newly-added files are added to the backup, and all deleted
files are deleted from the backup. If so, that's a surprise to me - that's not
what I expect "incremental backup" to mean. If others agree, maybe the
documentation needs to be clearer. If that's not the explanation, I'd love to
know what is. I've looked through logs but don't see any details about the
backup process adding and removing files, just the number of "nodes" for each
repo on each backup.
As it happens, we will have older backups, because our IT department backs up
the entire VM on a roughly-logarithmically expiring basis. But I had assumed
that, since the "retention period" was inapplicable, everything was retained
forever. Am I wrong?
Regards,
Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel + 44 (0)131 472 4792 / Fax + 44 (0) 131 472 4799
http://www.tmvse.com / mailto:[email protected]
DISCLAIMER
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified that
any dissemination, distribution or copying of this message and/or attachments
is strictly prohibited. The company accepts no liability for any damage caused
by any virus transmitted by this email. Furthermore, the company does not
warrant a proper and complete transmission of this information, nor does it
accept liability for any delays. If you have received this message in error,
please contact the sender and delete the message.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
