deleted snaps on source and now replication fails with "1277, source-dest snap-pair 0 not found"

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

davros123

New Member
Feb 15, 2021
8
1
3
Hi @gea ,
I deleted a range of snaps on my main server. When I went to the backup server and ran the backup jobs - it complained - obvious now that I should not have deleted the most recent snap :(

Apart from scrapping it and starting from scratch - any way to force the replicate jobs to run or do I need to delete it all and start from scratch.

Code:
Log: Last run of Job 1650506760 (newest first)
2023.02.19.12.56.25       &my_log_last line 2328
<- &my_log line 2086
<- &my_end_all line 2055
<- &my_fast_end line 1626
<- &my_newest_snap_pair line 857       error
2023.02.19.12.56.24       &my_log_last line 1622
<- &my_newest_snap_pair line 857
<- &my_remote_delta_replication line 468
<- &my_run line 178       1277, source-dest snap-pair 0 not found;: 0,0
2023.02.19.12.56.21       &my_log_last line 819
<- &my_remote_delta_replication line 468
<- &my_run line 178       start remote incremental replication: read snaps
2023.02.19.12.56.21       &my_log_last line 817
<- &my_remote_delta_replication line 468
<- &my_run line 178       ncwait in remote call: 60
2023.02.19.12.56.21       main line 76       start job-replicate with parameter:
id=1650506760, action=run, par='run_1650506760
 

gea

Well-Known Member
Dec 31, 2010
3,141
1,182
113
DE
Incremental replications need a common snap pair. If you destroy that you need to rerun an initial transfer
- rename the target filesystem ex to filesystem.old (to keep it on problems)
- restart the replication, on success destroy filesystem.old

If the snappair is there and you want to recreate the ongoing incremental replication job
- recreate the job with same settings and old jobid (from snap names)
 
Last edited:
  • Like
Reactions: davros123