2015. május 20., szerda

Querying Exchange quota limits in Powershell

Get-mailbox | where {$_.UseDatabaseQuotaDefaults -ne $true} 

Get-MailboxDatabase | Get-MailboxStatistics | Where-Object {$_.StorageLimitStatus -match 'BelowLimit|IssueWarning|ProhibitSend|MailboxDisabled'} 

Get-mailbox | get-mailboxstatistics | sort-object totalitemsize –descending | ft displayname,totalitemsize

Get-PublicFolder -Recurse -ResultSize Unlimited  | Get-PublicFolderStatistics -Server exchange | Select FolderPath, ItemCount, TotalAssociatedItemSize, TotalDeletedItemSize, TotalItemSize | fl

2015. május 4., hétfő

Windows 2008 Server R2 hangs on "Preparing to configure Windows. Do not turn off your computer"

Last night I started installing updates on a Windows 2008 R2 box but when I had my dinner and returned to my computer I got pissed off seeing the server stalled at
and I could not RDP into the OS. I spent ca. half an hour waiting for something to happen, then, made a short google search. It turned out that if I connected to this OS via the services.msc console of an other server being in the same domain network I could see that WINDOWS MODULES INSTALLER Service was stuck in Stopping state.
Using the built-in Sysinternals utils:
taskkill /S hostname /IM trustedinstaller.exe
or
sc \\computername queryex TrustedInstaller
taskkill /s computername /pid /f
...I could have been able to terminate that task. According to some internet records if I had done so, my server would have restarted without a hitch. Luckily enough, after entertaining me for more than one hour (-meanwhile actualy doing nothing-) this damn server finally restarted by itself! After the reboot it installed the updates and got ready in less than 5 minutes.
So, in case you are here because you are in the same business as I was, now you'd better have some coffee and wait patiently instead of roughly interfere.

2015. április 3., péntek

Dell OMSA services installation trouble on Debian 7 (wheezy how to)

root@omsa:~# echo 'deb http://linux.dell.com/repo/community/deb/latest /' > /etc/apt/sources.list.d/linux.dell.com.sources.list
root@omsa:~# apt-get update
Hit http://ftp.hu.debian.org wheezy Release.gpg
Hit http://ftp.hu.debian.org wheezy-updates Release.gpg
Hit http://ftp.hu.debian.org wheezy Release
Hit http://ftp.hu.debian.org wheezy-updates Release
Hit http://ftp.hu.debian.org wheezy/main Sources
Hit http://ftp.hu.debian.org wheezy/main i386 Packages
Hit http://ftp.hu.debian.org wheezy/main Translation-en
Hit http://ftp.hu.debian.org wheezy-updates/main Sources
Hit http://ftp.hu.debian.org wheezy-updates/main i386 Packages/DiffIndex
Hit http://ftp.hu.debian.org wheezy-updates/main Translation-en/DiffIndex
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main Sources
Hit http://security.debian.org wheezy/updates/main i386 Packages
Hit http://security.debian.org wheezy/updates/main Translation-en
Get:1 http://linux.dell.com  Release.gpg [827 B]
Get:2 http://linux.dell.com  Release [1,392 B]
Ign http://linux.dell.com  Release
Get:3 http://linux.dell.com  Packages [12.2 kB]
Ign http://linux.dell.com  Translation-en_US
Ign http://linux.dell.com  Translation-en
Fetched 14.4 kB in 4s (3,136 B/s)
Reading package lists... Done
W: GPG error: http://linux.dell.com  Release: The following signatures couldn't                                                                                                                    be verified because the public key is not available: NO_PUBKEY 1285491434D8786F
root@omsa:~# gpg --keyserver pool.sks-keyservers.net --recv-key 1285491434D8786F                                                                                                                
gpg: directory `/root/.gnupg' created
gpg: new configuration file `/root/.gnupg/gpg.conf' created
gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/root/.gnupg/secring.gpg' created
gpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: requesting key 34D8786F from hkp server pool.sks-keyservers.net
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key 34D8786F: public key "Dell Inc., PGRE 2012 (PG Release Engineering Build Group 2012) <PG_Release_Engineering@Dell.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
root@omsa:~#
root@omsa:~# gpg -a --export 1285491434D8786F | apt-key add -
OK
root@omsa:~# apt-get update
Hit http://ftp.hu.debian.org wheezy Release.gpg
Hit http://ftp.hu.debian.org wheezy-updates Release.gpg
Hit http://ftp.hu.debian.org wheezy Release
Hit http://ftp.hu.debian.org wheezy-updates Release
Hit http://ftp.hu.debian.org wheezy/main Sources
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://ftp.hu.debian.org wheezy/main i386 Packages
Hit http://ftp.hu.debian.org wheezy/main Translation-en
Hit http://ftp.hu.debian.org wheezy-updates/main Sources
Hit http://ftp.hu.debian.org wheezy-updates/main i386 Packages/DiffIndex
Hit http://security.debian.org wheezy/updates Release
Hit http://ftp.hu.debian.org wheezy-updates/main Translation-en/DiffIndex
Hit http://security.debian.org wheezy/updates/main Sources
Hit http://security.debian.org wheezy/updates/main i386 Packages
Hit http://security.debian.org wheezy/updates/main Translation-en
Get:1 http://linux.dell.com  Release.gpg [827 B]
Hit http://linux.dell.com  Release
Hit http://linux.dell.com  Packages
Ign http://linux.dell.com  Translation-en_US
Ign http://linux.dell.com  Translation-en
Fetched 827 B in 4s (187 B/s)
Reading package lists... Done
root@omsa:~#
root@omsa:~# apt-get install srvadmin-omcommon
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation: The following packages have unmet dependencies:
 srvadmin-omcommon : Depends: libssl0.9.8 (>= 0.9.8k-1) but it is not installable
