-
Notifications
You must be signed in to change notification settings - Fork 308
run Gittip 86 #1937
Comments
32 accounts reviewed |
Droplet spun up. |
The |
The versions of |
Okay! So my options are to upgrade my local Postgres, or run the backup manually for today. |
Running the backup manually is inconvenient, because I can't ... specify ... a ... URI. ;-) |
Droplet updated, in the mean time. :-) |
I could also skip the backup for this week, since @zwn assures me that we're backing up somewhere, using Heroku's backup system. I don't like being backed into a corner like that, though. |
I'm building Postgres. |
I'm getting segfaults from Postgres. |
Okay! Back on track ... |
Backup taken. |
$ heroku pgbackups ID Backup Time Status Size Database ---- ------------------- ------------------------------ ------ ----------------------------------------- b001 2013/06/15 04:41.26 Finished @ 2013/06/15 04:41.33 10.8MB HEROKU_POSTGRESQL_ROSE b002 2013/07/17 19:17.19 Finished @ 2013/07/17 19:17.27 13.2MB HEROKU_POSTGRESQL_ROSE b003 2013/10/16 20:11.24 Finished @ 2013/10/16 20:11.47 18.9MB HEROKU_POSTGRESQL_ROSE b004 2013/10/25 12:06.59 Finished @ 2013/10/25 12:07.16 19.3MB HEROKU_POSTGRESQL_ROSE b005 2013/11/22 19:18.08 Finished @ 2013/11/22 19:18.17 21.1MB HEROKU_POSTGRESQL_ROSE_URL (DATABASE_URL) a022 2013/12/16 18:35.39 Finished @ 2013/12/16 18:35.49 22.4MB DATABASE_URL a029 2013/12/23 15:54.26 Finished @ 2013/12/23 15:54.40 22.8MB DATABASE_URL a036 2013/12/30 20:52.49 Finished @ 2013/12/30 20:53.06 23.2MB DATABASE_URL a043 2014/01/06 15:58.22 Finished @ 2014/01/06 15:58.35 23.5MB DATABASE_URL b051 2014/01/09 15:34.49 Finished @ 2014/01/09 15:35.08 23.7MB HEROKU_POSTGRESQL_ROSE_URL (DATABASE_URL) a050 2014/01/13 18:54.35 Finished @ 2014/01/13 18:54.53 24.0MB DATABASE_URL a054 2014/01/17 17:38.37 Finished @ 2014/01/17 17:38.48 24.3MB DATABASE_URL a055 2014/01/18 19:12.16 Finished @ 2014/01/18 19:12.29 24.4MB DATABASE_URL b062 2014/01/19 15:30.55 Finished @ 2014/01/19 15:31.05 24.4MB HEROKU_POSTGRESQL_ROSE_URL (DATABASE_URL) a056 2014/01/19 17:11.19 Finished @ 2014/01/19 17:11.31 24.4MB DATABASE_URL a057 2014/01/20 04:28.09 Finished @ 2014/01/20 04:28.22 24.4MB DATABASE_URL a058 2014/01/21 04:05.58 Finished @ 2014/01/21 04:06.14 24.4MB DATABASE_URL a059 2014/01/22 03:59.00 Finished @ 2014/01/22 03:59.19 24.5MB DATABASE_URL a060 2014/01/23 05:03.01 Finished @ 2014/01/23 05:03.10 24.5MB DATABASE_URL Are these them? |
Backup verified. |
Documentation: https://devcenter.heroku.com/articles/pgbackups#list-backups |
@clone1018 Those are the ones that Heroku does for us. I've been keeping a weekly backup on my laptop. I'm not ready to give up that practice yet. I think it's a good idea to have a backup somewhere we control better than the Herokuzon cloud. |
No, that's fine. I was responding to "I could also skip the backup for this week, since @zwn assures me that we're backing up somewhere" |
Script started. |
Script ran for {age} (2:15:36.668592). |
Log downloaded. |
Droplet destroyed. |
Tweet tweeted on Twitter. |
MassPay done and posted back for 24 users. |
Escrow moved from Balanced to New Alliance and from New Alliance to PayPal. |
Sorry for that 9.3 dependency. The ability to supply the url on the command line seemed so essential and obvious that I didn't check the version. The subconscious thought being it must have been there 'forever'. As for the backups, they are taken automatically by heroku and stored somewhere. For more info see #1646. |
@zwn No worries. The absence of that feature in 9.1 was the reason for the configure-pg-env.sh script in the first place. Glad we're over that hump now. :-) |
85
The text was updated successfully, but these errors were encountered: