Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor update to os units section

...

Cloud Servers may also generate usage based on the Operating System or Software installed on the Cloud Server.

  • OS Unit Elements (OS Units, REDHAT OS Units, SUSE OS Units, SUSE SAP OS Units, WINDOWS OS Units) - As described in more detail in Introduction to OS Units, each Operating System is a member of an OS Units Group. Each OS Units Group is defined to so that servers who are members of the group either incur a specific number of OS Units per hour based on the number of vCPU when the server is in a running state or do not to generate OS Units at all. If a server is a member of an OS Units Group that is defined to incur OS Units, the appropriate number of OS Units are generated per hour based on the vCPU configuration of the server. This usage is generated regardless of whether the server is in a running or stopped state. Each OS Units Group  is mapped to an OS Units Usage element and depending on the OS Type, may or may not generate Usage when a Virtual Server is deployed with that OS type. The Detailed Usage report does not provide asset-level information about this usage. See the Introduction article for complete details. For asset-level details on the usage calculation, see How to Create an OS Units Usage Report.
  • Software Units - As described in more detail in Introduction to Cloud ("Priced") Software, some OS Images include software for which usage is incurred. Each Priced Software package is defined to either incur a specific rate of Software Units based either on the number of vCPU or simply "per server". Separate rates are applied depending on whether the server is in a started or stopped state. If a Cloud Server has Priced Software, the appropriate number of Software Units are generated per hour based on the running state and, where necessary, the vCPU configuration of the server.  The Detailed Usage report does not provide asset-level information about this usage. For asset-level details on the usage calculation, see How to Create a Software Usage Report.

...

  • Cloud Server Snapshots - Servers provisioned with the Cloud Server Snapshot feature incur usage to either Essentials Snapshot Hours, Advanced Snapshot Hours, One Month Snapshot Hours, Three Month Snapshot Hours,  Twelve Month Snapshot Hours, or Long-Term Image Storage Hours based on the server's Snapshot Service Plan.  This usage begins being incurred immediately upon service enablement before any snapshots are taken or stored. In addition, if Snapshot Replication is enabled for a Server with the Advanced, One Month, Three Month or Twelve Month Snapshot plans, Usage will appear under Advanced Replicated Snapshot Hours, One Month Replicated Snapshot Hours, Three Month Replicated Snapshot Hours, or Twelve Month Replicated Snapshot Hours beginning from the time Replication was enabled on the Server.  Usage charges are based on the aggregate size of all of the local disks attached to the Cloud Server, and on the Service Plan selected (Essentials, Advanced, One Month, Three Month, or Twelve Month), as well as Snapshot Replication, if enabled. The charges apply to the total size of the disks, not the amount used by the Operating System, as the stored snapshot includes the exact state of all local disks (even if unformatted) and any Disks that are replicated to a secondary location. Likewise, Advanced Replicated Snapshot Hours, One Month Replicated Snapshot Hours, Three Month Replicated Snapshot Hours, or Twelve Month Replicated Snapshot Hours are incurred beginning from the time Replication was enabled on the Server. Usage stops when the service is disabled. Usage will continue to be incurred until Replication is fully disabled. The “(Snapshot Plan) Snapshot Service Hours” and "(Snapshot Plan) Replicated Snapshot Hours" usage charges are in addition to the normal Economy/Standard/High-Performance usage charges for local disks that are described in Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds:
      • EXAMPLE 1: A Cloud Server with 30 GB of Standard local storage and 50 GB of High-Performance local storage will generate 30 Storage Hours per hour and 50 High-Performance Hours per hour. If this Server is enabled for Cloud Server Snapshots, it will continue to generate 30 Storage Hours and 50 High-Performance Hours per hour but will now additionally generate 80 (Essentials, Advanced, One Month, Three Month or Twelve Month) Snapshot Service Hours so long as the Snapshot service is enabled. If disks are added or removed from the Cloud Server while enabled, the (Essentials, Advanced, One Month, Three Month or Twelve Month) Snapshot Service Hours will be adjusted automatically.
      • EXAMPLE 2: A Cloud Server enabled for Twelve Month Snapshots with 30 GB of Standard local storage and 50 GB of High-Performance local storage will generate 30 Storage Hours per hour and 50 High-Performance Hours per hour totaling 80 Twelve Month Snapshot Service Hours. If this Server is also enabled for Replicated Snapshots, it will generate an additional 80 Twelve Month Replicated Snapshot Hours as long as Snapshot Replication is enabled on the Server.
    • In addition, note that a "Snapshot Preview" Cloud Server that is newly created from a Snapshot (Local or Replicated) as described in How to Create a "Snapshot Preview" Cloud Server from a Successful Historical Snapshot incurs all local disks as Standard Disk Speed rates ("Storage Hours") while it is in Snapshot Preview mode. Local disks incur normal disk speed usage only after the server is migrated to a "Normal" server as described in How to Migrate a "Snapshot Preview" Server to a Normal Cloud Server.

      From a reporting perspective, details of Snapshot Usage (and Replicated Snapshot usage) are contained in the Snapshot Usage report

      is migrated to a "Normal" server as described in How to

      Generate a Snapshot Usage Report

