The new nowait parameter

[TAC109]

I've a few questions about the new /nowait parameter:

In the manual it states that it must be the first parameter. I take it that
it is the 'first' after the /b parameter?

Is it true that in the current implementation the /nowait parameter can
only be used effectively in a TBWinPE/RE environment because PHYLock and
VSS are disabled?

Any plans to remove these restrictions in future versions?

[TeraByte Support]

has to be the very first parameter after the .exe name.

it's more for restoring or copying offline to several targets at the same
time.

only one active instance of phylock or vss can be active, so no. use /wait
to backup back to back or if you don't need them (not in use), it will lock
to do the backup.


"Tom Cole" wrote in message news:9870@public.image...

I've a few questions about the new /nowait parameter:

In the manual it states that it must be the first parameter. I take it that
it is the 'first' after the /b parameter?

Is it true that in the current implementation the /nowait parameter can
only be used effectively in a TBWinPE/RE environment because PHYLock and
VSS are disabled?

Any plans to remove these restrictions in future versions?

[TAC109]

Thanks.

Are you saying that the /nowait parameter can't be used to, say, backup 2
physically different drives in parallel (in a TBWinPE/RE environment)?

"TeraByte Support" wrote:
> has to be the very first parameter after the .exe name.
>
> it's more for restoring or copying offline to several targets at the same
> time.
>
> only one active instance of phylock or vss can be active, so no. use /wait
> to backup back to back or if you don't need them (not in use), it will lock
> to do the backup.
>
>
> "Tom Cole" wrote in message news:9870@public.image...
>
> I've a few questions about the new /nowait parameter:
>
> In the manual it states that it must be the first parameter. I take it that
> it is the 'first' after the /b parameter?
>
> Is it true that in the current implementation the /nowait parameter can
> only be used effectively in a TBWinPE/RE environment because PHYLock and
> VSS are disabled?
>
> Any plans to remove these restrictions in future versions?

[TeraByte Support]

no, not saying that.

they would be locked for backup, phylock/vss is not used in that
environment.

NOTE: use a drive letter, you can't save two to the same using File (direct) target or you'll get corruption.

"Tom Cole" wrote in message news:9872@public.image...

Thanks.

Are you saying that the /nowait parameter can't be used to, say, backup 2
physically different drives in parallel (in a TBWinPE/RE environment)?

"TeraByte Support"

wrote:
> has to be the very first parameter after the .exe name.
>
> it's more for restoring or copying offline to several targets at the same
> time.
>
> only one active instance of phylock or vss can be active, so no. use
> /wait
> to backup back to back or if you don't need them (not in use), it will
> lock
> to do the backup.
>
>
> "Tom Cole" wrote in message news:9870@public.image...
>
> I've a few questions about the new /nowait parameter:
>
> In the manual it states that it must be the first parameter. I take it
> that
> it is the 'first' after the /b parameter?
>
> Is it true that in the current implementation the /nowait parameter can
> only be used effectively in a TBWinPE/RE environment because PHYLock and
> VSS are disabled?
>
> Any plans to remove these restrictions in future versions?