Data migration via MigGUI - questions with Sync

Question

Due to some issues we encountered (logistics) with file compression/quotas, here's what I'd LIKE to do, but not sure if it can be done:
1) Create a miggui project called like: VOL1
2) But when I go in to select the items to be migrated, I don't want to select the entire volume, but rather specific "top level" directories.
3) Start the migration during business hours
4) Then when we're ready, kick everyone off and do a final "sync" to get the items that were missed (due to being open or whatever) the first time.
The questions:
a) Can I have multiple data migrations within the same project but each one defined as a specific directory? Or will I need to make multiple projects for that?
b) The Sync only relies upon date/timestamp right? But on OES (with NSS) there's like 3 timestamps I think, so which one does it use/compare against?
c) We've seen issues with people's GroupWise Archives where the miggui will see new dates/times in their Archive (index files, etc.) but a Beyond Compare CRC check will show the data is actually the same.

Answer 1

Originally Posted by Ramesh
kjhurni wrote:
> Hi Oza,
>
> A few problems:
>
> 1) You cannot select multiple file systems, so if you only want to
> migrate things one at a time, you have to create multiple projects in
> order to do that.
Multiple File systems? What is your source server? Traditional and NSS
volumes can be dragged and dropped within the same project. On Linux,
NCP and NSS volumes can also be done in the same project. More info on
this please...
>
> 2) The file timestamps are incorrect and off by one hour when the
> miggui runs. The server OS time and date DO show correctly, but the
> times in the miggui in the logs and the files it's actually writing to
> the NSS volumes are all off by one hour.
If your source server is NetWare 5.1 then there was a bug in tsa500.nlm
which caused files on the destination to be off by an hour. The fixed
tsa500.NLM can be found here:
NOVELL: Downloads
If your source is not NetWare 5.1, then some questions:
1. All the files and directory migrated have their timestamp off by 1
hour? So on src if a file has modified time as 10-Oct-2009 12:32 on
destination after migration the file has 10-Oct-2009 11:32?
If yes, then we'll have to investigate more...
2. The miggui logs being off by 1 hour looks like DST (Daylight Savings
Time) settings are not applied on JVM running in your server. Because
miggui uses Java api to get the local time which in-turn gets it from
JVM that uses the server time. So in any case, the time stamps should
not be different, since we uses only local time.
You can perform one check to confirm the DST is applied on JVM or not.
Download TimeTest-20070923.jar from IBM java site,
IBM - Guidance on updating Java SDKs and JREs for Daylight Saving Time (DST) changes
and execute "java -jar TimeTest-20070923.jar" at console and verify with
server time.
Rgds
Ramesh
Multiple File systems meaning when you open the migration utility and click the Add button, an item appears called: File System. You can only have ONE of those per project. What I had wanted was to be able to put multiple "file systems" in the project so that it would do one at a time, so that if we had problems on one, we could re-run just that one item. Instead, I have to create multiple projects with a File System item added that does a specific top-level folder. It works, just a lot more tedious with keeping multiple projects and having to constantly re-authenticate.
Source server is NW 6.5.7
I've got an SR open.
The log files in the miggui filesystem.log are off by one hour (but not on the other two servers we've done). When I looked in Windows Explorer at the file creation times (when it migrated directories and whatnot), those were also off by one hour.
But the system time showed correctly, so that's where we're trying to figure out why and what went wrong.
First Novell tech said it was because we had set hardware clock to Local Time, not UTC (but my other two servers are set to local time and didn't do this).
Just thought it was odd that the system time would show one thing, but the file system would show something different. But it's been escalated to backline so hopefully we'll figure it out.
Tech support was also under the impression that the SYNC operation in miggui did not sync files, only metadata. That would be bad if that's the case.