I am not aware of an existing solution, but I would suggest the following solution.
For a true backup, you probably want to be outside of GCS. You can create a bucket in Amazon's S3 service, which is very similar to GCS. First, you save an image to a bucket in GCS. Then, you save the same file to a bucket in S3 using the same key/object name that you used for GCS.
In your code, you can add simple logic to serve a file from GCS first, but if it fails, to serve it from S3. The only difference is a path to the file.
If you prefer to stay within GCS, you can have two buckets - production and backup, and set up a cron job to periodically sync them. Again, you can use the same object name as object names have to be unique within a bucket. If a file has a unique object name in production bucket, it is guaranteed to be unique in backup bucket as well.