...

titleEssentials and Advanced Snapshot Plans End of Sale Effective October 24, 2019
  • Cloud Monitoring - Servers provisioned with the Cloud Monitoring feature incur usage to Essentials Monitoring Hours and Advanced Monitoring Hours based on the server's Cloud Monitoring Plan. For each hour a Cloud Server is provisioned with a given Cloud Monitoring Plan, it will generate one quantity to the associated usage element. For example, if a Cloud Server is provisioned with Advanced Cloud Monitoring, it will generate 24 Advanced Monitoring Hours per day so long as the server remains provisioned with that plan.
  • DRS for Cloud - Use of the DRS for Cloud service generates usage across two different elements:
    • DRS Source Server Hours - Each Source Server in a DRS Consistency Group contributes one hour of usage to this element for each hour it is a member of the Consistency Group. This usage is attributed to the data center location of the Source Server.
      1. Example: User creates a Consistency Group at Noon with two Source Servers in NA9 paired with two Target Servers in NA12. This configuration will generate 24 DRS Source Server Hours in NA9 on the first day (12 hours x 2 Source Servers = 24 Source Server Hours) and 48 DRS Source Server Hours/day thereafter until the Consistency Group is deleted. 
      2. Asset-level details on how this usage is computed can be identified through the DRS Pairs Usage report. This report identifies each Source Server / Target Server pair in a Consistency Group and how usage was computed for the Source Servers in those groups for each day. For details, see How to Generate a DRS Pairs Usage Report.
    • DRS Storage Hours - A Consistency Group includes a specific amount of DRS Journal storage in both the Source and Target locations. This usage is attributed to the DRS Storage Hours element separately in each location in the same manner that other disk storage usage is computed - one hour for each GB of DRS Journal storage.
      1. Example: User creates a Consistency Group at Noon with two Source Servers in NA9 paired with two Target Servers in NA12 and allocates 10,000 GB of DRS Journal Storage to the Consistency Group. On the first day, this configuration will generate 12,000 DRS Storage Hours in NA9 (12 hours x 10,000 GB = 12,000 DRS Storage Hours) and another 12,000 DRS Storage Hours in NA12. Thereafter, both NA9 and NA12 will be attributed 24,000 DRS Storage Hours/day until the Consistency Group is deleted. 
      2. Asset-level details for this usage appears on the Detailed Usage report. Each location's DRS Journal will appear on a separate row in the report with a column identifying the amount of DRS Journal storage and the attributed DRS Storage Hours.
    • Security GroupsSecurity Groups usage appears on the Summary and Security Group Usage reports under the usage element Security Group Hours.
      Security Group Hours start accruing starting from the time that either:
      1. A Cloud Server is added to a Server Security Group, or
      2. The first Server NIC is added to a VLAN Security Group
        Security Group Hours will continue to accrue until either the Cloud Server is removed from a Security Group or all Server NICs on a given Cloud Server are removed from Security Groups. usage element.
        From a reporting perspective, details of Security Group Usage are contained in the Security Group Usage report as described in How to Create a Security Group Usage Report

...