RMX recovery failed

[keyset6]

As a precaution I brought a UBA backup from site A to my test 9006.3 to build a spare hard drive. For the first time the process failed, during the script the system restarted. Tried this again after formatting the hard drive with STA-TINIT. Before the restarts was:

ERROR ON GET <:URS@@@DD10023>: H'8101
ERROR ON PUT <DS:APSU/RS@@@DD>: H'8004
ERROR ON GET <:URS@@@DD10023>: H'8101
ERROR ON PUT <DS:APSU/RS@@@DD>: H'8004
ERROR ON GET <:URS@@@DD10023>: H'8101
ERROR ON PUT <DS:APSU/RS@@@DD>: H'8004

To be able to do the TINIT I of course had to boot from the ISYAPS in the DAT, but could not. I had another DAT drive which I installed, that was able to load the ISYAPS but not the RMX! I then re-installed the original DAT drive. I recall something about a certain model DAT drive needed to have a DM4L processor to boot from ISYAPS, which I don't have.

I then successfully restored RMX from site B, also a 9006.3 system. I went to the site A to bring back another backup from 2012. I wonder if the backup was bad, or there's some kind of other incompatibility.

Now I'm restoring Unix with the ISYAPS tape from the same system (Site A) I'm attempting to restore RMX from. I don't think it should matter. I believe any Unix version should be compatible with any RMX database, correct? I may the attempt the 2012 backup tomorrow. If this doesn't work I sure don't want to but may have to configure everything manually. I could see just removing everything (Site B's data) could take a good part of a day before reconfiguring the new data. The hard drive does have another system's RMX, with just 2 card slots configured the same.

 

[donb01]

I think the database has to at least be the same version, because both unix and RMX make changes to the database - if one has a database structure that has a "FieldX" in it and the other does not then you are going to get read or write errors.

Just an assumption based on past database work with computers. If you have Database A and client A, and then you add a client B, if there have been any changes in Database B (which needs client B) then you are going to have problems.

 

[keyset6]

I tried the other backup, the ISYAPS from the site I was trying to restore from, and my 2nd spare hard drive - same thing happened. The process once again made the drive un-bootable so I had to restore the hard drive with another system's data. I finally deleted all the data and cards, now I'm in the process of manually adding everything. For Rolmphones %ADDSTN from EMML can actually save some time after a couple Rolmphones are configured. Haven't used that in years. For analogs at least all the config is the same, do after ADD-SCSU, then station # and pen I have a string ready in a Procomm Meta file for the rest.

When I built the hard drive with another site's data the ISYAPS I used had an old version of Unix that didn't have Direct Amo. I then was able to do a Recovery (or maybe upgrade? not in the office to check my notes) with a newer version that had Direct Amo. So, as long as the ISYAP is 9006.3 SMR something - it seems any RMX should be able to be loaded as long as it's also 9006.3.

 

[donb01]

I used to really like %addstn and %chastn to change device type. They took them away in 6.5 when they started pushing LC-Win, and LC-Win had no equivalent, and then people must have griped enough because they added a change device type function back in to LC-Win 4 for 6.6. No matter how great they made LC-Win there are still things you need to do in Direct AMO that it is stupid about, and some things, like checking Backup log. you still need ProComm for. Even in the HP4K, which has the Assistant that is really nice to use for some things, they still have expert mode for us command line junkies, and if you know how to use the macro functions it can really kick butt when you need to add a whole lot of stations or make mass changes.

 

[keyset6]

For the last week I've been creating the database for the PBX I was trying to make a backup drive from the DAT (Site A). Took a while just to delete site B's data. Some of the DPLN I could leave as is. I'm almost done creating Site A's database. As you mentioned I used Direct Amo and Meta Keys in Procomm for creating analog exts., one fortunate thing is there's no LCOS restrictions or differences in site A, so the string after ADD-SCSU, the station and PEN can be the same except for a few ringdown phones.

Question re: REGEN: - I don't see a practical way to save all the commands. I thought DEST would be manageable since the string was all in one line, but it's very time consuming to get it into a Procomm .was format so it could be compiled as a script. Is there some kind od utility to capture and re-send REG-LDPLN for example? I ended up doing that manually, one slight advantage is the system will ened up with a basic simplified routing plan since the site doesn't have any dial restrictions based on area codes.

 

[donb01]

I use REGEN on the 4000 all the time and find it quite awesome to work with for creating stations, single or bulk, and CFW information. Most of the rest I tend to do using the assistant.

I know REGEN is on the 9006, but I never used it on there. If it worked I would assume RENEN-LDPLN is how it would happen.

Here is what I did for one on mine:

<regen-ldpln

PLAN = 35
REGEN-LDPLN:35;
H500: AMO LDPLN STARTED
ADD-LDPLN:0,
15,
9&686&9855,3
,0,2,NAT,ISDN;
CHA-LDPLN:35,0,,N;
AMO-LDPLN-111 AMO LCR DIALING PLAN FOR THE SWITCHING UNIT
REGENERATE COMPLETED;

The thing I notice on the 9006 is that it looks like it actually does two commands - it's hard to figure out, but my guess is if you do

REGEN-LDPLN on the one you want to copy over, and use the CAPTURE function of ProComm to capture all that, then all you have to do is copy the lines into ProComm on the new system to add the entries.

Problem here is it looks all nice and pretty when you do the regen, but what you don't see here is that after you do the ADD you will have to wait for switch responses, and then the CHA needs to come and you have to wait for switch responses. It's going to be hard to put that in a script. On the 4000 it gives you one line of code, you paste it on the command line, edit as needed (for phones) and hit Enter.

So depending on how much effort you want to make it probably IS possible!

 

[keyset6]

The trouble with for LDPLN for example it's not one continuous string on one line going across. DEST is, but even with that you'd need to add: transmit "(command)" then waitfor, or waitquiet 1 or 2 if compiling a Procomm script for each entry. It has to line up just right for the script to compile. I did that with about 10 DESTs but it took quite a while to get it right. I've got about 3/4 of DEST done manually. So, copying config via REGEN from another system to create a backup hard drive on another isn't practical for what I have. I can see though, where it would be useful to add stations for MAC purposes.

 

[keyset6]

Figures I'd think of this now, I'm just about done. On my home pc I have a file renaming program I bought for arranging MP3 files in a certain order on CDs and flash memory. For that I just have it add 1- , 2-, 3- and so on before each file so they'll play in that order. That may have been able to insert the commands required to compile a script. Probably a lot of formatting would have to be done to get it right.