title: Google nearline pricing on overwrites
body: <p>I have Google Nearline storage set up and working fine via gcloud/gsutil. </p>
  
  <p>So far I have been using rsync to back some databases up eg...</p>
  
  <pre><code>rsync -d -R  /sourcedir/db_dir gs://backup_bucket/
  </code></pre>
  
  <p>Currently the files are datastamped in the filename, so we get a different filename every day. </p>
  
  <p>I've just spotted the mention of early deletion charges (currently on trial).</p>
  
  <p>I'm assuming whenever I delete a file with -d, I will get charged for that file up to 30 days ? If so, there's no point deleting it before then (but will get charged).</p>
  
  <p>But if I keep the filename the same, but overwrite the file with the latest days backup, the text says...</p>
  
  <p>"if you create an object in a bucket configured for Nearline, and 10 days later you overwrite it, the object is considered an early deletion and you will be charged for the remaining 20 days of storage."</p>
  
  <p>So I'm a bit unclear, if I have a file and overwrite it with a new version, am I then charged <em>again</em> for each file/day, every time its updated as well as the new file ?</p>
  
  <p>eg, for one file, backed up daily via rsync (assuming same filename this time)...over 30 days</p>
  
  <pre><code>day1 myfile is created
  
  day2 myfile is updated
  
  day3 myfile is updated
  
  ... and so on
  </code></pre>
  
  <p>Am I now being charged (filespaceday1 * 30days) + (filespaceday2 * 29days) + (filespaceday3 * 28) and so on... just for the one file (rather than filespace * 30 days)?</p>
  
  <p>Or does it just mean, if I create a 10gig file, and overwrite it with a 2meg file, I will be charged for 10gig for the 30 days (and ignore the 2meg file costs) ?</p>
  
  <p>If so, are there any best practices for rsync and keeping charges down ?</p>