You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/06 18:02:00 UTC

[jira] [Commented] (CLOUDSTACK-10222) Clean previous snaphosts from primary storage when taking new one

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354249#comment-16354249 ] 

ASF GitHub Bot commented on CLOUDSTACK-10222:
---------------------------------------------

khos2ow commented on issue #2398: CLOUDSTACK-10222: Clean previous snaphosts from primary storage when …
URL: https://github.com/apache/cloudstack/pull/2398#issuecomment-363510373
 
 
   @rhtyd @rafaelweingartner @wido @DaanHoogland Since 4.11 is out can we get this PR going again?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Clean previous snaphosts from primary storage when taking new one
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10222
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10222
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Secondary Storage, Snapshot, XenServer
>    Affects Versions: 4.10.0.0, 4.11.0.0
>         Environment: XenServer, Swift
>            Reporter: Khosrow Moossavi
>            Priority: Major
>              Labels: easyfix
>             Fix For: 4.11.0.0
>
>
> When user creates a snapshot (manual or recurring), snapshot remains on the primary storage, even if the snapshot is transferred successfully to secondary storage. This is causing issues because XenServer can only hold a limited number of snapshots in its VDI chain, preventing the user from creating new snapshots after some time, when too many old snapshots are present on the primary storage. 
> {code:java}
> reason: SR_BACKEND_FAILURE_109 The snapshot chain is too long
> {code}
> Proposed solution:
> Keep only one snapshot (last successful) on the primary storage regardless that it was a full or partial snapshot.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)