Jump to content
Covecube Inc.
  • 0
Spider99

Other files and Sys Vol Info

Question

If you have a large amount of "other" files taking up space on your pool drive and would like to reduce the amount of "wasted" space then...

 

Warning doing this could stuff up you pc so go carefully and if it goes to pot its not my fault :)

 

Your friend here is the powershell cmdlet "vssadmin"

 

if you run the command via an elevated powershell window

 

vssadmin list shadowstorage

 

it will list your vss stores etc

 

and then run

 

vssadmin resize shadowstorage /on=[drive letter]: /For=[drive letter]: /MaxSize=[maximum size]

 

See http://woshub.com/how-to-clean-up-system-volume-information-folder/

 

for more details

 

got rid of 70GB+ of unneeded vss data for me :)

 

Enjoy

Share this post


Link to post
Share on other sites

8 answers to this question

Recommended Posts

  • 0

I just use the UI to do this. 

 

On client OS's (Windows 7, 8, 10), run "control sysdm.cpl" and open the "System Protection" tab.

From there, you can toggle the state, and delete the shadow copies.

 

on Server OS's, run "fsmgmt.msc" and find the "Configure Shadow Copies" option in the menus. 

Share this post


Link to post
Share on other sites
  • 0

yes should have said 2012 r2 - as yes you do have access in window 7 10 etc - but its missing from 2012 r2 - hence why i went looking

 

the fsmgmt.msc is a new one on me - actually it works in win 10 as well :)

Share this post


Link to post
Share on other sites
  • 0

In WHS2011, I'm pretty sure I can get there through the properties of the volume?

 

I turned them all off ages ago.

 

What I would like to be able to do easily is delete all the old files in the SIV folder but there are quite a few where I simply can not get access to (unless perhapsd I more the disks to another machine temporarly). I can not even set myself (or anyone) as Owner.

Share this post


Link to post
Share on other sites
  • 0

i was able to get ownership but it would appear to delete the files in svi but they would just come back - the vssadmin does the trick though just do it from an elevated ps prompt

Share this post


Link to post
Share on other sites
  • 0

I just use the UI to do this. 

 

On client OS's (Windows 7, 8, 10), run "control sysdm.cpl" and open the "System Protection" tab.

From there, you can toggle the state, and delete the shadow copies.

 

on Server OS's, run "fsmgmt.msc" and find the "Configure Shadow Copies" option in the menus. 

Another option: On the server, i right click on any drive and i have a choice called "Configure shadow copies..." . From there i can change the shadow size.

 

On a different matter, I installed server 2016 and reinstalled drivepool and moved my drives (not physically as this is the same server box as where 2012 r2 essentials was) to the new server. I was able to redirect the essentials dashboard server folders to the drivepool drive. Setup backups and three computers are backing up fine. However after I added a standard user account to access the server, though it created a user folder with that name, from the client computer launchpad, i am unable to access the shared folders from the client computer. I get a "Windows cannot access \\xxxxserver\shared folders Check the spelling of the name.....Error code 0x80070035". When i looked up the network pathway in the server for the shared folder it is as follows: " xxxserver\users2\xxxname" (xxxname is the name i created for the user). The reason it is users2 is probably because the drive pool drives already had a user folder with subfolders from my previous server 2012 r2 installation i suppose. So my question is how do i force lauchpad to go to the users2\xxxname account when clicking on lauchpad? Or is this issue because i connected the client pc as a workgroup (using the skip domain function)? Thanks

Share this post


Link to post
Share on other sites
  • 0

@asdaHP:

 

It looks like the Shared Folders issue is a common one on 2016.... which is odd.

 

http://homeservershow.com/forums/index.php?/topic/11755-windows-server-2016-essentials/page-3&do=findComment&comment=123872

 

You can always just use "\\SERVERNAME\ShareName" instead.

The reason the "Shared Folder" share was created was to hide all of the domain stuff (NETLOGON, SYSVOL, REMOTEINSTALL, etc), by using "DFS Namespace" feature of Windows Server. 

 

Administrators seem to not have an issue, but non-admins have this issue. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...