Sure, and anyone else... Added replicas and synced. Reconnected partner targets from hyper-v hosts. Basically showing duplicates in disk management. So I'll have a 600GB CSV volume with label HA1 and another 600 GB volume that is basically sitting there unlabeled when I connect via SCSI to the partn...

Thanks, that is the ticket. While I've been in the replication manager before I didn't recall an option to recreate the device on the secondary.

Fairly slick actually.

Running V8, lost the array that holds the HA images.

What's the best way to get it back up? I have the starwind config file for the server.

Thanks.

Well, there shouldn`t be any new drives. Have you enabled support for iSCSI devices in MPIO manager on all the client machines? Oh yeah, they are humming along fine with the other five targets and MPIO. If I use the initiator to connect to the newly created replica...the drive will show up in "...

Have two StarWind nodes..let's call them S1 and S2. Have two hyper-v hosts that target both of them, call them H1 and H2. All iSCSI and CSV of course. So I removed the replica partner for two targets from S2. Then added the replica partner back in (under a different target name) and everything says ...

I can verify this behavior...

After tape ejects (an LTO-5 tape drive Quantum) it will appear online for backup exec 2014. If you do something simple like an inventory the tape it will immediately appear offline.

Basically right clicking to turn it back to "online" and it is fine.

This is a hyper-v environment so take it for what it is worth. I just basically do straight HA, no dedupe or other stuff. Just basically HA images. I basically did a damn the torpedoes type thing and shutdown the starwind service on one of the nodes. Then upgraded a starwind node to V8. It resynced ...

Can you answer the question if it will require downtime during an upgrade or will it sync off a V6 partner?

This an interesting question because I've noticed something similar (although much smaller amounts disk usage)....

Do you stop the Starwind service before you did the reboots or did you just restart the servers during the patching?

Version 8 sounds awesome. Solving the blender effect, ssd cache, etc.

With that said, would be nice if you can expand upon a few of the items. Small writes, upgrading from 6 to 8 procedure, caching....

Try the delayed ack (nagle) registry fix?

TcpAckFrequency key if I remember correctly.

Not sure on your raid controller but... If you swap one drive at a time and let it rebuild after each swap, you should be able to expand your raid after all of them are swapped out. That will save the hassle of redoing the config. As for the other issue with the img files on the wrong drive...and th...

No problem Bruce. Last summer we suffered a major storm that knocked power out for several days. Fortunately (or wishing I was in the Bahamas) I was there. So I did my best to do a clean shutdown on the vm guests and then power off the HA nodes. Not all of us have generators to keep one node alive 2...

Depends on what you are most comfortable with and of course test everything before production. When I do updates to a node I basically run what I want manually and reboot. The HA part will cover the failover part without issue. At worse, users will get a slight pause. When it comes back up the node ...

Just wanted to let you know did the upgrade this morning and thus far everything is fine. Was actually surprised by how fast the HA targets synced.