Mixing
Google CloudSQL - Point In Time Recovery with Multiple Binary Log Files
This question related to 2nd Gen instances of Google CloudSQL.
When you perform point in time recovery on Google's CloudSQL platform, you must actually clone the instance, then specify the binary log file name and position to roll forward on.
I am unsure how this actually works internally, does it work out which backup needs to be first restored then which binary log files, if any, preclude the one you have selected? Or it does it clone the current state of the instance and roll back to the desired binary log file/position?
What if you have multiple binary log files in your chain since the last backup, i.e. because you have manually flushed logs?
Let's say you have a chain that looks like this in CloudSQL:
Full Backup > mysql-binlog.000001 > mysql-binlog.000002 > mysql-binlog.000003 > Full Backup > mysql-binlog.000004
and you want to restore to a recovery point in mysql-binlog.000003 - how do you do that, or do you not need to specify the precluding binlog files like you would if you were doing a native import with mysqlbinlog utility?
mysql google-cloud-platform google-cloud-sql recovery
edited Nov 22 '18 at 0:13
Ying Li
2,8162936
asked Nov 21 '18 at 11:35
MolenpadMolenpad
18712
add a comment |
This question related to 2nd Gen instances of Google CloudSQL.
When you perform point in time recovery on Google's CloudSQL platform, you must actually clone the instance, then specify the binary log file name and position to roll forward on.
I am unsure how this actually works internally, does it work out which backup needs to be first restored then which binary log files, if any, preclude the one you have selected? Or it does it clone the current state of the instance and roll back to the desired binary log file/position?
What if you have multiple binary log files in your chain since the last backup, i.e. because you have manually flushed logs?
Let's say you have a chain that looks like this in CloudSQL:
Full Backup > mysql-binlog.000001 > mysql-binlog.000002 > mysql-binlog.000003 > Full Backup > mysql-binlog.000004
and you want to restore to a recovery point in mysql-binlog.000003 - how do you do that, or do you not need to specify the precluding binlog files like you would if you were doing a native import with mysqlbinlog utility?
mysql google-cloud-platform google-cloud-sql recovery
edited Nov 22 '18 at 0:13
Ying Li
2,8162936
asked Nov 21 '18 at 11:35
MolenpadMolenpad
18712
add a comment |
This question related to 2nd Gen instances of Google CloudSQL.
When you perform point in time recovery on Google's CloudSQL platform, you must actually clone the instance, then specify the binary log file name and position to roll forward on.
I am unsure how this actually works internally, does it work out which backup needs to be first restored then which binary log files, if any, preclude the one you have selected? Or it does it clone the current state of the instance and roll back to the desired binary log file/position?
What if you have multiple binary log files in your chain since the last backup, i.e. because you have manually flushed logs?
Let's say you have a chain that looks like this in CloudSQL:
Full Backup > mysql-binlog.000001 > mysql-binlog.000002 > mysql-binlog.000003 > Full Backup > mysql-binlog.000004
and you want to restore to a recovery point in mysql-binlog.000003 - how do you do that, or do you not need to specify the precluding binlog files like you would if you were doing a native import with mysqlbinlog utility?
mysql google-cloud-platform google-cloud-sql recovery
edited Nov 22 '18 at 0:13
Ying Li
2,8162936
asked Nov 21 '18 at 11:35
MolenpadMolenpad
18712
This question related to 2nd Gen instances of Google CloudSQL.
When you perform point in time recovery on Google's CloudSQL platform, you must actually clone the instance, then specify the binary log file name and position to roll forward on.
I am unsure how this actually works internally, does it work out which backup needs to be first restored then which binary log files, if any, preclude the one you have selected? Or it does it clone the current state of the instance and roll back to the desired binary log file/position?
What if you have multiple binary log files in your chain since the last backup, i.e. because you have manually flushed logs?
Let's say you have a chain that looks like this in CloudSQL:
Full Backup > mysql-binlog.000001 > mysql-binlog.000002 > mysql-binlog.000003 > Full Backup > mysql-binlog.000004
and you want to restore to a recovery point in mysql-binlog.000003 - how do you do that, or do you not need to specify the precluding binlog files like you would if you were doing a native import with mysqlbinlog utility?
mysql google-cloud-platform google-cloud-sql recovery
mysql google-cloud-platform google-cloud-sql recovery
edited Nov 22 '18 at 0:13
Ying Li
2,8162936
asked Nov 21 '18 at 11:35
MolenpadMolenpad
18712
edited Nov 22 '18 at 0:13
Ying Li
2,8162936
asked Nov 21 '18 at 11:35
MolenpadMolenpad
18712
edited Nov 22 '18 at 0:13
Ying Li
2,8162936
edited Nov 22 '18 at 0:13
Ying Li
2,8162936
edited Nov 22 '18 at 0:13
Ying Li
2,8162936
2,8162936
asked Nov 21 '18 at 11:35
MolenpadMolenpad
18712
asked Nov 21 '18 at 11:35
MolenpadMolenpad
18712
asked Nov 21 '18 at 11:35
MolenpadMolenpad
18712
18712
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You need to restore to the previous backup and then select the binlog that contains the point-in-time for which you want to go back to. You need to find and select that final point in the binlog to restore to. The instructions are here.
To answer your specific question, you only need to select the latest binlog (the one that contains the point-in-time). You basically choose the backup and then the binlog, and then the point in the binlog and the restoring is done by us.
answered Nov 21 '18 at 23:29
Ying LiYing Li
2,8162936
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53411217%2fgoogle-cloudsql-point-in-time-recovery-with-multiple-binary-log-files%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You need to restore to the previous backup and then select the binlog that contains the point-in-time for which you want to go back to. You need to find and select that final point in the binlog to restore to. The instructions are here.
To answer your specific question, you only need to select the latest binlog (the one that contains the point-in-time). You basically choose the backup and then the binlog, and then the point in the binlog and the restoring is done by us.
answered Nov 21 '18 at 23:29
Ying LiYing Li
2,8162936
add a comment |
You need to restore to the previous backup and then select the binlog that contains the point-in-time for which you want to go back to. You need to find and select that final point in the binlog to restore to. The instructions are here.
To answer your specific question, you only need to select the latest binlog (the one that contains the point-in-time). You basically choose the backup and then the binlog, and then the point in the binlog and the restoring is done by us.
answered Nov 21 '18 at 23:29
Ying LiYing Li
2,8162936
add a comment |
You need to restore to the previous backup and then select the binlog that contains the point-in-time for which you want to go back to. You need to find and select that final point in the binlog to restore to. The instructions are here.
To answer your specific question, you only need to select the latest binlog (the one that contains the point-in-time). You basically choose the backup and then the binlog, and then the point in the binlog and the restoring is done by us.
answered Nov 21 '18 at 23:29
Ying LiYing Li
2,8162936
You need to restore to the previous backup and then select the binlog that contains the point-in-time for which you want to go back to. You need to find and select that final point in the binlog to restore to. The instructions are here.
To answer your specific question, you only need to select the latest binlog (the one that contains the point-in-time). You basically choose the backup and then the binlog, and then the point in the binlog and the restoring is done by us.
answered Nov 21 '18 at 23:29
Ying LiYing Li
2,8162936
answered Nov 21 '18 at 23:29
Ying LiYing Li
2,8162936
answered Nov 21 '18 at 23:29
Ying LiYing Li
2,8162936
answered Nov 21 '18 at 23:29
Ying LiYing Li
2,8162936
2,8162936
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53411217%2fgoogle-cloudsql-point-in-time-recovery-with-multiple-binary-log-files%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
