Code Backup Doc

tracking/Backups.md

@@ -0,0 +1,50 @@
+## Zowe Backups
+
+See https://github.com/zowe/zlc/issues/178 for background.
+
+This document details current backups methods used by the Zowe community, and to identify any gaps that may exist.
+
+### Source Code Backups
+
+Source code is not backed up outside of Github. Github provides mechanisms for restoring the source code to a given state, but does not provide backup capabilities outside redundant storage architecture for data at rest. 
+
+This is a possible gap, though, as far as I can tell, Github has never had an event with widespread data loss. We can still investigate [Github's article on backups](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/backing-up-a-repository).
+
+### Binary Artifact Backups
+
+Binary Artifacts (i.e., component releases, Zowe releases) are  backed by Artifactory cloud. The Artifactory cloud solution has an internal backup and restore procedure, [documented here](https://jfrog.com/knowledge-base/how-backup-works-for-artifactory-cloud/).
+
+For Zowe artifacts which we provide on Zowe.org (Convenience PAX, SMP/e, CLI Core/Plugin ZIP), these artifacts are  cloned into Amazon S3, and can be restored from Artifactory.
+
+All binary artifacts produced by Zowe can additionally be recreated from a source code snapshot.
+
+### Infrastructure Backups
+
+There are a few areas of infrastructure for Zowe:
+
+* z/OS Build Environments
+* Jenkins Build Environment
+* Zowe websites: zowe.org and docs.zowe.org.
+
+##### z/OS Build Environment
+
+There are two parts to our z/OS build environments, zD&T and z/OS guests. Our zD&T is available as an image which can be redeployed at any point in time. Image storage is unknown; vendor internal.
+
+ Our z/OS guests hosted by Marist are set up for monthly snapshot backups. These backups will not allow for incremental restoration / rollback - only the latest snapshot taken is available. Since the z/OS Guest systems change slowly and the only real case for rollback is disaster recovery, this limitation is acceptable.
+
+##### Jenkins Build Environment
+
+There are two Jenkins build environments currently in use by Zowe, and two aspects to Jenkins backups.
+
+First, we have two Jenkins environments: wash.zowe Jenkins and LinuxFoundation Jenkins (jenkins.zowe). The wash.zoweJenkins system is backed up periodically to Github. The LinuxFoundation Jenkins system is backed up by Linux Foundation team's process.
+
+Second, the Jenkins builds themselves. Jenkins builds in Zowe use declarative or scripted pipelines on the whole, and are stored as code in Github - so they are subject to source code backup backup. There are a few builds defined directly within Jenkins itself, and those backups are included in the Jenkins system backup. 
+
+##### Zowe Websites
+
+Both Zowe websites, zowe.org and docs.zowe.org, are stored as source code in Github, and deployed by Jenkins jobs. Both sites are as a result backed up via Jenkins backups and Github source backups.
+
+### Odds and ends
+
+Zowe Sample Code. This code is present in Github, and is covered by Github source backups.
+Community documentation - box, google docs, other? Github