Postgres RDS System Snapshot Restoration Inconsistency

0

I have a Postgres RDS instance that is producing very strange behavior regarding system snapshots. Basically, when I manually create a snapshot and then restore it I am always able to connect to it from an ec2 instance within the same VPC once the restoration process is complete.

However, about 95% of the time lately when I try to restore a system (automatic) snapshot, I cannot connect to it. Even if I use the EXACT same settings (VPC, security groups, subnet, etc) as another existing instance, the connection just times out. I just did one last test before this post to ensure again this weirdness was happening and surprisingly I could connect to the restored system snapshot that was made earlier today. Then again with identical settings, I tried to restore and connect to a system snapshot from the previous day it timed out.

Does anyone have any idea on what is going on here?

1개 답변
0

Hard to say, one thing to check is that your client can reach the database listener port. That will tell you if you have network access to the database.

https://code.google.com/archive/p/paping/downloads

AWS
중재자
philaws
답변함 2달 전
profile picture
전문가
검토됨 한 달 전
  • I tried the paping tool and it basically showed me exactly what I was expecting. I just did the same test again.

    Spun up 2 instances from the most recent snapshot and the one before. I get the exact same results. First one works, 2nd timed out. Which after about 12 times trying this, does show a new pattern it seems! It looks like every other snapshot exhibits this behavior. I suppose I should look into what is happening that time of day CRON job wise or whatever but I'm open to any ideas!

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