Handoff -- how long?

[craigr]

I believe my handoff from VSS to Vault Standard either went or is going well. I'm at that stage where nothing happens for hours and hours and I'm not sure if that's normal or when I'm going to be able to use my laptop again.

Handoff processed all my projects, which I previously calculated consisted of about 84,000 files and 19+ GB. Now it says it's committing about 69,000 files... and there it sits. For 3 hours. With no feedback. I can't move the laptop out of the WiFi network it's in or I'll lose any indication of when it's done. So... is there a way to tell a) if it's actually still doing anything, b) when it's done if I shut off my laptop or have a temporary WiFi glitch, or c) how much longer it's going to take? I need to pack it up tomorrow morning and it would be nice to know if it's going to be done or if I should make other plans.

And then as I'm looking around here on the site it looks like I have to keep VSS and my VSS data installed on the server because it isn't really handing it off but rather it needs to have the old data for history. WTH? Seriously? Is there a better way to do this so that we're not saddled forever with this hybrid solution where some of our data will forever require that an ancient and rapidly unsupported app has to always be installed on any server we move to, and we'll never be able to reclaim that space? I thought I was upgrading away from VSS. I don't want to be saddled with it forever. That's what I'm paying you guys to do for me.

And by way of suggestion: You should explain how much temporary disk space is required by this process because it's pretty major and by default it ends up in C:\WINDOWS\TEMP which on many older systems doesn't have a lot of space available for growth. I got errors with my first (so-called) handoff and had to move the temp folders to other drives.

Craig

[lbauer]

A lot depends on how big your VSS database is, whether the Handoff encountered problems getting files, how many shares, pins there are.

Check the Vault Server log to see if there are any errors. It's called sgvault.log and is in %windir%\temp\sgvault on the server machine. Look at CPU/Memory use. Is it fluctuating at all?

[craigr]

Like I said... The VSS data is 19GB. The log just has an entry for when I logged in as admin. Nothing else. There were no errors reported on-screen during the processing of the projects.

It looks like the sgvault table is processing transactions and there is CPU activity. So it's running. Any way to know when it will be done?

Any comments on my questions about having to keep VSS installed for the rest of my life? Am I missing something there?

[lbauer]

Any way to know when it will be done?

I wish I could give you a time estimate, but we don't really know. Maybe estimate 10 seconds per transaction?

If you use Handoff and need to access VSS history, then yes, you need to keep the database. But after a time, you may not need the VSS database anymore and can remove it. You'd get an error if you tried to access VSS history.

Another way to bring in your VSS database is with the full VSS import. It imports all your history. However a 19 GB VSS database would take several days to import and might not be error-free because of the tendency for VSS to have data corruption. If you archive off only the last several versions you need, you might be able to do the full import.

http://support.sourcegear.com/viewtopic ... 13&t=12240

[craigr]

I happened to be awake at 3:30 AM (14.5 hours) and it was done. 10 seconds per transaction is 8 days, so perhaps I should count myself lucky?

I'm disappointed about the necessity to keep VSS installed for the rest of the life of my company, and that to actually replace it (which is what I thought I was doing) would take days/months/whatever to import.


Craig

[lbauer]

and that to actually replace it would take days/months/whatever to import.

It probably took many years and many thousands of transactions to create your VSS database. You're right, such an import won't happen overnight. However, it's a one time task, and then you're done.

If you feel all that data and VSS history is important in the coming years, then it might be worth the effort. Otherwise you can choose to only import the more recent version(s), keep VSS for a while, then only use the history you've created in Vault.