Offsite use of Vault

[ProspectiveBuyer]

I looked around at all the support forums to try to get an answer to this question, but was unsuccessful. Is is possible to use Vault from a remote site via an internet connection like you can with sourceoffsite? If so, is this a built-in feature of the Vault client, or do I need sourceoffsite in addition to Vault?

Thanks for clearing up my confusion.

[dan]

Yes, remote access is a built-in feature of Vault - it goes through IIS, so any machine that can get to your IIS server can access Vault.

[nicolajb]

But what will perform best when conecting remotely?
1) SoS on top of VSS
or
2) Vault?

[lbauer]

It depends on your particular work flow and database configuration.

SourceGear Vault is significantly faster than VSS over a remote connection. Just like SourceOffSite, Vault is also built for speed across a network, and in most cases will be almost as fast as SourceOffSite. The difference is that Vault will be slower than SOS for some operations, but will be faster than SOS for other operations.

For instance, Vault sends file deltas, which means that Vault only transmits information about what information has changed, rather than the new file. This can really have an impact when dealing with large files with few changes. So, for example, if you are downloading 100 10K files for the first time, SourceOffSite will be faster than Vault, which would be faster than VSS. However, if you were downloading 10 100K files, all of which had one line changed, Vault would be much faster than SOS.

We recommend you try Vault for yourself, to see how it works in your particular environment.

[Guest]

This may seem like a completely clueless questions, so patience please. I am the one responsible for the implementation but not the one doing the evaluation... but if feels like a couple of questions were not asked, but assumed.

Our company recently move to using SorceOfSite ontop of VSS. ( great product )

Recently my team was notified that the company will be moving shortly to using Vault and dropping VSS, yet for those team members working off-site, will continue to use SOS ontop of Vault, instead of VSS. ( this was a statement made by our Product Mngr.)

1) is this possible? ( cant find documentation on this yet)

2) if possible, is this reasonable?

3) if not possible - we have several scripts and tools that currently rely on the SOS command line client. How easy will it be to port these to work with the Vault command line client?

4) can our SOS licenses be transferred toward Vault licenses, if we do move the Source Control to the Vault route.

5) Are the offsite capabilities of Vault as robust as those of SourceOfSite?

Thanks

[ericsink]

This may seem like a completely clueless questions, so patience please. I am the one responsible for the implementation but not the one doing the evaluation... but if feels like a couple of questions were not asked, but assumed.

Our company recently move to using SorceOfSite ontop of VSS. ( great product )

Recently my team was notified that the company will be moving shortly to using Vault and dropping VSS, yet for those team members working off-site, will continue to use SOS ontop of Vault, instead of VSS. ( this was a statement made by our Product Mngr.)

1) is this possible? ( cant find documentation on this yet)

2) if possible, is this reasonable?

3) if not possible - we have several scripts and tools that currently rely on the SOS command line client. How easy will it be to port these to work with the Vault command line client?

4) can our SOS licenses be transferred toward Vault licenses, if we do move the Source Control to the Vault route.

5) Are the offsite capabilities of Vault as robust as those of SourceOfSite?

Thanks

1. No, SOS cannot be used as a front end for Vault.

2. "Offsite" capabilities are built-into Vault, so SOS is not needed.

3. It shouldn't be terribly difficult to adapt those scripts, but they will need some changes.

4. Sorry, no. We have no special pricing break for moving from SOS to Vault. Vault is priced so aggressively that we don't really have room to offer additional discounts for SOS users.

5. Vault's remote access capabilities are actually somewhat stronger than those of SOS. For example, Vault can send binary deltas in both directions, whereas SOS cannot. Vault travels over the HTTP protocol, considered friendlier to firewalls. Vault supports absolutely all operations from a remote client, whereas SOS omits a few advanced features such as merge branches.

[guest(prospectivebuyer)]

1. No, SOS cannot be used as a front end for Vault.

2. "Offsite" capabilities are built-into Vault, so SOS is not needed.

3. It shouldn't be terribly difficult to adapt those scripts, but they will need some changes.

4. Sorry, no. We have no special pricing break for moving from SOS to Vault. Vault is priced so aggressively that we don't really have room to offer additional discounts for SOS users.

5. Vault's remote access capabilities are actually somewhat stronger than those of SOS. For example, Vault can send binary deltas in both directions, whereas SOS cannot. Vault travels over the HTTP protocol, considered friendlier to firewalls. Vault supports absolutely all operations from a remote client, whereas SOS omits a few advanced features such as merge branches.

Thank you for the truely quick reply .... really appreciate the information.

If I may suggest, it might be usefull to others, if the infomration above was made available in the FAQ's.