Corrupted Email Archive ?
We have a 3GB email backup file that we're trying to migrate to another server. The imsrestore command restores the first email, then exits:
$ du -sh 060808B.email
2.9G060808B.email
$ cat 060808B.email | /usr/iplanet/server5/bin/msg/store/bin/imsrestore -f-
--
Tape Version : 2
Backup Date: Tue, 08 Aug 2006 10:12:22
Message Store : MYMAIL
Block factor : 20
--
/MYMAIL/groupB
/MYMAIL/groupB/b118dms
/MYMAIL/groupB/b118dms/INBOX
/MYMAIL/groupB/b118dms/INBOX/847
The log seems to indicate that there is an errant value somewhere:
[14/Aug/2006:09:04:59 -0600] Portal1B stored[694]: Store Notice: checkpoint peruser started
[14/Aug/2006:09:04:59 -0600] Portal1B stored[694]: Store Notice: checkpoint peruser finished
[14/Aug/2006:09:35:40 -0600] Portal1B /usr/iplanet/server5/bin/msg/store/bin/imsrestore[2745]: Store Error: Error in fstat: Value too large for defined data type
[14/Aug/2006:09:36:50 -0600] Portal1B /usr/iplanet/server5/bin/msg/store/bin/imsrestore[2812]: Store Error: Error in fstat: Value too large for defined data type
We are using iPlanet Messaging Server 5.2 (a component of the Luminis portal) and we are migrating from Windows to Solaris 9. Any suggestions would be greatly appreciated. Thank you.
# 1
What was the command used to create the backup?Also, syntax on your restore....imsrestore -f-should beimsrestore -f -That's "dash 'f' space dash"
# 2
We tried using "imsrestore -f -" and the results were the same. We'll get the command the admin used to create the backup file and update this thread.
# 3
What version of Messaging Server? there are at least 20 different versions of Messaging 5.2. Some work has certainly been done in the imsrestore area, so knowing how old what you have can be important.
Also, you really truly should be looking at moving to 6.2, by now. 5.2 is on the road for End Of Support Life.
# 4
Unfortunately, upgrading is not currently an option; the Messaging Server is bundled as a component of SCT's Luminis portal.
Both the source (Win 2K server) and destination (Solaris 9) Messaging Server are 5.2p2.
The admin sent us the scripts they use to take the backup. They create separate backup files for each group:
imsbackup -f k:\backups\email\current\group%%2.email
%%2 is the second argument to the batch script (traverses from A to Z).
Is the 2GB file limit a problem on Windows?
# 5
Yes, the 2 gig limit is for all os's.Your backup needs also to be done with the -f - flag in order to be able to restore it.
# 6
Hi,
I just tried backing up a single 3GB mailbox (not a group) on an iMS5.2hf2.07 Win2K install and restoring to a iMS5.2hf2.12 Solaris 9 install and this worked fine.
How much manages to get restored before the error you mentioned occurs?
Have you tried backing up/restoring individual accounts rather then a large group backup - does this work?
Are you able to upgrade messaging server to a later hotfix release?
imsbackup -f - doesn't work under windows currently (bug #6449794 - supposed to be fixed in the upcoming iMS5.2hf2.14 patch - contact sun support for a copy).
The 2GB file limit doesn't appear to be a problem for windows specifically which is why you don't need to use the imsbackup -f - option under windows to back up more then 2GB. The issue may be more to do with the backup under one OS and restore under another.
Cheers,
Shane.
# 7
Not to argue with you, Shane, but . . .There were some problems with early imsbackup on windows. I vaguely remember seeing these problems. I suggest contacting Support for a current Windows hotfix (and, for Unix, too).Alternatively, use MoveUser to migrate users......
# 8
Imsrestore completes one email, then quits:
$ cat 060808B.email | /usr/iplanet/server5/bin/msg/store/bin/imsrestore -f -
--
Tape Version : 2
Backup Date: Tue, 08 Aug 2006 10:12:22
Message Store : MYMAIL
Block factor : 20
--
/MYMAIL/groupB
/MYMAIL/groupB/b118dms
/MYMAIL/groupB/b118dms/INBOX
/MYMAIL/groupB/b118dms/INBOX/847
Backing up and restoring a single user works fine.
Unfortunately, if we apply any hotfixes not specifically supplied by the Luminis Portal vendor, we run the risk of violating the support agreement (I also have a help ticket with them on this).
The imsbackup completes on the Win2K box. I am waiting to hear back from the admin if they've ever restored from it.
# 9
Movemail might take too long. The current production server is in California and the new system is located in Utah. Also, there is about 70GB of email to copy.
# 10
You may need to apply a current hotfix before it's going to work. properly.
# 11
Hi,
I tried backing up a group (rather then an individual user) on W2K and restoring on Solaris and this also worked fine.
At this point you seem to have several options:
1. Use movemail (recommend upgrading if possible)
2. Use imsbackup but only do one user at a time
3. Upgrade both systems and see if you can get imsbackup working for backup groups
As Jay quite correctly pointed out, there were imsbackup fixes in later hotfix releases which may be the reason why you cannot currently use the group imsbackup images. Time to push your vender I think.
Good luck.
Shane.
# 12
"movemail"? Not something I'm familiar with.
"MoveUser" is a utility provided with every release of Messaging Server.
Yes, many gigs over a WAN will take a while.
Alternative:
use mboxutil to create a list of all users' folders on the Windows end.
Use mboxutil on the Solaris end, to create those folders, after populating the ldap server.
Do a simple filesystem backup for *.msg (all message files).
Restore to new system.
Run reconstruct -r
enjoy.....
# 13
Yep I meant to say moveuser... *slaps head*
Re: raw backup/restore of .msg files. This is another option but it has the disadvantage of resulting in a loss of all folder/flag information (such as read message status). This would make any migration far from transparent to the end-user but is definitely another option.
Is the cut-over intended to occur over a single night or weekend aka big-bang style?
Cheers,
Shane.
