Your Personal Developer Instance (PDI) is scheduled for automatic reclamation

[akshayashetty]

I received the following email regarding PDI. This is not the inactivity monitor.

Is there a way to retain the PDI?

[Dr Atul G- LNG]

No mate. 

[Tanushree Maiti]

Hi @akshayashetty 

FYI ->Keeping PDIs Available for Active Builders: Upcoming PDI Reclamation Changes

[ralvarez]

Same happened to me this week: got the email, logged into the instance, it went offline anyway. So update sets are the right call, but doing it by hand every time is the part that never happens until it is too late.

I ended up automating it and put it on Share (free): Instance Backup lets you define what to export per table, runs on a schedule, and produces standard update set XML you just import and commit on the new PDI. It can also push each backup to external storage, so the copy survives even if the instance is reclaimed before you notice.

[KeDix]

@ralvarez so it ( Instance Backup ) needs to be downloaded and installed/imported and then configured for automation to work?

[ralvarez]

Yes, that is the flow, and it is a one-time setup. Download it from Share, import the update set into your PDI and commit it, then create a backup definition (which tables to capture and what to export from each) and give it a schedule. From there it runs on its own and produces the update set XML for each run, which you import and commit on the new instance if you ever need to restore.

If you also want the copies to survive the instance being reclaimed, add your external storage details and it will push each backup there.