E: Unable to correct problems, you have held broken packages.
root@omsa:~# dpkg -l|grep libssl
ii  libssl1.0.0:i386                     1.0.1e-2+deb7u16              i386         SSL shared libraries
WTF happens
root@omsa:~# wget http://snapshot.debian.org/archive/debian/20110406T213352Z/pool/main/o/openssl098/libssl0.9.8_0.9.8o-7_i386.deb

--2015-04-03 11:55:41--  http://snapshot.debian.org/archive/debian/20110406T213352Z/pool/main/o/openssl098/libssl0.9.8_0.9.8o-7_i386.deb
Resolving snapshot.debian.org (snapshot.debian.org)... 185.17.185.187, 193.62.202.30, 2001:630:206:4000:1a1a:0:c13e:ca1e, ...
Connecting to snapshot.debian.org (snapshot.debian.org)|185.17.185.187|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3090794 (2.9M) [application/x-debian-package]
Saving to: `libssl0.9.8_0.9.8o-7_i386.deb'
100%[=========================================================================================================================================================>] 3,090,794   1.11M/s   in 2.6s

2015-04-03 11:55:44 (1.11 MB/s) - `libssl0.9.8_0.9.8o-7_i386.deb' saved [3090794/3090794]

root@omsa:~# dpkg -i libssl0.9.8_0.9.8o-7_i386.deb
Selecting previously unselected package libssl0.9.8.
(Reading database ... 24865 files and directories currently installed.)
Unpacking libssl0.9.8 (from libssl0.9.8_0.9.8o-7_i386.deb) ...
Setting up libssl0.9.8 (0.9.8o-7) ...

root@omsa:~# apt-get install srvadmin-omcommon
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libsmbios2 python-libsmbios smbios-utils srvadmin-omilcore
Suggested packages:
  libsmbios-doc
The following NEW packages will be installed:
  libsmbios2 python-libsmbios smbios-utils srvadmin-omcommon srvadmin-omilcore
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,685 kB of archives.
After this operation, 24.5 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
[.....]
Setting up python-libsmbios (2.2.13-0ubuntu4) ...
Setting up smbios-utils (2.2.13-0ubuntu4) ...
Setting up srvadmin-omilcore (7.1.0-3) ...
     **********************************************************
     After the install process completes, you may need
     to log out and then log in again to reset the PATH
     variable to access the Dell OpenManage CLI utilities
     **********************************************************
Setting up srvadmin-omcommon (7.1.0-2) ...
root@omsa:~#

