What Are You Doing Right Now
-
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
Well, the iSCSI connection isn't required for anything production... so it's not worth downtime and a reboot outside of regular scheduled downtime.
But it's (iSCSI) required so I can do some very important things regarding backups.
Like to create backups?
At a high level, I need to move existing backups to an iSCSI drive, so that I can kill the existing backup RAID, and make a new one using different and more drives, then move the backups back.
But I may have to wait until I can reboot the hypervisor... or perhaps I can connect to the iSCSI device via USB (it's a QNAP). Got it for the purpose of stuff like this, temporary storage and such.
-
The QNAP isn't the problem, Windows is the problem here.
-
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
Well, the iSCSI connection isn't required for anything production... so it's not worth downtime and a reboot outside of regular scheduled downtime.
But it's (iSCSI) required so I can do some very important things regarding backups.
Like to create backups?
At a high level, I need to move existing backups to an iSCSI drive, so that I can kill the existing backup RAID, and make a new one using different and more drives, then move the backups back.
But I may have to wait until I can reboot the hypervisor... or perhaps I can connect to the iSCSI device via USB (it's a QNAP). Got it for the purpose of stuff like this, temporary storage and such.
How much storage space is this qnap providing (and how many TB's worth of backups need to move?)
-
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
Well, the iSCSI connection isn't required for anything production... so it's not worth downtime and a reboot outside of regular scheduled downtime.
But it's (iSCSI) required so I can do some very important things regarding backups.
Like to create backups?
At a high level, I need to move existing backups to an iSCSI drive, so that I can kill the existing backup RAID, and make a new one using different and more drives, then move the backups back.
But I may have to wait until I can reboot the hypervisor... or perhaps I can connect to the iSCSI device via USB (it's a QNAP). Got it for the purpose of stuff like this, temporary storage and such.
How much storage space is this qnap providing (and how many TB's worth of backups need to move?)
About 11 TB of backup data ^_^, QNAP is providing 14.5.
-
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
Well, the iSCSI connection isn't required for anything production... so it's not worth downtime and a reboot outside of regular scheduled downtime.
But it's (iSCSI) required so I can do some very important things regarding backups.
Like to create backups?
At a high level, I need to move existing backups to an iSCSI drive, so that I can kill the existing backup RAID, and make a new one using different and more drives, then move the backups back.
But I may have to wait until I can reboot the hypervisor... or perhaps I can connect to the iSCSI device via USB (it's a QNAP). Got it for the purpose of stuff like this, temporary storage and such.
How much storage space is this qnap providing (and how many TB's worth of backups need to move?)
About 11 TB of backup data ^_^, QNAP is providing 14.5.
That aughta be fun . .
-
I think I'll just go USB 3.0, I dont' have time to wait on iSCSI to uninstall or to reboot the hypervisor.
-
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
Well, the iSCSI connection isn't required for anything production... so it's not worth downtime and a reboot outside of regular scheduled downtime.
But it's (iSCSI) required so I can do some very important things regarding backups.
Like to create backups?
At a high level, I need to move existing backups to an iSCSI drive, so that I can kill the existing backup RAID, and make a new one using different and more drives, then move the backups back.
But I may have to wait until I can reboot the hypervisor... or perhaps I can connect to the iSCSI device via USB (it's a QNAP). Got it for the purpose of stuff like this, temporary storage and such.
Why not just use an SMB share? If iSCSI is being so difficult, the performance difference can't be so much to make it worth the configuration pains.
-
@tim_g said in What Are You Doing Right Now:
The whole thing is just jacked up... and I can't reboot a hypervisor just whenever because iSCSI took a dump.
http://gifimage.net/wp-content/uploads/2017/08/ron-swanson-computer-gif-4.gif
-
Talking with a couple of my bosses about how long we need to retain backups of our production data (database and other files for web application).
-
@travisdh1 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
Well, the iSCSI connection isn't required for anything production... so it's not worth downtime and a reboot outside of regular scheduled downtime.
But it's (iSCSI) required so I can do some very important things regarding backups.
Like to create backups?
At a high level, I need to move existing backups to an iSCSI drive, so that I can kill the existing backup RAID, and make a new one using different and more drives, then move the backups back.
But I may have to wait until I can reboot the hypervisor... or perhaps I can connect to the iSCSI device via USB (it's a QNAP). Got it for the purpose of stuff like this, temporary storage and such.
Why not just use an SMB share? If iSCSI is being so difficult, the performance difference can't be so much to make it worth the configuration pains.
It was already set up as iSCSI, and it takes a lot of time to rebuild the stuff in the QNAP too. Had MS not screwed up, I'd well be on my way. It is directly connected to the hypervisor, so i'd get the full 1gbps bandwidth that I won't even come close to otherwise.
Now that iSCSI isn't working, I'd rather go USB 3 next because it is faster than anything else.
This isn't anything urgent, but needs to get done... this was the time I allotted for it... and of course it isn't working.
-
@tim_g said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
Well, the iSCSI connection isn't required for anything production... so it's not worth downtime and a reboot outside of regular scheduled downtime.
But it's (iSCSI) required so I can do some very important things regarding backups.
Like to create backups?
At a high level, I need to move existing backups to an iSCSI drive, so that I can kill the existing backup RAID, and make a new one using different and more drives, then move the backups back.
But I may have to wait until I can reboot the hypervisor... or perhaps I can connect to the iSCSI device via USB (it's a QNAP). Got it for the purpose of stuff like this, temporary storage and such.
Why not just use an SMB share? If iSCSI is being so difficult, the performance difference can't be so much to make it worth the configuration pains.
It was already set up as iSCSI, and it takes a lot of time to rebuild the stuff in the QNAP too. Had MS not screwed up, I'd well be on my way. It is directly connected to the hypervisor, so i'd get the full 1gbps bandwidth that I won't even come close to otherwise.
Now that iSCSI isn't working, I'd rather go USB 3 next because it is faster than anything else.
This isn't anything urgent, but needs to get done... this was the time I allotted for it... and of course it isn't working.
Yep, sounds exactly right. You had X time to work on it, it broke so now it's X+Y time.
I even agree with you on the USB3 thing. Just needs done already instead of being a pain in the backside.
-
And of course no male-male USB 3 cable...
-
So now on to SMB...
-
@tim_g said in What Are You Doing Right Now:
And of course no male-male USB 3 cable...
bwhaha
I feel sorry for you right now.
-
@tim_g said in What Are You Doing Right Now:
And of course no male-male USB 3 cable...
Gotta roll your own man.
http://hades.mech.northwestern.edu/images/6/67/Soldering_x.gif
-
@mattspeller said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
And of course no male-male USB 3 cable...
Gotta roll your own man.
http://hades.mech.northwestern.edu/images/6/67/Soldering_x.gif
Lol
-
Now I can hope for this going direct connection SMB
-
@tim_g Not nearly so bad as it could be, but ouch.
-
I feel like if it was a Fedora KVM hypervisor, the iSCSI iniator would not have broken. And if it had, it would have been super simple to reinstall it, and not have to reboot.
-
@tim_g said in What Are You Doing Right Now:
Now I can hope for this going direct connection SMB
More like you have that to look forward to allowing you escape Thanks Giving dinner.
Well timed ploy you have there Tim.
"Ohh I've got this server at work that's being a huge pain in the ass, it's just finished. I have to go to the office for a few hours to get this done!"
