Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup specific devices #2

Open
nitinmohan87 opened this issue Feb 20, 2014 · 0 comments
Open

Backup specific devices #2

nitinmohan87 opened this issue Feb 20, 2014 · 0 comments

Comments

@nitinmohan87
Copy link

Have a 'device' attribute for rightscale_backup resource which specifies what device to back up. At this moment, we backup all devices by default due to issues with RightScale API Backup resource and the design of this cookbook.

Suppose I have 2 volumes - "volume1" and "volume2" attached to an instance at "/dev/xvdg" and "/dev/xvdf" respectively. Now I create a backup as follows

rightscale_backup "my_backup" do
  lineage "test_lineage"
  devices ["/dev/xvdg", "/dev/xvdh"]
  action :create
end

The parameters to backup create API call are

params = {
  : backup => {
    :lineage => @new_resource.lineage,  # will be "test_lineage"
    :name => @new_resource.name,        # will be "my_backup"
    :volume_attachment_hrefs => hrefs   # will be an array of hrefs of volumes attached at ["/dev/xvdg", "/dev/xvdh"]
  }
}

After the backup is complete, I now end up with 2 snapshots both named "my_backup" in "test_lineage" lineage. When I restore this backup (containing 2 snapshots) I end up with 2 volumes attached to the instance with the same name "my_backup". Now, we cannot update the volume attributes in the node variable because the volumes have same name which causes a conflict.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant