What happens when I delete the first of several AWS EBS snapshots?How to determine actual size of an amazon snapshot?How are Amazon EBS snapshot's sizes calculated?Amazon pricing - transfer between EC2, EBS and S3Amazon EC2 terminology - AMI vs. EBS vs. Snapshot vs. VolumeWhich of snapshots I can safely remove?How to determine actual size of an amazon snapshot?How to schedule automatic (daily) snapshots of AWS EC2 Windows Instance?How to determine total size of Amazon EC2 snapshots?Amazon snapshot issueImproving I/O rates for EBS snapshot backed volumesTrusted Advisor: Amazon EBS Snapshots issue

Polynomial division: Is this trick obvious?

How was the blinking terminal cursor invented?

How long do Aarakocra live?

Roman Numerals Equation 2

301 Redirects what does ([a-z]+)-(.*) and ([0-9]+)-(.*) mean

Why did nobody know who the Lord of this region was?

When the match time is called, does the current turn end immediately?

How can we delete item permanently without storing in Recycle Bin?

How does the Heat Metal spell interact with a follow-up Frostbite spell?

Why is the marginal distribution/marginal probability described as "marginal"?

Why is Drogon so much better in battle than Rhaegal and Viserion?

Non-African Click Languages

How to know the path of a particular software?

What kind of environment would favor hermaphroditism in a sentient species over regular, old sexes?

How to generate a triangular grid from a list of points

How to find the radius of this smaller circle?

Cannot remove door knob -- totally inaccessible!

Would life always name the light from their sun "white"

Why doesn't Iron Man's action affect this person in Endgame?

Why is the A380’s with-reversers stopping distance the same as its no-reversers stopping distance?

Rushed passport - does my reason qualify?

Why use a retrograde orbit?

Why would you put your input amplifier in front of your filtering for and ECG signal?

How to handle professionally if colleagues has referred his relative and asking to take easy while taking interview



What happens when I delete the first of several AWS EBS snapshots?


How to determine actual size of an amazon snapshot?How are Amazon EBS snapshot's sizes calculated?Amazon pricing - transfer between EC2, EBS and S3Amazon EC2 terminology - AMI vs. EBS vs. Snapshot vs. VolumeWhich of snapshots I can safely remove?How to determine actual size of an amazon snapshot?How to schedule automatic (daily) snapshots of AWS EC2 Windows Instance?How to determine total size of Amazon EC2 snapshots?Amazon snapshot issueImproving I/O rates for EBS snapshot backed volumesTrusted Advisor: Amazon EBS Snapshots issue






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








4















On http://aws.amazon.com/ebs/pricing/



it says:
"EBS Snapshots



[...] For the first snapshot of a volume, Amazon EBS saves a full copy of your data to Amazon S3. For each incremental snapshot, only the changed part of your Amazon EBS volume is saved."



I intend to snapshot some of my instances daily and keep snapshots for 7 days after which the snapshots are destroyed.



What happens when, eventually, I destroy the first snapshot? Will the subsequent snapshots be worthless given the first is no longer available?