root@omsa:~# apt-get install srvadmin-all
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libargtable2-0 libasound2 libopenipmi0 libperl5.14 libsensors4 libsnmp-base libsnmp15 libxi6 libxslt1.1 libxtst6 openipmi setserial snmpd srvadmin-base srvadmin-deng srvadmin-hapi
  srvadmin-idrac srvadmin-idrac-ivmcli srvadmin-idrac-vmcli srvadmin-idrac7 srvadmin-idracadm srvadmin-idracadm7 srvadmin-isvc srvadmin-jre srvadmin-megalib srvadmin-omacore
  srvadmin-rac-components srvadmin-rac4 srvadmin-rac4-populator srvadmin-rac5 srvadmin-racadm4 srvadmin-racadm5 srvadmin-racdrsc srvadmin-racsvc srvadmin-smcommon srvadmin-smweb
  srvadmin-storage srvadmin-storageservices srvadmin-storelib srvadmin-storelib-sysfs srvadmin-sysfsutils srvadmin-tomcat srvadmin-webserver srvadmin-xmlsup x11-common
Suggested packages:
  libasound2-plugins lm-sensors snmp-mibs-downloader
The following NEW packages will be installed:
  libargtable2-0 libasound2 libopenipmi0 libperl5.14 libsensors4 libsnmp-base libsnmp15 libxi6 libxslt1.1 libxtst6 openipmi setserial snmpd srvadmin-all srvadmin-base srvadmin-deng
  srvadmin-hapi srvadmin-idrac srvadmin-idrac-ivmcli srvadmin-idrac-vmcli srvadmin-idrac7 srvadmin-idracadm srvadmin-idracadm7 srvadmin-isvc srvadmin-jre srvadmin-megalib srvadmin-omacore
  srvadmin-rac-components srvadmin-rac4 srvadmin-rac4-populator srvadmin-rac5 srvadmin-racadm4 srvadmin-racadm5 srvadmin-racdrsc srvadmin-racsvc srvadmin-smcommon srvadmin-smweb
  srvadmin-storage srvadmin-storageservices srvadmin-storelib srvadmin-storelib-sysfs srvadmin-sysfsutils srvadmin-tomcat srvadmin-webserver srvadmin-xmlsup x11-common
0 upgraded, 46 newly installed, 0 to remove and 0 not upgraded.
Need to get 115 MB of archives.
After this operation, 319 MB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://ftp.hu.debian.org/debian/ wheezy/main libasound2 i386 1.0.25-4 [463 kB]
Get:2 http://linux.dell.com/repo/community/deb/latest/  srvadmin-deng 7.1.0-3 [1,230 kB]
Get:3 http://ftp.hu.debian.org/debian/ wheezy/main libsensors4 i386 1:3.3.2-2+deb7u1 [53.9 kB]
Get:4 http://ftp.hu.debian.org/debian/ wheezy/main libxi6 i386 2:1.6.1-1+deb7u1 [76.6 kB]
[.......]
Setting up srvadmin-racsvc (7.1.0-3) ...
Setting up srvadmin-rac4-populator (7.1.0-3) ...
Setting up srvadmin-rac-components (7.1.0-2) ...
Setting up srvadmin-racdrsc (7.1.0-2) ...
Setting up srvadmin-rac4 (7.1.0-3) ...
Setting up srvadmin-racadm5 (7.1.0-2) ...
update-alternatives: using /opt/dell/srvadmin/sbin/racadm-wrapper-rac5 to provide /opt/dell/srvadmin/sbin/racadm (racadm) in auto mode
Setting up srvadmin-rac5 (7.1.0-2) ...
Setting up srvadmin-idracadm (7.1.0-2) ...
Setting up srvadmin-idrac-vmcli (7.1.0-2) ...
Setting up srvadmin-idrac-ivmcli (7.1.0-2) ...
Setting up srvadmin-idrac (7.1.0-2) ...
Setting up srvadmin-idracadm7 (7.1.0-2) ...
Setting up srvadmin-idrac7 (7.1.0-2) ...
Setting up srvadmin-all (7.1.0-3) ...
root@omsa:~#

Further reading: http://linux.dell.com/repo/community/deb/latest/
http://serverfault.com/questions/425322/how-to-set-up-dell-omsa-tools-on-debian-6-squeeze-pe2950

2015. március 23., hétfő

powershell - check if exists

Taken from various forums... can't remember where from.

do {
$testpath = Test-Path -path \\dns2\d$\test
start-sleep -s 10}
until ($testpath -eq $true)

