Is it good idea to schedule sdelete.exe -z c:: for kvm?

KVM has nothing to do with it. In its simplest case, sdelete zeroes the free space, which means:
- for qcow2 it will grow the qcow2 to its maximum size. Then you will need to run qemu-img to shrink it back by removing zeroed blocks
- for sparse raw files it will fill the whole size (i don't know if sparse file handling frees a zeroed block or not. I think rather not)
- for pre-allocated storage (like LVM or full .raw disk) it does nothing

Do you have more information on how "it really helps out"?
 
ozgurerdogan said:
Yes thats why I use sdelete. My disk formats are .raw. So was just wondering if using windows task scheduler to automate sdelete ok ? or better using it manually?
Click to expand...

I normally run it manually when I see backups growing larger than I like.

I see nothing wrong with running it on a schedule if that is your preference.
Just make sure you do not schedule it to run when high disk io would cause problems or during the VM backup.
 
e100 said:
I normally run it manually when I see backups growing larger than I like.

I see nothing wrong with running it on a schedule if that is your preference.
Just make sure you do not schedule it to run when high disk io would cause problems or during the VM backup.
Click to expand...

I think you are right at that point. I would only need to run it maybe 3-4 time a year. So can handle it with manual running. Only matter I have 9 kmvs. By the way, what do you do for linux kmvs if you have one to free up space when backing up?
 
You must log in or register to reply here.
Top Bottom