Instances removed for Hyperledger service in Cloud Foundry - Trial account

[former_member251760]

Hi Team,

I was working on Hyperledger service in cloud foundry, and created instances for Channel, and node. After completing the development and deploying the chaincode, I stopped using it for a while, and today when I logged into the cockpit, I was greeted with a message that "it looks like you are logging in for the first time", and an account was created (subaccount).

When I checked in the hyperledger service, I did not see the old stuff created and deployed, can someone from SAP help test the changes to my account... in the recent 30 day period?

Thank you

[mariusobert · Accepted solution]

Is it possible that your trial account expired? Each trial phase lasts for 30 days, which you can extend twice (e.g. up to 90 days in total).

When these 90 days are over, your trial account will be removed.

[former_member251760 · Accepted solution]

Yes, It was about to expire and should have actually expired in the duration after which I logged in back.

What I need assistance with is, restoring the state of account so that my objects can be retrieved, I had a working scenario set.

[mariusobert · Accepted solution]

I'm afraid there is no way to restore these objects as it is only a free trial service. Sorry.

[former_member251760]

{
"error": {
"message": "An unforeseen technical error occurred, for which there is no immediate recovery. If required, consider to open an incident to enable the development team to review and help.",
"code": "InternalServerError",
"status": 500
},

[former_member251760]

Hi Team,

Any idea if the service is down or under maintenance, this error is faced during execution, after the chaincode is deployed and instantiated successfully

Thank you

[Former Member]

Yup, standard behavior - one way to save your sandbox blockchain is to use the API's and save a large JSON file "off chain". And maybe load it back in onto a newly created one. I don't think it would preserve the original genesis block, though and haven't tried this 'restore' routine yet.