do {
    sleep -seconds 1
    $mailboxExists = get-mailboxpermission -Identity "CN=$displayName,$DN" -User "NT AUTHORITY\SELF" -ErrorAction SilentlyContinue |fw IsValid
    write-host "." -nonewline
} while (!$mailboxExists)


Import-Module ActiveDirectory
#Import CSV
$csv = @()
$csv = Import-Csv -Path "C:\Temp\bulk_input.csv"

#Get Domain Base
$searchbase = Get-ADDomain | ForEach {  $_.DistinguishedName }

#Loop through all items in the CSV
ForEach ($item In $csv)
{
  #Check if the OU exists
  $check = [ADSI]::Exists("LDAP://$($item.GroupLocation),$($searchbase)")
  
  If ($check -eq $True)
  {
    Try
    {
      #Check if the Group already exists
      $exists = Get-ADGroup $item.GroupName
      Write-Host "Group $($item.GroupName) alread exists! Group creation skipped!"
    }
    Catch
    {
      #Create the group if it doesn't exist
      $create = New-ADGroup -Name $item.GroupName -GroupScope $item.GroupType -Path ($($item.GroupLocation)+","+$($searchbase))
      Write-Host "Group $($item.GroupName) created!"
    }
  }
  Else
  {
    Write-Host "Target OU can't be found! Group creation skipped!"
  }
}

2015. március 6., péntek

How to intall smokeping - the only way it works :)

What is smokeping? That's a powerful network monitoring tool which works mainly with tricky ICMP pings and also able to do special TCP and UDP port connection tests built-in. You can check your statistics on web based graphs.

How to install it? There are blogs that discusses the process but I strongly recommend not to follow them word for word because they suffer from serious errors that keep you from succeeding. Happily you are here, at the perfect place for the perfect tutorial!

What is a master and slave configuration?
Master is actually your central smokeping server. It periodically checks the hosts you configured to monitor. Nothing surprising, ehm ? Let's look at the slave(s) then. They check BACK to the master (or any other configured host) and send their results BACK to the master who process their data and displays the results together with its normal monitoring data.

Okay, let's install my master Debian/Ubuntu node first. I'm going to create two logical units inside my monitoring tree. I'll call the first "External hosts" and the second (guess what) "Internal hosts".

MASTER node
------
apt-get update
apt-get install smokeping
Check if /etc/default/smokeping has only ONE active line: "MODE=master"
cd /etc/smokeping/
touch slave-secrets
You define here your SLAVE servers individual passwords. In my case I will have two slave (also active checking) servers in my "External hosts", see later.
cat /etc/smokeping/slave-secrets
mywebserver:topsecr3t
myftpserver:topsecr3t
echo "topsecr3t" > slavesecrets.conf
chmod 660 slave-secrets
chmod 600 slavesecrets.conf
chown smokeping:www-data slave-secrets slavesecrets.conf
cd config.d/
cat Alerts
*** Alerts ***
to = me.admin@mydomain.com
from = smokeping@mydomain.com

[...others are remain the same default...]
cat Database
*** Database ***

step     = 200
pings    = 100

[...others are remain the same default...]
These two variables are changed because I want to check my hosts in every 200 seconds with 100 ping packets.
cat General
*** General ***

owner    = Me.Da.Admin
contact  = me.admin@mydomain.com
mailhost = localhost
# NOTE: do not put the Image Cache below cgi-bin
# since all files under cgi-bin will be executed ... this is not
# good for images.
cgiurl   = http://localhost/cgi-bin/smokeping.cgi
[...others are remain the same default...]
 cat Probes
*** Probes ***

+ FPing

binary = /usr/bin/fping
packetsize = 500
pings = 100
step = 200
timeout = 1.5
[...others are remain the same default...]
Several other parameters can be used, see later.
 cat Slaves
*** Slaves ***
secrets=/etc/smokeping/slave-secrets

+mywebserver
display_name=My Great webserver
color=ff0000

+myftpserver
display_name=My Super FTP server
color=00b7e2

I've defined here my slave servers. NOT those hosts I want to check. Don't be confused: these two categories are totaly different!
cat Targets
 *** Targets ***
probe = FPing

menu = Top
title = Network Latency Grapher
remark = Welcome to my little SmokePing website.

