I was dealing with a new customer with that error recently that accidentally had included their old backup solution's folders in the Unitrends backup, resulting in a backup that was a few TB larger than the appliance capacity... thus the no space error.

Is this the exact error?

“FATAL: NO MORE SPACE ON DEVICE (DESPITE RECOVERY ATTEMPTS).

No purgable backups were found.”

That's more like it. Carry on.

I thought this was a random thread. There seems to be a very pronounced pattern as of late...

Wait... what? No hat? Who is that guy? Did your experience being accidentally hat-free at Spice World usher in a new chapter in your life?

@NetworkNerd said:

@ajstringham said:

@NetworkNerd said:

Maybe I could use the HP DL 385 G5 I have with the MSA 70 and run something like FreeNAS on it for another datastore option?

That's one option. Something that would be good for, to be honest, would be your StorageCraft server, if you go with that.

I was thinking use it as a NFS datastore and a place to store the VM files for my current physical machines like was mentioned above. That saves money on a secondary backup solution.

Actually, that would be a tertiary backup solution, as you have Veeam and BE already. The original decision seemed to be "buy hardware or buy another backup solution". It seems that utilizing current hardware like that could avoid both?

Sorry if I ruined anyone's night. No, there are no nude pics of me on my phone, so don't waste time trying to hack my accounts.

I still say the same thing I have been saying all along. If there were any nude pics on my phone, they would NOT be of myself! What kind of person has nude pics of themselves on their phone? The only thing that would make sense is if they were purposely taken to send to someone else. At that point, there are any number of avenues they can take to being viewed by God-knows-who out there. At the very least, whoever the intended recipient was probably showed them to all his buddies. Dumb. Just dumb. Or, it was done on purpose. Either way, how is that Google's problem or fault?

@scottalanmiller said:

@art_of_shred It's been a while, I'm not sure that I can identify the pre-MS Skype from the new Skype behaviour anymore.

I don't use it enough to really know. It just seemed that the change was in the months-long gap I didn't use it; and the switch-over was in that same gap.

@Dashrender said:

@JaredBusch said:

@Dashrender said:

Are you then saying that a closed window with the icon still on the taskbar, not just the notification area is closed? definitely not what I consider closed.

It is closed because the X button is a close window button. Not a close application button. That is by design. Yes a developer can additionally add in a function to Application.Exit(), but that is not required nor default.

Understood, but close window to me means not in the task bar (but can be in the notification bar). And - that is the way Skype USED to work.

Yes. Am I mistaken, or did that change when MS took over Skype?

@JaredBusch said:

@art_of_shred said:

This is where I agree that it is somewhat annoying. If you're going to have a standard, keep to the standard. I like the X to close an application. But, this is the real world, where we don't always get what we want. And it's not always selectable in the options menu. Oh well.

I agree that it would be nice, but that would require a change int he default windows behavior.

On a side note, An application also has a setting at the project level that developers can choose to exit an application after all forms are closed. By setting this, a dev does not have to write code into the X button and the application will still close once all the windows forms are closed. I do not like to trust in that functionality though and I always specifically code my windows forms to exit the application on form close as appropriate to the app.

Thanks for that information. I never knew that (why would I?), and I guess it makes all the difference.

@scottalanmiller said:

@art_of_shred said:

No, I am not calling that closed. I am saying how is sitting in the task bar different than going to the notifications? Either way, it's still running in the background.

Point taken. One, though, is in your face and one is not. Often people are looking to clean up their taskbars, that was the purpose of choosing the close button over the minimize button explicitly but then it does exactly what the minimize button is for. It's not that you need to close it all of the time, but if you have a button with the only viable reason for its existence being to at least get it out of the task bar (I'd prefer if it actually shut it down, I shouldn't need multiple steps for such a common task) I'd like to not be surprised by a change in the Windowing interface and have to take additional actions for an action I already clearly conveyed to the application.

This is where I agree that it is somewhat annoying. If you're going to have a standard, keep to the standard. I like the X to close an application. But, this is the real world, where we don't always get what we want. And it's not always selectable in the options menu. Oh well.

@Dashrender said:

@JaredBusch said:

@art_of_shred said:

Define "not close". If I hit the X and it's still running, that means not closed to me. That's what Lync does, that's what nearly every chat thing I've used does. It's pretty normal.

By definition based on the links posted previously and by my personal experience writing windows form based applicaitons, it is a close window button. it is not a close applicaiton button unless the software developer also specifically adds code in the Me.FormClosed event handler. A lot of basic applications do this, so it is how people assume that it is an exit program button.

Are you then saying that a closed window with the icon still on the taskbar, not just the notification area is closed? definitely not what I consider closed.

No, I am not calling that closed. I am saying how is sitting in the task bar different than going to the notifications? Either way, it's still running in the background.

Define "not close". If I hit the X and it's still running, that means not closed to me. That's what Lync does, that's what nearly every chat thing I've used does. It's pretty normal.

I will admit I rarely use Skype unless prompted to do so by a team member. However, I won't assume that anyone else out there uses it in any specific way. Making assumptions about a widely-used product based on the (mostly assumed) information you have about how the people you know and their use of it, is basically worthless. Like I have a clue what millions of people out there are using their Skype accounts for. You don't either. Get used to it.

As Joe and I were just sitting here discussing it, it seems a large number of communications apps behave that way. Is it that hard to right-click the icon in the tray and hit close? It's always worked for me.

Well, it's not just Skype. I've encountered plenty of software that is legitimate software that doesn't actually close when you click the "X". It's mildly annoying, but it hasn't caused me to question the motives or legitimacy of the manufacturer or the product. It's just annoying and I learn how to make it do what I want. If people in general aren't that smart... well... too bad for them.

@JaredBusch said:

I cannot wear this years shirt yet. I only picked up large size shirts this year. I am right on the boarder of it looking too tight to wear in public. Another 10 pounds and it should be wearable..

What's wrong with a too-tight shirt that says "cheap. fast. easy. just the way you like it."? That should be the only way to wear it!

So, you're saying there's a chance I could make it as a singer?

If you turn a fan on while doing it, I seriously can't tell the difference.