forums › forums › Monyog › Monyog Deployment › Migrate From Monyog 3.65 -> 4.02
- This topic is empty.
-
AuthorPosts
-
-
October 19, 2010 at 8:53 pm #12133everlast73Member
Is there any way to migrate your settings from a Windows install of MONyog 3.65 to a Linux install of MONyog 4.02?
Thanks.
-
October 20, 2010 at 4:37 am #31434ShalmaliMember
Please copy the contents of data folder from the C:Documents and SettingsAll UsersApplication DataWebyogMONyogdata on your windows and paste it in /usr/local/MONyog/data on your linux machine. Restart MONyog service.
-
October 20, 2010 at 4:34 pm #31435everlast73Member'Shalmali' wrote:
Please copy the contents of data folder from the C:Documents and SettingsAll UsersApplication DataWebyogMONyogdata on your windows and paste it in /usr/local/MONyog/data on your linux machine. Restart MONyog service.
We copied all directories from the Windows server to the Linux server, the registered servers do not display on the Linux system. Was there a step that was left out?
-
October 20, 2010 at 5:43 pm #31436peterlaursenParticipant
Where did you copy to? You will need to replace the MONyog /data folder (or the subfolders inside it) on the Linux system.
Please specify the name of the folder(s) you copied and the exact path to where you copied.
Refer documentation:
Here are the default paths where you can find the data collected by MONyog for the first connection created by MONyog.
- In windows systems:
XP or older: C:Documents and SettingsAll UsersApplication DataWebyogMONyogdata 001
Vista and newer: C:ProgramDataWebyogMONyogData 001
- In Linux systems:
RPM: /usr/local/MONyog/data/0001
Tar: In the same directory where MONyog was 'untarred'.
When using the GUI to register a server a folder for each connection is created automatically. Folders are named with a 4-digit numerical name ('0001', '0002' etc.). Any number upto 9999 is valid. At start-up MONyog will check for such and use them. So if you simply need to duplicate a connection you can simply copy the '0002' folder for instance and rename to '0003' or whatever (MONyog must be stopped while doing).
-
October 20, 2010 at 5:56 pm #31437everlast73Member
Peter –
I moved the contents of C:Documents and SettingsAll UsersApplication DataWebyogMONyogData from my Windows system to /usr/local/MONyog/data. After the move, I restarted the MONyogd service on the Linux server. This is a list of the directory structure:
[root@monyog MONyog]# ls -lR
.:
total 120
drwxr-xr-x 2 root root 4096 Oct 19 15:29 bin
-rwS
1 root root 17408 Oct 19 15:30 Counters.defdrwxr-xr-x 15 root root 4096 Oct 20 12:30 data
-rwS
1 root root 135 Oct 19 15:35 MONyog.ini-rwS
1 root root 2394 Oct 20 12:29 MONyog.log-rw-r–r– 1 root root 9174 Sep 21 10:27 MONyog.lua
-rw-r–r– 1 root root 3704 Sep 21 10:27 MONyog.mib
-rwS
1 root root 14336 Oct 20 12:31 preferences.config-rw-r–r– 1 root root 4337 Sep 21 10:27 README
drwxr-xr-x 2 root root 4096 Oct 19 15:29 res
./bin:
total 22016
-rwxr-xr-x 1 root root 1277 Sep 21 10:27 MONyog
-rwxr-xr-x 1 root root 22500896 Sep 21 10:27 MONyog-bin
./data:
total 104
drwxrwxr-x 2 root root 4096 Oct 20 12:26 0001
drwxrwxr-x 2 root root 4096 Oct 20 12:26 0002
drwxrwxr-x 2 root root 4096 Oct 20 12:26 0003
drwxrwxr-x 2 root root 4096 Oct 20 12:26 0004
drwxrwxr-x 2 root root 4096 Oct 20 12:27 0005
drwxrwxr-x 2 root root 4096 Oct 20 12:27 0006
drwxrwxr-x 2 root root 4096 Oct 20 12:27 0007
drwxrwxr-x 2 root root 4096 Oct 20 12:27 0008
drwxrwxr-x 2 root root 4096 Oct 20 12:27 0009
drwxrwxr-x 2 root root 4096 Oct 20 12:27 0010
drwxrwxr-x 2 root root 4096 Oct 20 12:28 0011
drwxrwxr-x 2 root root 4096 Oct 20 12:28 0012
drwxrwxr-x 2 root root 4096 Oct 20 12:28 0013
./data/0001:
total 1700472
-rw-rw-r– 1 root root 16384 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 189624320 Oct 20 10:54 mysql.data
-rw-rw-r– 1 root root 1515220977 Oct 20 10:47 sniffer.data
-rw-rw-r– 1 root root 34684068 Oct 20 10:57 system.data
./data/0002:
total 136
-rw-rw-r– 1 root root 3072 Jul 30 2009 connection.data
-rw-rw-r– 1 root root 0 Jul 30 2009 mysql.data
-rw-rw-r– 1 root root 114688 Jan 13 2010 sniffer.data
-rw-rw-r– 1 root root 0 Jul 30 2009 system.data
./data/0003:
total 31948
-rw-rw-r– 1 root root 16382 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 32647952 Oct 20 10:53 mysql.data
-rw-rw-r– 1 root root 0 Dec 11 2009 system.data
./data/0004:
total 15040
-rw-rw-r– 1 root root 13308 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 13151977 Oct 20 10:53 mysql.data
-rw-rw-r– 1 root root 2195411 Oct 20 10:53 system.data
./data/0005:
total 28340
-rw-rw-r– 1 root root 16382 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 28956962 Oct 20 10:52 mysql.data
-rw-rw-r– 1 root root 0 Aug 24 2009 system.data
./data/0006:
total 20004
-rw-rw-r– 1 root root 13312 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 14204749 Oct 20 10:53 mysql.data
-rw-rw-r– 1 root root 6217538 Oct 20 10:53 system.data
./data/0007:
total 1560
-rw-rw-r– 1 root root 13312 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 1564618 Oct 20 10:53 mysql.data
-rw-rw-r– 1 root root 0 Mar 30 2010 system.data
./data/0008:
total 30192
-rw-rw-r– 1 root root 16382 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 25967153 Oct 20 10:53 mysql.data
-rw-rw-r– 1 root root 4874013 Oct 20 10:54 system.data
./data/0009:
total 30192
-rw-rw-r– 1 root root 16384 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 25295667 Oct 20 10:54 mysql.data
-rw-rw-r– 1 root root 3072 Jan 13 2010 sniffer.data
-rw-rw-r– 1 root root 5537658 Oct 20 10:53 system.data
./data/0010:
total 75784
-rw-rw-r– 1 root root 16384 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 64806233 Oct 20 10:54 mysql.data
-rw-rw-r– 1 root root 3072 Jan 13 2010 sniffer.data
-rw-rw-r– 1 root root 12668685 Oct 20 10:54 system.data
./data/0011:
total 39792
-rw-rw-r– 1 root root 16384 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 33703447 Oct 20 10:53 mysql.data
-rw-rw-r– 1 root root 12288 Jan 13 2010 sniffer.data
-rw-rw-r– 1 root root 6942720 Oct 20 10:52 system.data
./data/0012:
total 12312
-rw-rw-r– 1 root root 13310 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 6405670 Oct 20 10:52 mysql.data
-rw-rw-r– 1 root root 6147733 Oct 20 10:52 system.data
./data/0013:
total 18656
-rw-rw-r– 1 root root 13312 Oct 19 16:49 connection.data
-rw-rw-r– 1 root root 16616424 Oct 20 10:51 mysql.data
-rw-rw-r– 1 root root 2432814 Oct 20 10:50 system.data
./res:
total 19212
-rw-r–r– 1 root root 292864 Sep 21 10:27 Counters.def
-rw-r–r– 1 root root 19341312 Sep 21 10:27 MONyog.res
Do I need to reregister the servers in the new system?
-
October 21, 2010 at 5:46 am #31438MaheshMember
Do I need to reregister the servers in the new system?
— There is no need to re-register server if you are copying from older version to newer version of MONyog.
We tried at our end — Migration of v3.65 /data/ folder from Windows to Linux where MONyog v4.02 is running, it displays registered servers in Linux system.
BTW: Source — Windows XP and Target – CentOS 5.5(64 bit).
To reproduce this issue we need some information mentioned below:
1) Exact Windows and Linux version ?
2) Zip and attach MONyog.log file from MONyog running in Linux (/usr/local/MONyog/MONyog.log)
-
-
AuthorPosts
- You must be logged in to reply to this topic.