Got it, let's break this down for you—since your Bitbucket Server on that Windows Server 2012 VM is dead and you can't confirm if local code is up to date, here's exactly what you need to do to get the latest source and find where Bitbucket stores its data:

Bitbucket Server Repository Storage Location on Windows #

First, let's track down where your code lives on the VM:

• Default path: Bitbucket Server stores all repository data in this directory by default:
  C:\Atlassian\ApplicationData\Bitbucket\shared\data\repositories
• Custom path check: If you changed the storage location during setup, open the bitbucket.properties file (usually at C:\Atlassian\ApplicationData\Bitbucket\shared\bitbucket.properties) and look for the plugin.bitbucket-git.storage.directory property—this line will point you to your custom repo storage folder.

Retrieving the Latest Source Code When Bitbucket Won't Start #

Assuming you can still access the VM's filesystem (either by logging into the server directly or mounting its disk to another machine), follow these steps:

1. Locate your target repository: Inside the repositories folder, each repo is stored in a numbered folder (like 1, 2, etc.). If you don't know which number matches your repo, check the repository-config subfolder (under C:\Atlassian\ApplicationData\Bitbucket\shared\data\)—each repo has a .properties file here that maps its ID (the folder number) to its name.
2. Clone the bare repository: Bitbucket stores repos as bare Git repos (no working directory with actual files). To get a usable working copy, clone this bare repo using Git:
   On Windows, run this command in Git Bash or Command Prompt:

   git clone C:\Atlassian\ApplicationData\Bitbucket\shared\data\repositories\1 my-working-repo
   

   Replace 1 with your repo's numbered folder, and my-working-repo with the name you want for your local working directory.
3. Confirm you have the latest code: Once cloned, run git log --oneline to see the most recent commits. The top entry is the latest version of your code.
4. If the VM won't boot at all: Mount the VM's disk to another Windows machine, navigate to the repo storage path we found earlier, and copy the bare repo folder. Then clone it as described above on the new machine.

A quick note: Make sure you have Git installed on the machine where you're doing the clone—if you don't, grab it from the official Git site (but since you're dealing with code, I'm guessing you already have it handy!).

内容的提问来源于stack exchange，提问作者Taher Stenberg