+ External
menu = External hosts
title = Ext

++ mywebserver
menu = My Superb Webserver
host = 10.243.43.6

++ myftpserver
menu = My gorgeos ftpserver
host = 172.16.29.253

++ mysmokeping
menu = this.server
host = 195.95.95.95
slaves = mywebserver myftpserver

+Internal
menu = Interal hosts
title = Gateways

++ MyGateway
menu = My Little Cisco Switch
host = 172.16.21.254

I've set the most important things here: my monitored hosts. Probe type is simple fping. Two units here: External and Internal. Their friendly name will shown in the web menu as "External hosts" and "Internal hosts". External has 3 hosts inside it: two external servers and the monitor server itself. mywebserver and myftpserver HAVE to be the same string as the servers identifies themselves! (as they answer to the "hostname" shell command) ++mysmokeping section MUST HAVE the "slaves = mywebserver myftpserver" line. If you don't have it, the slaves are going to reply with the unpleasant message
"ERROR: we did not get config from the master. Maybe we are not configured as a slave for any of the targets on the master ?"
/etc/init.d/smokeping restart
If you can't see any useful answer to this :) you may find this command profitable: journalctl -xn

Wait some minutes and point your browser to http://195.95.95.95/smokeping/smokeping.cgi

And! Here is the point for slaves: set your file rights according to the following:
/var/lib/smokeping# ls -sal
[...]
4 drwxrwx---  2 smokeping www-data  4096 Mar  6 13:05 External
cd smokeping/
chown smokeping:www-data *
chmod 755 *
This is a MUST to let the Slaves able to POST their data to apache running on your smokeping master.

SLAVE nodes
-----
apt-get install smokeping
cat /etc/default/smokeping
MODE=slave
MASTER_URL=http://195.95.95.95/cgi-bin/smokeping.cgi
SHARED_SECRET=/etc/smokeping/slavesecrets.conf

Note that this is considerably unsecure configuration. Use VPN connections, firewalls or other type of http authentication,in .htaccess for example. The above 3 lines you have to have, no more or less.
echo "topsecret" > /etc/smokeping/slavesecrets.conf
ls -sal /etc/smokeping/slavesecrets.conf
Set file rights as:
-r--r-----  1 smokeping root   13 Mar  6 07:41 slavesecrets.conf

All the other files are needless here. You can safely delete the whole config.d/ directory for example. Nice, huh?
/etc/init.d/smokeping restart
 Wait some minutes and watch your slave-driven data flow under your "External" session on your Master's webpage.
In case anything going wrong - or nothing, check your apache error log:
cat /var/log/apache/error.log

Check the online manual for further reference.

2015. március 3., kedd

Incremental back up vhdx files of Hyper-V Virtual Machines hosted on Cluster Shared Volumes to a network share

It's 2015 so why would anyone still use Windows Server 2008 R2? Windows Server Backup in Windows Server 2012 includes great (but limited,see below) support for CSV backup. Some notes and warnings:
  •     Virtual machines hosted on CSV’s cannot be added as part of normal system backup configuration
  •     Windows Server Backup has to be configured on all nodes to ensure that backup and recovery will be available in the event of a failure on one of the nodes in the cluster.
  •     Volumes recovery not supported - can be cheated
  •     Security access control lists are not applicable on CSV file service root. Therefore, file recovery to the root of CSV volume is not supported.
Say you have two Hyper-V hosts, one SAN hosting your VMs' files via Cluster Shared Volumes for your Hyper-V Hosts and you also have four VMs on the Hosts - each has two VMs. You already set up your OS level (e.g. Windows Backup) jobs inside your Hosts OSs and VM OSs and has already been backing up your data to the SAN on dedicated backup LUNs lying on physically separeted fault tolarent arrays. Look sufficient, isn't it.
Actually, it isn't that good. What if your SAN blows up? You lost all your VMs and your VMs' backups at the same time. You also need to have a fool-proof off-site backup and it must be easily handled. Luckily, there is a simple solution without the need to include third party tools, like HVbackup. (which is, anyway, a good one)
Let's say that your first Hyper-V Host server called HOST1 and your VMs running by it are named VM1 and VM2.
So you have a file system on Host1 like this:

as C:\ClusterStorage\Volume4\VM1\ ....

