bbr on windows stemcell about bosh-backup-and-restore HOT 6 CLOSED

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/156944749

The labels on this github issue will be updated when the story is started.

from bosh-backup-and-restore.

Hi @jgprogramming

Currently, cf-deployment with windows cells is not supported by bbr. And there is no way to skip an instance in the deployment when running bbr deployment backup/restore.

Emmanouil && @jamesjoshuahill

from bosh-backup-and-restore.

+1 on this issue--it is blocking us from testing BBR in the persistence pipeline, and I suspect that it will block other teams soon also. I suppose we could deploy the windows cell to a different deployment, but that would be quite a lot of work, and would result in a flaky non-standard deployment for us, so I am reluctant to go down that road.

Is it not possible to just skip windows VMs when traversing a deployment, and just emit a warning? To me that seems like a much better behavior than failing with no way to recover.

from bosh-backup-and-restore.

One thought--if you are running commands via ssh, you could start your script with Exit which will generate an error, but not exit on unix, and will terminate the shell on windows. (since windows is case insensitive, and Unix is not.)

If you want to not have an ugly error in your logs, then the following seems to swallow the error on Unix without causing parse errors on windows:

Exit 2> exit.txt
rm exit.txt

from bosh-backup-and-restore.

Hello @julian-hj and @jgprogramming

We have a new 1.2.4 BBR which works with windows VMs (it properly skips them without failing).

from bosh-backup-and-restore.

@alamages excellent news! We shall unpause DRATS in our pipelines. Thanks for the heads up.

from bosh-backup-and-restore.