What effect does deleting EC2 snapshots have? - amazon-ec2

I'm not sure what effect deleting an EC2 snapshot has on the other ones. For example, if I snapshot an EBS volume 4 times and delete the oldest one, can I still do a full restore from the latest ones? In other words, is there any benefit in keeping old snapshots other than to save incremental changes?

The only benefit is being able to restore to the older snapshot. Deleting one snapshot does not effect any of the others. Feel free to get rid of the old ones. The new ones will still work.

Related

Advising on what to do with 4 year old snapshot on HyperV

I recently came across a server in a client that they have very old snapshots.
What should I do with these insanely old snapshot? Is there a risk of virtual disk corruption if I exclude all these snapshots?
Should I exclude one by one? Oldest to newest? Or exclude the whole snapshot tree at once?
I suggest export this particular VM to some backup location, then try to delete snapshot tree. In case something goes wrong restore VM from exported location.

TeamCity not picking up VCS changes after server rollback

We are using TeamCity 9.0.0. The server got corrupted for reasons not relevant to this discussion, so I had to rollback to a stable snapshot (we use Amazon AWS snapshots), which was roughly 12 hours old. I lost some of the builds that happened during those 12 hours but that's ok.
The restore seemed to work, but now the VCS Triggers are not happening. The VCS root is from TFS 2013.
I tried checkin in new changes and builds still don't trigger. I tried running the build manually and it doesn't pick up the latest changes.
It looks like something got out of sync when I restored the snapshot.
Thoughts?
--------Update 1 -------
I looked at the history and I see several builds triggering after I rolled back my server so I think that is not related. I tried creating a new VCS root and removing the existing one. I checked in a change and the build triggered fine. I tried a second check in and this time the build didn't trigger. It's almost like it misses some changesets.
Try cleaning Server cache at <TeamCity Data Directory>/system/caches. If even that doesn't work try deleting and re-creating the VCS.

UberSVN on Windows: Take a backup of all repositories at once and restore them

I am new to SVN and UberSVN on windows. I am using UberSVN 12.04 Free edition (not using any uberapp.)
I would like to know if there is anyway in which I can take the backup of all the repositories at once?
I know that I can take one by one backups for every Repo.
Is there any way that I can take backups and restore it at once and it playes well with Uberportal as well. (shows in the repositories tab)
Some detail will be appreciated as I am not to familar with SVN and its configuration.
You can just copy the entire directory if you want to take a cut of your repo's outside of the svn backup options.
There isn't a way to add multiple repo's at once to uberSVN at the moment, you would need to do these individually.
It is something that has been discussed from time to time, but if it's a feature you deem important I'd recommend raising it via the suggestion area here, then other users can see it and comment etc and we can assess demand.

How to take backup of StarTeam project

I have a project repositiory on Start Team server.
I need to take regular back up the same.
How can I achieve this?
The Star team backup steps are given in the Appendix C of the “The StarTeam Administrator’s Guide.pdf”
It depends on what you mean by backing up the Project. If you mean backing up the entire repository then StarTeam makes this really easy. You just need a snapshot of the DB and a full copy of the repository files (full steps are documented.) However, if you mean backing up a specific Project in the repository, and ONLY that Project, with all history intace, then this is not currently possible--or at least it is a major challenge.
StarTeam used to have an ability to Import/Export projects but they discontinued support and development of that tool years ago. If you wish to back up a single Project independent of the rest of the server, then this is still possible, and useful in the case where you want to split the repository into a separately managed repository. Here is how to do that:
Create a duplicate repository including all of the repository files.
Delete everything from the clone except for the Project(s) that you want to split off -- note that in StarTeam 2011 the Project Delete was broken, so you may need to do this in a direct SQL query which marks the projects/views as deleted. Contact Support if you run into problems deleting manually, especially if you have a large repository.
Once your clone has been pruned of unnecessary projects, run the Online Purge tool until all projects and respective files have been removed from the DB and the Vault.
You can now change what you need to change on the new repository, such as the users, groups, security, etc. without affecting the first repository.
Once you have validated the new repository is working properly, you can then run a similar process on the first repository to get rid of the projects that were split off.
Another potential use for this is if you had reached end of life for a project and you wanted to keep it offline and backed up but wanted it to be restorable with full history on demand (for regulatory purposes, etc.) while being freed up to remove it from the active repository so you can make other projects run faster. Though this is probably best done in batches of projects as the process is currently quite labor intensive to perform.

Xcode : Recover complete project from snapshot?

today I am playing a bit with the Xcode snapshot feature and I wonder if I could recreate a complete project from a snapshot if all code is lost.
It seems to me in the Snapshot-Manager I can only see snapshots of the current project, not of all projects. So if my projectfile is lost or damaged is there anyway to recover my files from a snapshot?
I also wonder were the snapshots are saved. Not in the project folder I found out already.
Go to the "Projects" tab in the Xcode Organizer and select your project. You should see all the snapshots that have been made. Select the snapshot you want to restore to and select "Export Snapshot" to save it somewhere to disk. What you export to disk is your "recovered" version of your project.
I agree systems such as SVN and Git are far superior to Xcode's snapshot mechanism for version control. However, the snapshot mechanism can be very useful. For example, I just made a change to a project. Before making the change, Xcode asked me if I'd like to take a snapshot. After the change it turned out that I didn't want to make that change and so I used this mechanism to restore the project to the prior state.
Before trusting Xcode snaphot feature too much, may I suggest you to consider source code management with CVS, SVN or Perforce (integrated in Xcode)?
For me, the main usage of snapshot is during a refactoring session: You create a snapshot before applying refactoring changes, so that you are able to revert your modifications.
Have a look in your home folder:
~/Library/Application Support/Developer/Shared/SnapshotRepository.sparseimage
Within this you'll find the project snapshots.
But, you're better off using a proper source control system
Since there has been some remarks concerning version control systems. I would really advice to give git a chance. If you include the xcode specific files into the git repo, then you have the same effect as the snapshot mechanism.
So if you have a project that is not git controlled at the moment you can just use one of these howtos to create a git repo:
Using Git with an existing XCode project
And then don't forget to add the .xcodeproj directory and things should be a bit smoother.
I really dislike Linus Torwald at times, but git is just the best VCS I ever came across.
This document explains how snapshots are restored:
http://developer.apple.com/library/ios/#documentation/IDEs/Conceptual/Xcode4TransitionGuide/SCM/SCM.html

Resources