To backup your first virtual guest (with its entire CSV, being on the safe side) on your external backup server share, just execute:

wbadmin start backup -include:C:\ClusterStorage\volume4\ -backuptarget:\\backupserver\vmbackup\vm1

It takes some time:

You can easily restore files from your VM's virtual disk if you find it in the backup:
Then just mount it in your Disk Management (Attach VHD) .....
and then assign a drive letter to it, open your new disk with a file explorer and find your real VD :) inside it. You should repeat above process by attaching this real VD also with your Disk Management console.

In case you need to restore your whole VM (whole means: disaster recovery including all its Hyper-V settings)
Find your backup versions: (if you are lucky enough to have more than a single one)

wbadmin get versions -backuptarget:\\backupserver\vmbackup\vm1

Restoring: (be careful)

wbadmin start recovery -version:02/11/2015-08:25 -backuptarget:\\backupserver\vmbackup\vm1 -itemtype:file -items:C:\ClusterStorage\Volume4\  -recursive -recoverytarget:Z\recover -machine:HOST1

What did I mean when I said backup versions? Have you ever been frustrated that Windows Backup can't maintain multiple versions on a network share? So did I. I've tried to cheat WSB with using a local hardlink pointing out to the network share.
mklink /D M:\MyNetwork \\mybackupserver\vmbackup
and
wbadmin start backup -include:C:\ClusterStorage\volume4\ -backuptarget:\\localhost\d$\MyNetwork\vm1 -quiet
Tadaamm! So far so good.

Unfortunately,
wbadmin get versions -backupTarget:M:\MyNetwork                                               
matter-of-factly answers that it can't be fooled in such a stupid way.

wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.
The backup cannot be completed because the backup storage destination is a shared folder mapped to a drive letter. Use the Universal Naming Convention (UNC) path (\\servername\sharename\) of the backup storage destination instead. 
In short, it sadly won't be versioning, just keeps one full version as usual. Bad luck. Folks say I should use iSCSI based network drives because thats the only way to get WSB versioning. I don't want to bother with this because I already have lots of iSCSI drives from the SAN and I would be a bit afraid of messing up these drives from different sources.

Meanwhile, here are some useful facts from Technet topics to consider about WBS: 
You can also set -vssFULL  parameter in backup jobs but there's not much use in doing so. According to the manual: "If specified, performs a full backup using the Volume Shadow Copy Service (VSS). Each file's history is updated to reflect that it was backed up. If this parameter is not used, wbadmin start backup makes a copy backup, but the history of files being backed up is not updated." In short: "vssfull is only meaningful if there is another 3rd party backup application is being simultaneously used on the same machine along with server backup application and you have application like exchange running on the machine who have vss writers. if that is not the case - it can be ignored and defaults will work fine."
And "All backups after first backup automatically takes incremental storage space on the backup location since changes are tracked using volume shadow copy on the backup location. This incremental storage space is proportional to the changes from the last backup."

2015. január 9., péntek

How to flush / empty / purge / resize your System Volume Information folder

vssadmin list shadowstorage
[....]
Shadow Copy Storage association                                                         
For volume: (F:)\\?\Volume{7df38471-635b-11e4-9415-000c29dbe934}\                    
Shadow Copy Storage volume: (F:)\\?\Volume{7df38471-635b-11e4-9415-000c29dbe934}\    
Used Shadow Copy Storage space: 249 GB (41%)                                         
Allocated Shadow Copy Storage space: 251 GB (41%)                                    
Maximum Shadow Copy Storage space: UNBOUNDED (2863325530%)
[...]
                        
vssadmin resize shadowstorage /on=F: /For=F: /Maxsize=40GB 
Successfully resized the shadow copy storage association  

If you want to delete a shadowstorage and encounter the infamous error message:

C:\Users\administrator> vssadmin delete shadowstorage /on=F: /For=F:     
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool      
(C)Copyright2001-2013MicrosoftCorp.                                                                                                                         
Error: The specified shadow copy storage association is in use.                

then use your superpower:
cmd> vssadmin list shadows
cmd> diskshadow
diskshadow>list shadows all

diskshadow>delete shadows oldest F:
diskshadow>delete shadows volume F:
diskshadow>delete shadows all
diskshadow>list shadows all
diskshadow>exit