share|improve this question




























    4















    On http://aws.amazon.com/ebs/pricing/



    it says:
    "EBS Snapshots



    [...] For the first snapshot of a volume, Amazon EBS saves a full copy of your data to Amazon S3. For each incremental snapshot, only the changed part of your Amazon EBS volume is saved."



    I intend to snapshot some of my instances daily and keep snapshots for 7 days after which the snapshots are destroyed.



    What happens when, eventually, I destroy the first snapshot? Will the subsequent snapshots be worthless given the first is no longer available?










    share|improve this question
























      4












      4








      4








      On http://aws.amazon.com/ebs/pricing/



      it says:
      "EBS Snapshots



      [...] For the first snapshot of a volume, Amazon EBS saves a full copy of your data to Amazon S3. For each incremental snapshot, only the changed part of your Amazon EBS volume is saved."



      I intend to snapshot some of my instances daily and keep snapshots for 7 days after which the snapshots are destroyed.



      What happens when, eventually, I destroy the first snapshot? Will the subsequent snapshots be worthless given the first is no longer available?










      share|improve this question














      On http://aws.amazon.com/ebs/pricing/



      it says:
      "EBS Snapshots



      [...] For the first snapshot of a volume, Amazon EBS saves a full copy of your data to Amazon S3. For each incremental snapshot, only the changed part of your Amazon EBS volume is saved."



      I intend to snapshot some of my instances daily and keep snapshots for 7 days after which the snapshots are destroyed.



      What happens when, eventually, I destroy the first snapshot? Will the subsequent snapshots be worthless given the first is no longer available?







      amazon-ec2 amazon-ebs






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 18 '14 at 14:39









      JepperJepper

      227312




      227312




















          1 Answer
          1






          active

          oldest

          votes


















          6














          When you delete any EBS snapshot, if there's a later snapshot for the same volume, every block in the first snapshot that wasn't included in the later snapshot (because it didn't change) is logically rolled forward (in a sense) into the later snapshot, so the later snapshot is still perfectly valid when any or all earlier snapshots are deleted.



          Conceptually, you can also think of the snapshot process consisting of two separate pieces: the compressed,¹ backed-up data that is stored in chunks in Amazon S3² during the snapshot process, and then the snapshot itself, which is only a container of pointers to those chunks of raw data. Every snapshot references a particular archived data chunk for each block of the volume, and those chunks are fetched and reassembled when a snapshot is restored. When a snapshot is deleted, any archived data chunk that is no longer referenced by any other snapshot is purged, but any chunk referenced by any other snapshot... isn't.



          So you can freely delete any snapshot in a series, without impacting the validity of earlier or later snapshots. Note, though, that purging snapshots of volumes that don't change much will also not save you very much in monthly snapshot storage fees, because you already are paying very little for them, since they contain very little unique data.



          See also:



          https://stackoverflow.com/questions/19501192/confusion-over-ebs-snapshots-in-amazon/19503615#19503615



          How to determine actual size of an amazon snapshot?




          ¹ compressed ...well, maybe. The internal workings of EBS snapshots have always been a black box but when this answer was originally written in 2014, the conventional wisdom held that EBS compressed the backup chunks before storing them in S3. This may have been incorrect all along or may no longer be the case because it subsequently changed -- perhaps due to the fact that compressing already-encrypted data is much less efficient than compressing unencrypted data and EBS volumes are so easy to create with transparent encryption that the prevalence of encrypted volumes made the compression unproductive -- but there does not appear to be any official, documented source currently indicating that the backup data is actually compressed. The actual charge for snapshot storage is almost always substantially less than the logical size of the snapshot, so this particular detail is not necessarily important, but I've striken the word from the original answer, in the interest of accuracy.



          ² in Amazon S3 is where snapshot data is stored, but the buckets are owned and controlled by the EC2/EBS service, so the buckets are not visible in the console and the raw snapshot data isn't accessible to the end-user.






          share|improve this answer

























          • So the Amazon host, does a LVM (?) snapshot of lets say a 10GB volume. The entire volume (or non-zero blocks at least) are copied to S3. But so far it's not costing us anything..? Later we take another snapshot, where 100MB has changed. We are now charged for 100MB of storage?

            – Jepper
            Aug 21 '14 at 20:49











          • Not LVM, it's a raw block device snapshot, with no awareness of the actual filesystem. The first snapshot stores the entire volume, subsequent snapshots store the changes. You pay storage for both. Deleting either of the two will only reduce your cost by the cost of storing the changed blocks.

            – Michael - sqlbot
            Aug 21 '14 at 21:29











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "2"
          ;
          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
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f622211%2fwhat-happens-when-i-delete-the-first-of-several-aws-ebs-snapshots%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









          6














          When you delete any EBS snapshot, if there's a later snapshot for the same volume, every block in the first snapshot that wasn't included in the later snapshot (because it didn't change) is logically rolled forward (in a sense) into the later snapshot, so the later snapshot is still perfectly valid when any or all earlier snapshots are deleted.



          Conceptually, you can also think of the snapshot process consisting of two separate pieces: the compressed,¹ backed-up data that is stored in chunks in Amazon S3² during the snapshot process, and then the snapshot itself, which is only a container of pointers to those chunks of raw data. Every snapshot references a particular archived data chunk for each block of the volume, and those chunks are fetched and reassembled when a snapshot is restored. When a snapshot is deleted, any archived data chunk that is no longer referenced by any other snapshot is purged, but any chunk referenced by any other snapshot... isn't.



          So you can freely delete any snapshot in a series, without impacting the validity of earlier or later snapshots. Note, though, that purging snapshots of volumes that don't change much will also not save you very much in monthly snapshot storage fees, because you already are paying very little for them, since they contain very little unique data.



          See also:



          https://stackoverflow.com/questions/19501192/confusion-over-ebs-snapshots-in-amazon/19503615#19503615



          How to determine actual size of an amazon snapshot?




          ¹ compressed ...well, maybe. The internal workings of EBS snapshots have always been a black box but when this answer was originally written in 2014, the conventional wisdom held that EBS compressed the backup chunks before storing them in S3. This may have been incorrect all along or may no longer be the case because it subsequently changed -- perhaps due to the fact that compressing already-encrypted data is much less efficient than compressing unencrypted data and EBS volumes are so easy to create with transparent encryption that the prevalence of encrypted volumes made the compression unproductive -- but there does not appear to be any official, documented source currently indicating that the backup data is actually compressed. The actual charge for snapshot storage is almost always substantially less than the logical size of the snapshot, so this particular detail is not necessarily important, but I've striken the word from the original answer, in the interest of accuracy.



          ² in Amazon S3 is where snapshot data is stored, but the buckets are owned and controlled by the EC2/EBS service, so the buckets are not visible in the console and the raw snapshot data isn't accessible to the end-user.






          share|improve this answer

























          • So the Amazon host, does a LVM (?) snapshot of lets say a 10GB volume. The entire volume (or non-zero blocks at least) are copied to S3. But so far it's not costing us anything..? Later we take another snapshot, where 100MB has changed. We are now charged for 100MB of storage?

            – Jepper
            Aug 21 '14 at 20:49











          • Not LVM, it's a raw block device snapshot, with no awareness of the actual filesystem. The first snapshot stores the entire volume, subsequent snapshots store the changes. You pay storage for both. Deleting either of the two will only reduce your cost by the cost of storing the changed blocks.

            – Michael - sqlbot
            Aug 21 '14 at 21:29















          6














          When you delete any EBS snapshot, if there's a later snapshot for the same volume, every block in the first snapshot that wasn't included in the later snapshot (because it didn't change) is logically rolled forward (in a sense) into the later snapshot, so the later snapshot is still perfectly valid when any or all earlier snapshots are deleted.



          Conceptually, you can also think of the snapshot process consisting of two separate pieces: the compressed,¹ backed-up data that is stored in chunks in Amazon S3² during the snapshot process, and then the snapshot itself, which is only a container of pointers to those chunks of raw data. Every snapshot references a particular archived data chunk for each block of the volume, and those chunks are fetched and reassembled when a snapshot is restored. When a snapshot is deleted, any archived data chunk that is no longer referenced by any other snapshot is purged, but any chunk referenced by any other snapshot... isn't.



          So you can freely delete any snapshot in a series, without impacting the validity of earlier or later snapshots. Note, though, that purging snapshots of volumes that don't change much will also not save you very much in monthly snapshot storage fees, because you already are paying very little for them, since they contain very little unique data.



          See also:



          https://stackoverflow.com/questions/19501192/confusion-over-ebs-snapshots-in-amazon/19503615#19503615



          How to determine actual size of an amazon snapshot?




          ¹ compressed ...well, maybe. The internal workings of EBS snapshots have always been a black box but when this answer was originally written in 2014, the conventional wisdom held that EBS compressed the backup chunks before storing them in S3. This may have been incorrect all along or may no longer be the case because it subsequently changed -- perhaps due to the fact that compressing already-encrypted data is much less efficient than compressing unencrypted data and EBS volumes are so easy to create with transparent encryption that the prevalence of encrypted volumes made the compression unproductive -- but there does not appear to be any official, documented source currently indicating that the backup data is actually compressed. The actual charge for snapshot storage is almost always substantially less than the logical size of the snapshot, so this particular detail is not necessarily important, but I've striken the word from the original answer, in the interest of accuracy.



          ² in Amazon S3 is where snapshot data is stored, but the buckets are owned and controlled by the EC2/EBS service, so the buckets are not visible in the console and the raw snapshot data isn't accessible to the end-user.






          share|improve this answer

























          • So the Amazon host, does a LVM (?) snapshot of lets say a 10GB volume. The entire volume (or non-zero blocks at least) are copied to S3. But so far it's not costing us anything..? Later we take another snapshot, where 100MB has changed. We are now charged for 100MB of storage?

            – Jepper
            Aug 21 '14 at 20:49











          • Not LVM, it's a raw block device snapshot, with no awareness of the actual filesystem. The first snapshot stores the entire volume, subsequent snapshots store the changes. You pay storage for both. Deleting either of the two will only reduce your cost by the cost of storing the changed blocks.

            – Michael - sqlbot
            Aug 21 '14 at 21:29













          6












          6








          6







          When you delete any EBS snapshot, if there's a later snapshot for the same volume, every block in the first snapshot that wasn't included in the later snapshot (because it didn't change) is logically rolled forward (in a sense) into the later snapshot, so the later snapshot is still perfectly valid when any or all earlier snapshots are deleted.



          Conceptually, you can also think of the snapshot process consisting of two separate pieces: the compressed,¹ backed-up data that is stored in chunks in Amazon S3² during the snapshot process, and then the snapshot itself, which is only a container of pointers to those chunks of raw data. Every snapshot references a particular archived data chunk for each block of the volume, and those chunks are fetched and reassembled when a snapshot is restored. When a snapshot is deleted, any archived data chunk that is no longer referenced by any other snapshot is purged, but any chunk referenced by any other snapshot... isn't.



          So you can freely delete any snapshot in a series, without impacting the validity of earlier or later snapshots. Note, though, that purging snapshots of volumes that don't change much will also not save you very much in monthly snapshot storage fees, because you already are paying very little for them, since they contain very little unique data.



          See also:



          https://stackoverflow.com/questions/19501192/confusion-over-ebs-snapshots-in-amazon/19503615#19503615



          How to determine actual size of an amazon snapshot?




          ¹ compressed ...well, maybe. The internal workings of EBS snapshots have always been a black box but when this answer was originally written in 2014, the conventional wisdom held that EBS compressed the backup chunks before storing them in S3. This may have been incorrect all along or may no longer be the case because it subsequently changed -- perhaps due to the fact that compressing already-encrypted data is much less efficient than compressing unencrypted data and EBS volumes are so easy to create with transparent encryption that the prevalence of encrypted volumes made the compression unproductive -- but there does not appear to be any official, documented source currently indicating that the backup data is actually compressed. The actual charge for snapshot storage is almost always substantially less than the logical size of the snapshot, so this particular detail is not necessarily important, but I've striken the word from the original answer, in the interest of accuracy.



          ² in Amazon S3 is where snapshot data is stored, but the buckets are owned and controlled by the EC2/EBS service, so the buckets are not visible in the console and the raw snapshot data isn't accessible to the end-user.






          share|improve this answer















          When you delete any EBS snapshot, if there's a later snapshot for the same volume, every block in the first snapshot that wasn't included in the later snapshot (because it didn't change) is logically rolled forward (in a sense) into the later snapshot, so the later snapshot is still perfectly valid when any or all earlier snapshots are deleted.



          Conceptually, you can also think of the snapshot process consisting of two separate pieces: the compressed,¹ backed-up data that is stored in chunks in Amazon S3² during the snapshot process, and then the snapshot itself, which is only a container of pointers to those chunks of raw data. Every snapshot references a particular archived data chunk for each block of the volume, and those chunks are fetched and reassembled when a snapshot is restored. When a snapshot is deleted, any archived data chunk that is no longer referenced by any other snapshot is purged, but any chunk referenced by any other snapshot... isn't.



          So you can freely delete any snapshot in a series, without impacting the validity of earlier or later snapshots. Note, though, that purging snapshots of volumes that don't change much will also not save you very much in monthly snapshot storage fees, because you already are paying very little for them, since they contain very little unique data.



          See also:



          https://stackoverflow.com/questions/19501192/confusion-over-ebs-snapshots-in-amazon/19503615#19503615



          How to determine actual size of an amazon snapshot?




          ¹ compressed ...well, maybe. The internal workings of EBS snapshots have always been a black box but when this answer was originally written in 2014, the conventional wisdom held that EBS compressed the backup chunks before storing them in S3. This may have been incorrect all along or may no longer be the case because it subsequently changed -- perhaps due to the fact that compressing already-encrypted data is much less efficient than compressing unencrypted data and EBS volumes are so easy to create with transparent encryption that the prevalence of encrypted volumes made the compression unproductive -- but there does not appear to be any official, documented source currently indicating that the backup data is actually compressed. The actual charge for snapshot storage is almost always substantially less than the logical size of the snapshot, so this particular detail is not necessarily important, but I've striken the word from the original answer, in the interest of accuracy.



          ² in Amazon S3 is where snapshot data is stored, but the buckets are owned and controlled by the EC2/EBS service, so the buckets are not visible in the console and the raw snapshot data isn't accessible to the end-user.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited May 5 at 14:56

























          answered Aug 18 '14 at 22:26









          Michael - sqlbotMichael - sqlbot

          16.5k3563




          16.5k3563












          • So the Amazon host, does a LVM (?) snapshot of lets say a 10GB volume. The entire volume (or non-zero blocks at least) are copied to S3. But so far it's not costing us anything..? Later we take another snapshot, where 100MB has changed. We are now charged for 100MB of storage?

            – Jepper
            Aug 21 '14 at 20:49











          • Not LVM, it's a raw block device snapshot, with no awareness of the actual filesystem. The first snapshot stores the entire volume, subsequent snapshots store the changes. You pay storage for both. Deleting either of the two will only reduce your cost by the cost of storing the changed blocks.

            – Michael - sqlbot
            Aug 21 '14 at 21:29

















          • So the Amazon host, does a LVM (?) snapshot of lets say a 10GB volume. The entire volume (or non-zero blocks at least) are copied to S3. But so far it's not costing us anything..? Later we take another snapshot, where 100MB has changed. We are now charged for 100MB of storage?

            – Jepper
            Aug 21 '14 at 20:49











          • Not LVM, it's a raw block device snapshot, with no awareness of the actual filesystem. The first snapshot stores the entire volume, subsequent snapshots store the changes. You pay storage for both. Deleting either of the two will only reduce your cost by the cost of storing the changed blocks.

            – Michael - sqlbot
            Aug 21 '14 at 21:29
















          So the Amazon host, does a LVM (?) snapshot of lets say a 10GB volume. The entire volume (or non-zero blocks at least) are copied to S3. But so far it's not costing us anything..? Later we take another snapshot, where 100MB has changed. We are now charged for 100MB of storage?

          – Jepper
          Aug 21 '14 at 20:49





          So the Amazon host, does a LVM (?) snapshot of lets say a 10GB volume. The entire volume (or non-zero blocks at least) are copied to S3. But so far it's not costing us anything..? Later we take another snapshot, where 100MB has changed. We are now charged for 100MB of storage?

          – Jepper
          Aug 21 '14 at 20:49













          Not LVM, it's a raw block device snapshot, with no awareness of the actual filesystem. The first snapshot stores the entire volume, subsequent snapshots store the changes. You pay storage for both. Deleting either of the two will only reduce your cost by the cost of storing the changed blocks.

          – Michael - sqlbot
          Aug 21 '14 at 21:29





          Not LVM, it's a raw block device snapshot, with no awareness of the actual filesystem. The first snapshot stores the entire volume, subsequent snapshots store the changes. You pay storage for both. Deleting either of the two will only reduce your cost by the cost of storing the changed blocks.

          – Michael - sqlbot
          Aug 21 '14 at 21:29

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Server Fault!


          • 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.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f622211%2fwhat-happens-when-i-delete-the-first-of-several-aws-ebs-snapshots%23new-answer', 'question_page');

          );

          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







          Popular posts from this blog

          Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

          Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

          Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020