Administering Bitbucket Data Center in Azure
Once you've deployed Bitbucket Data Center to Azure using the reference deployment template, administering the application is similar to managing an application on your own hardware. The exception being that you'll need to go via the jumpbox to access your nodes, and shared home directory.
To access your jumpbox and nodes you'll need:
- The SSH credentials you provided during setup.
- The public DNS name or IP address of your load balancer (you can obtain this through the Azure portal via Menu > Resource groups > <your resource group> > bitbucket-lb-public-ip).
- The node IP addresses, listed against the bitbucketbbs-nodes
(instance n)row in Connected devices. (You can obtain this through the Azure portal via Menu > Resource groups > <your resource group> > bitbucket-vnet).
Connecting to your Azure jumpbox and nodes over SSH
You can access the jumpbox via a terminal, or using the command line using:
$ eval $(ssh-agent) $ ssh-add ~/.ssh/id_rsa $ ssh -A JUMPBOX_USERNAME@DNS_NAME_OR_IP_ADDRESS_OF_THE_LOAD_BALANCER
Once you've accessed the jumpbox, you can jump to any of the nodes in the cluster, using:
$ ssh NODE_IP_ADDRESS
Accessing your configuration files
For your Azure deployment, you may need to make changes to your bitbucket.properties file, just as you would for a deployment on your own hardware.
your shared bitbucket.properties lives in /var/atlassian/application-data/bitbucket/shared/bitbucket.properties
The shared home is mounted on each node under /var/atlassian/application-data/bitbucket/shared.
So from an existing node (when you're logged in through SSH), you can go to /var/atlassian/application-data/bitbucket/shared
We recommend you use the Azure native backup facility, which utilizes snapshots to back up your Bitbucket Data Center.
Migrating your existing instance into Azure
We recommend you use the standard options available to migrate data between Bitbucket instances.