[google-appengine] Re: Data recovery appspot

[James Calfee]

The project at the time was secure-gem .. I ported it to secure-gem2 but 
secure-gem2 does not have the backing data..

On Monday, June 19, 2017 at 6:18:15 PM UTC-5, James Calfee wrote:
>
> Hi, sorry for the delay.  
>
> The data-store upgrade was shortly after:
>
> 7/1/2015
>
> I have attached the email I received about the upgrade.  I was able to 
> upgrade my app's front-end, but for some reason I was not able to upgrade 
> the data store.  The data-store upgrade required an external tool (command 
> line) and I had some issue running it.  I'll be happy to enable support on 
> my account (silver or so).  I think I need someone to verify me and fetch 
> the data manually.  Or better yet just upgrade it into the new front-end 
> app so I can get to the blobstore again.
>
> Here is the email about the data upgrade:
>
> Dear App Engine Developer, 
>
> You are receiving this email because you are listed as an owner of a 
> Google App Engine application that is configured to use the deprecated 
> service Master/Slave Datastore, which will soon be shut down. Don’t worry 
> though, this email gives clear instructions for what you need to do. Even 
> if your application does not store data in Master/Slave Datastore, it is 
> still configured to use Master/Slave Datastore, so please keep reading. 
>
> When we launched App Engine, Master/Slave Datastore was the only database 
> service that applications could use to store data. Master/Slave Datastore 
> had issues scaling with the size and complexity of applications running on 
> App Engine, so we launched its successor, High Replication Datastore 
> (HRD), in 2011. Since that launch HRD has proven to scale without issues 
> <http://googleappengine.blogspot.com/2012/01/happy-birthday-high-replication.html>.
>  
>
>
> One of our core goals with Google Cloud Platform is to provide customers 
> with the best technologies to build their business, so when we saw that HRD 
> was a more robust technology, we decided to make HRD the default database 
> service. On April 4 2012 we announced 
> <http://googleappengine.blogspot.com/2012/04/masterslave-datastore-thanks-for-all.html>
>  
> the deprecation of Master/Slave Datastore -- our signal that three years 
> from that date we would formally shut down the service. 
>
> That three years is upon us and, as mentioned above, one or more 
> applications that you own (listed below) are running on Master/Slave 
> Datastore. If you don’t take any action these applications will be shutdown 
> on *July 6, 2015* and will no longer serve traffic (users will see HTTP 
> 404 responses). 
>
> To ensure that these applications continue to operate, you’ll need to 
> follow these few steps for each application:
>
>- Log into the Google Developers Console 
><https://console.developers.google.com/>.
>- Create a new project, which in turn creates a new HRD application.
>- Use the HRD Migration Utility 
><https://cloud.google.com/appengine/docs/adminconsole/migration> to 
>migrate any Master/Slave data to the new HRD application.
>
>
> *An important note*: You need to follow the above steps even if your 
> application does not store any data because your application is 
> *configured* to use the Master/Slave Datastore. For example, even if it’s 
> a static HTML website. When we shut down the Master/Slave Datastore these 
> applications will be also shut down if they are not migrated. 
>
> *For applications on the Java 6 runtime*: Java 6 apps must be upgraded to 
> Java 7 prior to the migration to HRD. 
> To determine whether your app is a Java 6 app:
>
>- Visit the App Engine Admin console <https://appengine.google.com/>, 
>and select your application.
>- In the left navigation pane, click *Versions* to display the 
>versions page.
>- At the top of this form, click *Try the new Versions page*.
>- The Java runtime used by your app will be listed under *RUNTIME*.
>
>
> To upgrade:
>
>- Update your development environment to use the latest App Engine 
>Java SDK.
>- Redeploy your app to production App Engine.
>- Test it for correct behavior. There are a small number of potential 
>compatibility issues 
><http://www.oracle.com/technetwork/java/javase/compatibility-417013.html> 
>between Java 6 and Java 7.
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/db847949-9ce5-4df6-95f2-f3c270f33630%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Data recovery appspot

[James Calfee]

Hi, sorry for the delay.  

The data-store upgrade was shortly after:

7/1/2015

I have attached the email I received about the upgrade.  I was able to 
upgrade my app's front-end, but for some reason I was not able to upgrade 
the data store.  The data-store upgrade required an external tool (command 
line) and I had some issue running it.  I'll be happy to enable support on 
my account (silver or so).  I think I need someone to verify me and fetch 
the data manually.  Or better yet just upgrade it into the new front-end 
app so I can get to the blobstore again.

Here is the email about the data upgrade:

Dear App Engine Developer, 

You are receiving this email because you are listed as an owner of a Google 
App Engine application that is configured to use the deprecated service 
Master/Slave Datastore, which will soon be shut down. Don’t worry though, 
this email gives clear instructions for what you need to do. Even if your 
application does not store data in Master/Slave Datastore, it is still 
configured to use Master/Slave Datastore, so please keep reading. 

When we launched App Engine, Master/Slave Datastore was the only database 
service that applications could use to store data. Master/Slave Datastore 
had issues scaling with the size and complexity of applications running on 
App Engine, so we launched its successor, High Replication Datastore (HRD), 
in 2011. Since that launch HRD has proven to scale without issues 
.
 


One of our core goals with Google Cloud Platform is to provide customers 
with the best technologies to build their business, so when we saw that HRD 
was a more robust technology, we decided to make HRD the default database 
service. On April 4 2012 we announced 

 
the deprecation of Master/Slave Datastore -- our signal that three years 
from that date we would formally shut down the service. 

That three years is upon us and, as mentioned above, one or more 
applications that you own (listed below) are running on Master/Slave 
Datastore. If you don’t take any action these applications will be shutdown 
on *July 6, 2015* and will no longer serve traffic (users will see HTTP 404 
responses). 

To ensure that these applications continue to operate, you’ll need to 
follow these few steps for each application:

   - Log into the Google Developers Console 
   .
   - Create a new project, which in turn creates a new HRD application.
   - Use the HRD Migration Utility 
    to 
   migrate any Master/Slave data to the new HRD application.


*An important note*: You need to follow the above steps even if your 
application does not store any data because your application is *configured* 
to use the Master/Slave Datastore. For example, even if it’s a static HTML 
website. When we shut down the Master/Slave Datastore these applications 
will be also shut down if they are not migrated. 

*For applications on the Java 6 runtime*: Java 6 apps must be upgraded to 
Java 7 prior to the migration to HRD. 
To determine whether your app is a Java 6 app:

   - Visit the App Engine Admin console , 
   and select your application.
   - In the left navigation pane, click *Versions* to display the versions 
   page.
   - At the top of this form, click *Try the new Versions page*.
   - The Java runtime used by your app will be listed under *RUNTIME*.


To upgrade:

   - Update your development environment to use the latest App Engine Java 
   SDK.
   - Redeploy your app to production App Engine.
   - Test it for correct behavior. There are a small number of potential 
   compatibility issues 
    
   between Java 6 and Java 7.

 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/220a52a6-fb99-49e7-a628-6a81b4668295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Data recovery appspot

[James Calfee]

I need to recover an old app from appspot.com .. I attempted to migrate it 
in 2014 but it did not port the data store back-end only the UI ported.  I 
really need the old blob-store data.  Can someone please direct me in the 
right direction?  Do you recall what this datastore upgrade was called?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/bc3c1335-7b66-4e36-aa27-cc99b6b834bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.