Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
add time in output #529
Open
add time in output #529
Comments
|
@ChristophHoyer that's a great idea! I'm not sure we have bandwidth right now to add this, but we would happily review a PR if you submitted one! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
it might be useful to see, how long a restore takes.
Therefore it would be helpful, if the ghe-restore command could print out a timestamp at the beginning and the end of the run.
Something like:
Checking for leaked keys in the backup snapshot that is being restored ...
Connect github.superserver.com:122 OK (v2.18.7)
WARNING: All data on GitHub Enterprise appliance github.superserver.com (v2.18.7)
will be overwritten with data from snapshot 20191203T011002.
Please verify that this is the correct restore host before continuing.
Type 'yes' to continue: yes
Starting restore of github.superserver.com:122 with backup-utils v2.18.0 from snapshot 20191203T011002
Start time: 2019-12-03 11:30
Stopping cron and github-timerd ...
Restoring UUID ...
Restoring MySQL database ...
Restoring Redis database ...
Restoring Git repositories ...
Restoring Gists ...
Warning: Gist backup missing. Skipping ...
Restoring GitHub Pages ...
Restoring SSH authorized keys ...
Restoring storage data ...
Restoring custom Git hooks ...
Restoring Elasticsearch indices ...
Restoring Audit logs ...
Restoring hookshot logs ...
Configuring appliance ...
Starting cron ...
Restoring SSH host keys ...
End time: 2019-12-03 12:00
Runtime: 00:30h
Restore of github.superserver.com:122 from snapshot 20191203T011002 finished.