Eksporter (0) Skriv ut
Vis alt
EN
Dette innholdet er ikke tilgjengelig på ditt språk, men her er den engelske versjonen.

Setting a Storage Analytics Data Retention Policy

Updated: March 10, 2014

By default, Storage Analytics will not delete any logging or metrics data. Blobs and table entities will continue to be written until the shared 20TB limit is reached. Once the 20TB limit is reached, Storage Analytics will stop writing new data and will not resume until free space is available. This 20TB limit is independent of the total limit for your storage account. For more information on storage account limits, see Azure Storage Scalability and Performance Targets.

There are two ways to delete Storage Analytics data: by manually making deletion requests or by setting a data retention policy. Manual requests to delete Storage Analytics data are billable, but delete requests resulting from a retention policy are not billable.

ImportantImportant
To avoid unnecessary charges, set a retention policy for logging and metrics.

You can configure two data retention policies: one for logging and one for metrics. When enabled for both, Storage Analytics will delete logs and table entries older than the specified number of days. The maximum retention period is 365 days (1 year).

noteNote
When you make any changes to your retention policy, it may take several minutes for your settings to be applied.

To set up a policy that deletes both logging and metrics data after 7 days, make a request to the Set Blob Service Properties, Set Table Service Properties, or Set Queue Service Properties operation with the <RetentionPolicy> nodes configured like shown:

…
<RetentionPolicy>
    <Enabled>true</Enabled>
    <Days>7</Days>
</RetentionPolicy>
…

The following XML shows the <RetentionPolicy> nodes in the context of complete payload for a Set Blob Service Properties request:

<?xml version="1.0" encoding="utf-8"?>
<StorageServiceProperties>
    <Logging>
        <Version>1.0</Version>
        <Delete>true</Delete>
        <Read>false</Read>
        <Write>true </Write>
        <RetentionPolicy>
            <Enabled>true</Enabled>
            <Days>7</Days>
        </RetentionPolicy>
    </Logging>
    <HourMetrics>
        <Version>1.0</Version>
        <Enabled>true</Enabled>
        <IncludeAPIs>false</IncludeAPIs>
        <RetentionPolicy>
            <Enabled>true</Enabled>
            <Days>7</Days>
        </RetentionPolicy>
    </HourMetrics>
    <MinuteMetrics>
        <Version>1.0</Version>
        <Enabled>true</Enabled>
        <IncludeAPIs>false</IncludeAPIs>
        <RetentionPolicy>
            <Enabled>true</Enabled>
            <Days>7</Days>
        </RetentionPolicy>
    </MinuteMetrics>
    <DefaultServiceVersion>2013-08-15</DefaultServiceVersion>
</StorageServiceProperties>

You can also configure a retention policy that uses different periods for logging and metrics. To disable a retention policy in the future, call the Set Blob Service Properties operation with the <Enabled> node inside set to false, as shown below:

…
<RetentionPolicy>
    <Enabled>false</Enabled>
    <Days>7</Days>
</RetentionPolicy>
…
noteNote
If you disable Storage Analytics for a storage service but a data retention policy is enabled, your old data will continue to get deleted. To avoid accidental data loss, ensure that you configure your data retention policy when enabling and disabling Storage Analytics.

See Also

Vis:
© 2014 Microsoft