How does the Product Backlog differ from the Sprint Backlog in Scrum?

I'm in dilemma after coming across various facts stating that Product Backlog and Sprint Backlog in Scrum relatively share the same properties. Is that true?

The Sprint Backlog is a subset of items that are in the Product Backlog.  The items in the Sprint Backlog are the Product Backlog items that the Developers have selected to work on during the Sprint.  Thus those items are still present in the Product Backlog until they are delivered as part of usable, valuable increments.

And DevOps and Scrum can come together? And What is major difference between them?

Biggest difference is that Scrum is a framework where DevOps is a methodology.  As such, the DevOps methodology can be used within the Scrum framework.  The Scrum framework encourages empirical decision making with some built in artifacts, responsibilities, and events. 

Those are fairly simplified answers. If you have more specific questions, you may want to ask them so that we can help clarify. 

I'm in dilemma after coming across various facts stating that Product Backlog and Sprint Backlog in Scrum relatively share the same properties. Is that true?

Both are ordered lists, and each represents an emergent forecast of work for meeting a commitment. Are those the properties you are referring to?

And DevOps and Scrum can come together? And What is major difference between them?

Yes, organizations can utterly fail to understand both, and the deep cultural change that is required to benefit from either. DevOps is the more likely of the two to be confused with automation.

Product Backlog list of items by Product Owner which might be completed by the Scrum Team within one Sprint where as Sprint Backlog is Spring Goal, Product Backlog items selected and actionable plan for delivering the Increment. Sprint Backlog is a plan by and for the Developers.