Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.comp.os.windows-11    |    Steaming pile of horseshit Windows 11    |    4,852 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 4,809 of 4,852    |
|    Maria Sophia to Paul    |
|    Re: PSA: Windows shadow storage can sile    |
|    23 Feb 26 00:25:08    |
   
   XPost: alt.comp.os.windows-10, alt.comp.microsoft.windows   
   From: mariasophia@comprehension.com   
      
   Paul wrote:   
   > vssadmin list shadowstorage   
   > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool   
   > (C) Copyright 2001-2013 Microsoft Corp.   
   >   
   > Shadow Copy Storage association   
   > For volume: (C:)\\?\Volume{0bd6166a-0836-4041-891c-792df2c72abd}\   
   > Shadow Copy Storage volume: (C:)\\?\Volume{0bd6166a-0836-40   
   1-891c-792df2c72abd}\   
   > Used Shadow Copy Storage space: 0 bytes (0%)   
   > Allocated Shadow Copy Storage space: 0 bytes (0%)   
   > Maximum Shadow Copy Storage space: 2.37 GB (2%) <===   
   >   
   > Shadow Copy Storage association   
   > For volume: (H:)\\?\Volume{bd4d69bc-6fbb-4f12-b804-f32c6b9e828c}\   
   > Shadow Copy Storage volume: (H:)\\?\Volume{bd4d69bc-6fbb-4f   
   2-b804-f32c6b9e828c}\   
   > Used Shadow Copy Storage space: 29.8 MB (0%)   
   > Allocated Shadow Copy Storage space: 320 MB (0%)   
   > Maximum Shadow Copy Storage space: 6.45 GB (5%) <===   
   >   
   > I can see no contribution from File History to VSS, one way or another.   
      
   Hi Paul,   
      
   Wow. That was refreshing! It's exciting to learn from a Usenet response!   
      
   Thanks for posting your numbers as we can all work together as a well-honed   
   team given each of our setups have been modified over many years.   
      
   What you're showing above is actually the "normal" case, AFAICT, and it   
   helps confirm the point of the PSA for a properly set up Windows box.   
      
   Your C: drive has a maximum shadow storage size of 2.37 GB (about 2%).   
   Your H: drive has a maximum of 6.45 GB (about 5%).   
      
   Since VSS always reports the maximum shadow storage size as a percentage of   
   the drive it's associated with, not a percentage of used space, free space,   
   or anything else, your "2.37 GB (2%)" means, I think, that your C: drive is   
   roughly 118 GB in total size and your "6.45 GB (5%)" on H: means that H:   
   drive is roughly 129 GB in total size (AFAICT).   
      
   Both of those sets of numbers appear to me to be sane, bounded values.   
   They likely won't run away and consume either of your entire disks.   
      
   In my case, the "Maximum Shadow Copy Storage space" was set to 100% of the   
   drive. I don't know why. I don't know how. I didn't even know to look.   
      
   Now I do know how to look, which is the main point of this helpful PSA:   
    C:\> vssadmin list shadowstorage /for=C:   
      
   The output doesn't mean VSS was using what it reports, but only that   
   Windows was allowed to reserve that much if it wanted to. Once the disk got   
   tight, VSS and NTFS metadata allocation pushed right up against that limit   
   and the last few GB vanished instantly, while I was editing a text file.   
      
   Your output on a better-set-up PC shows the opposite situation than mine.   
   Your max size is capped, so even if VSS wanted more space, it can't exceed   
   those limits on your machine so you won't likely see the same behavior.   
      
   Your additional helpful note about File History is apropos for this PSA.]   
      
   Looking it up, apparently Windows File History uses its own storage   
   mechanism & hence, it doesn't contribute to VSS usage. The two systems are   
   separate. I didn't realize it existed until you pointed it out. Thanks.   
    Win+R > FileHistory   
    Reported:   
    a. No file history was found   
    b. File History is currently turned off.   
    c. Configure File History settings'   
    d. Control Panel\All Control Panel Items\File History   
      
   It's probably important to note that it seems, after looking it up, that   
   File History does not use VSS shadow storage as it uses a normal folder   
   structure on whatever drive we selected as the File History target.   
   
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca