Forum Index  ViceVersa HOME         FAQ and Knowledge Base

 FAQForum FAQ   SearchSearch Forum  RegisterRegister 
 ProfileProfile   Log inLog in 

Timestamp issue with ibackup.com network drive
Goto page Previous  1, 2
 
Post new topic   Reply to topic     Forum Index -> Support
Author Message
mlabbe1



Joined: 10 Feb 2006
Posts: 8

PostPosted: Fri Feb 24, 2006 9:39 am    Post subject: Reply with quote

Ran the same test with the old version with and without history and it works correctly. That is, it doesn't have the timestamp issue that the new version has. Looks like some system call changed from one to the next.

Cheers,
Matt
Back to top
TGRMN Software
Site Admin


Joined: 10 Jan 2005
Posts: 8759

PostPosted: Fri Feb 24, 2006 11:11 am    Post subject: Reply with quote

Thanks Matt. I think we now know what the issue is and need to implement a fix in build 2010 before releasing the final version.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com
Back to top
mlabbe1



Joined: 10 Feb 2006
Posts: 8

PostPosted: Fri Feb 24, 2006 11:16 am    Post subject: Reply with quote

Excellent news. Thanks. Let me know if you want me to test the fix in my setup.

Cheers,
Matt
Back to top
TGRMN Software
Site Admin


Joined: 10 Jan 2005
Posts: 8759

PostPosted: Fri Feb 24, 2006 12:22 pm    Post subject: Reply with quote

thanks, can you try this one?
www.tgrmn.com/viceversa2010a.zip
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com
Back to top
mlabbe1



Joined: 10 Feb 2006
Posts: 8

PostPosted: Sat Feb 25, 2006 12:04 pm    Post subject: Reply with quote

Yup, that works like a charm. Thanks for the fix!
Back to top
JanDeBondt
Guest





PostPosted: Thu Aug 02, 2007 11:35 am    Post subject: Reply with quote

Hi,

I just ran into the exact same problem. Only... I am using Vice Versa Pro 2 build 2014 with synchronisation instead of replication.

Could it be that the old 'bug' has slipped back into the new build ?
I will already try Build 2010a a post the result later.
Back to top
KeppelSeghers



Joined: 26 Jul 2007
Posts: 7

PostPosted: Thu Aug 02, 2007 11:47 am    Post subject: Reply with quote

Just tested with build 2010a. It works fine....

Is there somewhere a list with issues solved since build 2010a ? so I can evaluate whether to use 2010a or wait for an update of build 2014

btw: the problem only occurs when I am using a mapped drive to a local folder as source or target.

My G:\ drive is mapped to E:\DATA\PROJECTS.
I need to do this in order to have shorter filenames (<259 characters) since usres are also using a mapping to this folder and so they can put long filenames.

The problem does not occur when I use E:\DATA\Project as source or target

Regards
Back to top
KeppelSeghers



Joined: 26 Jul 2007
Posts: 7

PostPosted: Thu Aug 02, 2007 12:28 pm    Post subject: Reply with quote

Confirmed !
Just tested with Build 2012 -> exactly the same problem.
running the executable ViceVersa2010a.exe, everything works fine.

Will there be a fix or new build available ?
Back to top
FL
Guest





PostPosted: Fri Aug 10, 2007 12:24 am    Post subject: Reply with quote

I am testing 2014 on two machines, experiencing exactly the problem described earlier this post.

Create new file X on machine A

synch

File X on machine B gets new timestamp

synch (2nd time, fine is copied again)

File X on machine A has same timestamp as machine B

any solution to this issue?
Back to top
KeppelSeghers



Joined: 26 Jul 2007
Posts: 7

PostPosted: Fri Aug 10, 2007 10:00 am    Post subject: Reply with quote

sure,
download this file www.tgrmn.com/viceversa2010a.zip
extract it
rename viceversa.exe to viseversa2014.exe
rename viceversa2010.exe to viseversa.exe

you will be running a 2010 version with a fix. for me it works fine.

Off course, I am also still waiting for a fix on 2014 or a new release... TGRMN ?!
Back to top
TGRMN Software
Site Admin


Joined: 10 Jan 2005
Posts: 8759

PostPosted: Fri Aug 10, 2007 10:30 am    Post subject: Reply with quote

Hi KeppelSeghers

Quote:
My G:\ drive is mapped to E:\DATA\PROJECTS.
I need to do this in order to have shorter filenames (<259 characters) since usres are also using a mapping to this folder and so they can put long filenames.

The problem does not occur when I use E:\DATA\Project as source or target


Can you describe again the exact problem you are seeing when using g:\ instead of E:\DATA\Project?
If needed could we send you a special version to debug this issue? thanks

PS is E:\DATA\Project a local folder or a folder on a remote PC?
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com


Last edited by TGRMN Software on Fri Aug 10, 2007 10:33 am; edited 1 time in total
Back to top
TGRMN Software
Site Admin


Joined: 10 Jan 2005
Posts: 8759

PostPosted: Fri Aug 10, 2007 10:32 am    Post subject: Reply with quote

Hi FL

Quote:

1. Create new file X on machine A
2. synch
3. File X on machine B gets new timestamp
4. synch (2nd time, fine is copied again)
5. File X on machine A has same timestamp as machine B


What timestamp file X gets in step 3?
Are you using iBackup or a VPN or a NAS?
thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com
Back to top
KeppelSeghers



Joined: 26 Jul 2007
Posts: 7

PostPosted: Fri Aug 10, 2007 11:39 am    Post subject: Reply with quote

Quote:
Can you describe again the exact problem you are seeing when using g:\ instead of E:\DATA\Project?
is E:\DATA\Project a local folder or a folder on a remote PC?


E:\DATA\PROJECT is a folder on a local server drive.
G:\ is a drive mapping on the server to the local E:\DATA\PROJECT

reason: users are publishing files via a drive mapping on E:\DATA\Project. using Windows they can create 259 chars long filenames.
In order for the server to be able to copy these files, I map the G:\ drive on the server to the same location as the users, so that the server sees exactly the same file lengths as the user.

symptoms:
If G:\ is the target drive, the timestamp on copied files from source to target becomes the actual time.
If G:\ is the source drive, the timestamp on copied files from target to source becomes tes actual time.

next time there is a synch, the files are copied back and the sourcefile gets the timestamp of the copie with the wrong timestamp. => all files change timestamp and I don't have to tell you what happens with the incremental backup...

the 2010a version is working perfectly
the 2012 version has the same problem.

I hope this can help you.

Quote:
If needed could we send you a special version to debug this issue?

PS: If realy required, I can do some tests using a debug version, but I need to be very carefull since this is running in a production environment.

Jan
Quote:
Quote:
Back to top
FL
Guest





PostPosted: Sat Aug 11, 2007 12:24 am    Post subject: Reply with quote

TGRMN Software wrote:
Hi FL

Quote:

1. Create new file X on machine A
2. synch
3. File X on machine B gets new timestamp
4. synch (2nd time, fine is copied again)
5. File X on machine A has same timestamp as machine B


What timestamp file X gets in step 3?
Are you using iBackup or a VPN or a NAS?
thanks


files are getting actual time/date
no iBackup, NAS but using VPN.
Back to top
FL
Guest





PostPosted: Wed Aug 22, 2007 1:05 am    Post subject: Reply with quote

^^
Back to top
Display posts from previous:   
Post new topic   Reply to topic     Forum Index -> Support All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © phpBB Group
Copyright © TGRMN Software. TGRMN Software products: