Restoring Shares from a Backup

Note: To perform a backup see Backing Up Shares and the Database.

Ensure that your IBM Aspera Shares backup is available.

Verify that you have copied the Shares backup files to your new machine. See Backing Up Shares and the Database.
Stop Shares services.
Stop the following services:
- Aspera Nginx Service
- Aspera Delayed Job Service
- Aspera Web Services
- Aspera Stats Collector
You can stop these services from the Computer Management window, accessible from Manage > Services and Applications > Services:
Update database.yml, cert.pem, and cert.key
Replace following files with the versions you backed up manually during the backup:
```
C:\shares\www\config\database.yml
C:\shares\nginx\conf\cert.pem
C:\shares\nginx\conf\cert.key 
```
Run the restore command.
To restore Shares, run the following command in a command prompt, where in this example, E:\aspera-shares-restore is the directory where the backup files are stored on the new server.
```
> cd C:\shares\www
> rake restore DIR=E:\aspera-shares-restore
> rake db:migrate  
> rake init  
> rake aspera:stats_collector:add_all_nodes  
```
Note: If the command prompt aborts the rake task with the error "Permission denied," close the command prompt. Right-click Command Prompt and select "Run as administrator". Otherwise, some of the rake tasks will throw errors on permission issues while overwriting existing files in Shares.
Start Shares services.
Restart the services from above:
- Aspera Nginx Service
- Aspera Delayed Job Service
- Aspera Web Services
- Aspera Stats Collector
You can start these services from the Computer Management window.