Can’t purge an old snapshot because it’s the previous timeflow of a refreshed VDB

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
DelphixEngine snapshot ''@2016-04-26T21:00:01.000''> delete

DelphixEngine snapshot ''@2016-04-26T21:00:01.000'' delete *> commit

 Error: Could not delete EMRT_PROD_dSources/Mars@2016-04-26T21:00:01.000

        because the following dependent datasets exist:


Action: Delete the dependent datasets and try again.

Why is it doing that?

DelphixEngine> database

DelphixEngine database> select Mars_0045/Mars_s5dev3

DelphixEngine database 'Mars_s5dev3'> ls


  type: MSSqlDatabaseContainer

  name: Mars_s5dev3

  creationTime: 2016-04-27T19:23:23.724Z

  currentTimeflow: 'DB_REFRESH@2016-05-24T11:20:46'

  description: (unset)

  group: Mars_0045

  os: Windows

  performanceMode: DISABLED

  previousTimeflow: 'DB_PROVISION@2016-04-27T15:23:27'

  processor: x86

  provisionContainer: EMRT_PROD_dSources/Mars

  reference: MSSQL_DB_CONTAINER-336


      type: MSSqlDBContainerRuntime

      logSyncActive: false


      type: SourcingPolicy

      loadFromBackup: false

      logsyncEnabled: false

  validatedSyncMode: DELPHIX_MANAGED

If you look above the currentTimeFlow is from May 24th    currentTimeflow: 'DB_REFRESH@2016-05-24T11:20:46'

Why is it showing the PreviousTimeFlow is from April 27th??? previousTimeflow: 'DB_PROVISION@2016-04-27T15:23:27'

We originally provisioned the VDB 'Mars_s5dev3' from dSource timecard 2016-04-27T15:23:27', then we refreshed it yesterday with 2016-05-24T11:20:46...

why does the PreviousTimeFlow impacting us in Deleting the 2016-04-27T15:23:27' timecard???

Will it eventually release, or should we go delete the timeflow?

Photo of Thom T

Thom T

  • 838 Points 500 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of Jatinder Luthra

Jatinder Luthra, Employee

  • 3,198 Points 3k badge 2x thumb
Hello Thom,                            

                Every Refresh/Rewind operation will create a new timeflow in Delphix.

It is normal for Delphix to hold the current and most recent timeflow because the old timeflow needs that dSource snapshot for undo functionality. It’s subject to retention, just like any other timeflow and you can override it by deleting the old timeflow.

You will find more information about timeflow and snapshots under Capacity Management screen on Delphix GUI or from Delphix Command Line Interface (CLI).
Photo of Thom T

Thom T

  • 838 Points 500 badge 2x thumb
Thank you Jatinder. This explains the behaviour.