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.
Related
I have two instances of Sonatype Nexus.
One of them is installed on a processing-focused machine, in other words, it has no disk space. So, I hold this instance to keep only our lighweight dependencies, such as small jars used by a lot of projects.
The other machine have enough disk space, but it is out of our network. I want to use it to keep the bigger dependencies, the ones we don't use frequently.
That said, I want to create a proxy repository into the first Nexus installation pointing to the installation that hold the biggest artifacts. But I don't want it to download the dependencies from the other, because it would cause a lot of headaches when deal to disk space. Do you guys have any idea on how to do it? I'll clarify, I need a proxy repository pointing to another Nexus installation that that don't download the artifacts when they're requested. Please, help.
I had a server that I linked to my current PC as "Z:\", and I had a repository there that I used for my programming commit/updates. There were multiple people working on the program, which warranted the need for a repository. We worked with Visual Studio and VisualSVN.
Unfortunately, my server died and we couldn't get it to start back up, so we've lost the repository. I have since bought and replaced my old server with a new one, but I'm having trouble re-creating the repository. For argument's sake, let's say that the copy of the program on my PC is the most updated one. How do I re-create the repository so that everyone can update/commit from there again?
In case there are multiple users who need access your repository, you should use a server, not direct file access schema (file://).
You must plan a backup strategy for your server and the repositories.
If you lost the storage that was holding the repositories, you lost the revision history of your projects. However, you should have the local copies of the project's data on your computers in form of working copies.
Search for working copies of your projects. The working copies will help you recover the latest state of your data and import it to a new SVN repository. Make sure that you do not import the hidden .svn metadata directory.
I have a Sonatype Nexus repository on an older machine, and I have purchased a newer server which will become my new repository host. In the installation of Nexus on the older machine I have an extensive collection of artifacts, the vast majority of which are now obsolete and can be safely removed from Nexus.
I know it is possible for me to move all of the artifacts from the old installation into the new installation by simply copying the sonatype-work directory to the new box. My question is this: If I want to prune the artifacts in that directory down to only what I need right now (probably about 20% of the repository contents) what steps would I have to take other than deleting the unwanted artifacts? For example, would I need to force Nexus to rebuild indexes? Thanks for the help!
You could just install the new Nexus and proxy off the old one via one proxy repo in addition to Central and other repos. Then you run this for a while and only things not found in other public repositories you configure will be proxied from the old Nexus instance.
At a later stage you could run scheduled task on the old repo that removed old items.
When you are satisfied you got everything you need, you do one last backup and then take the old Nexus instance offline.
Of course the other option is to just not worry and migrate it all. In the end you really only have to migrate what you actually deployed (so probably releases and 3rd party repos).
The easiest option btw. is to just copy the whole sonatype-work folder over to the new machine and fire it up with a new Nexus install there and flick the switch.
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.
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.