crobison Absent Member.
Absent Member.
515 views

Migracion of postoffice from SLES to SLES with dbcopy

I tried using the scp to migrate the domain and postoffice from SLES to SLES, but you have to down all the services and if the size of the domain and postoffice is large it takes many hours. I want to try dbcopy, because this way I can migrate with the services up, but I would like to know what is the best way to do this.. Mounting the directory from the remote system and migrating the domain and postoffice to the directory? using what nfs or sshfs?
Labels (1)
0 Likes
7 Replies
Micro Focus Expert
Micro Focus Expert

Re: Migracion of postoffice from SLES to SLES with dbcopy

Hi,

Perhaps this TID is helpful to you: https://www.novell.com/support/kb/doc.php?id=7010760

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
crobison Absent Member.
Absent Member.

Re: Migracion of postoffice from SLES to SLES with dbcopy

laurabuckley;2402256 wrote:
Hi,

Perhaps this TID is helpful to you: https://www.novell.com/support/kb/doc.php?id=7010760

Cheers,


Unfortunately it demonstrates the use of nss, cifs, but not from linux to linux...

thxs..
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Migracion of postoffice from SLES to SLES with dbcopy

Hi,

My apologies for sending you on a wild goose chase.

When doing pure Linux to Linux you could use rsync to do the move as there is no real advantage to using dbcopy in this case (my opinion!).

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
crobison Absent Member.
Absent Member.

Re: Migracion of postoffice from SLES to SLES with dbcopy

laurabuckley;2402485 wrote:
Hi,

My apologies for sending you on a wild goose chase.

When doing pure Linux to Linux you could use rsync to do the move as there is no real advantage to using dbcopy in this case (my opinion!).

Cheers,



The reason I wanted to use dbopy is to copy the postoffice and domain on line, was because the postoffice is so big... Do you have any link on how to use rsync to do this?
0 Likes
Knowledge Partner
Knowledge Partner

Re: Migracion of postoffice from SLES to SLES with dbcopy

In article <crobison.7160rz@no-mx.forums.microfocus.com>, Crobison wrote:
> The reason I wanted to use dbopy is to copy the postoffice and domain on
> line, was because the postoffice is so big... Do you have any link on
> how to use rsync to do this?


Rsync is a client/server file sync system. SLES comes with it, and it
appears to be installed by default. You have to configure the server side
on the destination, then on the source side (which can be the same box as
the destination) craft the fairly simple command to do the sync. A manual
run started at the beginning of a long slow time(weekend) followed by
scheduled (cron) daily runs while.
https://en.wikipedia.org/wiki/Rsync
https://www.digitalocean.com/community/tutorials/how-to-use-rsync-to-
sync-local-and-remote-directories-on-a-vps

basically rsync ends up being about a similar level of function and effort
of dbcopy, but they differ sufficiently that they make a great combination
for backing up your GW system while it is live.

Dbcopy makes sure the databases are copied intact, but doesn't clean up
deleted files
rsync syncs file deletes nicely, but doesn't make sure the database files
are internally consistant.
For a neat script that does the two nicely, see the 8th post in
https://forums.novell.com/showthread.php/455580-dbcopy-restore-question

For just a migration, the last run of either requires the agents to be
down anyways to not miss any mail happenings in that time frame, which
gives rsync a leg up.

Once you have a mounted remote file system for dbcopy to work, rsync can
be run totally that source server as both server and client.

As for nfs vs sshfs, nfs comes with SLES and has been around for ages,
sshfs doesn't as far as I can see and I hadn't heard about it until now.
'Guess' which has better support options.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
crobison Absent Member.
Absent Member.

Re: Migracion of postoffice from SLES to SLES with dbcopy

This is the plan I have conjured up... Setup the nfs server service on the main email server with the corresponding directory of the gwpo and gwdom, on the destination server use nfs client, connect and setup local directory mounting the gwpo and gwdom locally. Then run dbcopy to the local directory where the postoffice and domain will be placed...

nitial copy & Incremental copy commands:
./dbcopy -m -k -p -w -t 10 -f /mnt/nwserver1/mail/po1 /media/nss/PO1VL/po1
Final PO Copy command:
./dbcopy -m -k -p -w -t 10 -s /mnt/nwserver1/mail/po1 /media/nss/PO1VL/po1

How does this plan sound?
0 Likes
Knowledge Partner
Knowledge Partner

Re: Migracion of postoffice from SLES to SLES with dbcopy

In article <crobison.71exlz@no-mx.forums.microfocus.com>, Crobison
wrote:
> This is the plan I have conjured up...
> ....
> Initial copy & Incremental copy commands:


that should be the initial only, the second command can be used for
all your incrimentals and the final one when the POA agent is down.

Otherwise over all looks good on a quick look by me.



Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.