MO/CF Backup taking unusually longer time 1

[Ademat]

Hello,

I tried to do CF backup but it's taking unusually longer time. The estimated time for the backup was to be 02:14:43. After about 30:00:00, i decided to cancel the backup. Yet, the canceling process has taken another 40hours and has not completed. Please advise.

HBR Status: Backup cancelled

Operation: Backup
Type: mo-rmx
Mode: Auto
Archive: MO-RMX
Start Time: 2015-12-11 02:25:10
Estimated Time: 02:14:43 (+ 78:20:33)
Elapsed Time: 78:30:54
Remaining Time: 00:00:00


I have Hipath4000 V4.

Thanks a lot.

 

[sbcsu]

Hi,
I assume you need to backup the RMX - telephone system part of the HiPath rather than the Unixware 7
If so can you log on via Comwin?

REG-DDSM;

Please paste the result here.

 

[Ademat]

Thank you, sbcsu, for your input. I cannot even do any further backup since the canceling operation has not concluded.

Please see the result below:

REGENERATE-DDSM:;
H500: AMO DDSM STARTED
ADD-DCSM:A1,1,HD,"STDH4";
ADD-DASM:A1,1,3200&992&2400&1120&32767&3200&9868,4096&4096&4096&4096&4096&4096&40
96;
ADD-DLSM:A1,1,E,"DS:";
ADD-DLSM:A1,1,F,"BDA:"&"BD:"&":TMD:"&"AS:"&":AMD:"&"MP:";
ADD-DLSM:A1,1,G,":CGD:";
ADD-DLSM:A1,1,H,"MS:"&"SY:";
ADD-DLSM:A1,1,I,":SCR:";
ADD-DLSM:A1,1,J,":GLA:";
ADD-DLSM:A1,1,K,"IAG:";
ADD-DCSM:A1,6,HD,"CF1G3";
ADD-DASM:A1,6,3200&992&800&1120&12817,4096&4096&4096&4096&4096;
ADD-DLSM:A1,6,E,"DS:";
ADD-DLSM:A1,6,F,"BDA:"&"BD:"&":TMD:"&"AS:"&":AMD:"&"MP:";
ADD-DLSM:A1,6,G,":CGD:";
ADD-DLSM:A1,6,H,"MS:"&"SY:";
ADD-DLSM:A1,6,I,":MOD-SCR:";

AMO-DDSM -111 DISK STATUS
REGENERATE COMPLETED;

 

[Ademat]

...additional information

Below is the progress state as shown on Hipath4K Assistant web page.

Unit Status Estimated Time Elapsed Time Additional Information
AREA_E Cancelling 00:10:21 79:28:24 logfile
AREA_F Waiting 00:59:09 00:00:00 logfile
AREA_G Waiting 00:08:08 00:00:00 logfile
AREA_H Waiting 00:01:32 00:00:00 logfile
DATA Waiting 00:23:27 00:00:00 logfile
UNIX Waiting 00:29:52 00:00:00 logfile
Save Waiting 00:02:14 00:00:00 logfile

 

[sbcsu]

That looks good except the last line which I have as
ADD-DLSM:A1,6,I,":SCR:";
but that might be ok.

You can delete and re-add the CF drive in the UW7 backup and restore as far as I remember and that might be a good thing
to do.
First you can see if it is actually backing up by looking at the hard drive tray to see if IDE2 is flashing.
or log on to Comwin and type
TSN;
in caps to see what AMO's are being used.

If it is still continuing then just remove the CF card.

To backup using the Comwin proceed as follows:
Put in CF
DEA-DSSM:A1,6;
STA-INIT:A1,A1H61;
Y
ACT-DSSM:A1,6;
DEA-DSSM:A1,6;
COPY-DDRSM:A1,1,E&F,6,E&F,N;

 

[Ademat]

Tried to delete the CF backup option in the UW7 HBR but returned the error message "HBR is locked, it cannot be deleted." I checked the HDD tray and IDE2 indicator was constant ON (not flashing) Decided to remove the CF as you suggested, light went off. However, HBR is still showing locked in UW7.

I tried to backup through comwin, but it returned an error message on ACT-DSSM:A1,6; (DEVICE <:A1H61:> IS NOT ACTIVATED BECAUSE OF DSCR ERROR H'2B)

I decided to reboot the UNIX server for a proper reset and do a continous PING to know when it will come back ON. Unfortunately, it's not UP yet. Users can still make calls normally, but the unix is still timing out after about 30min. Is this normal?

Thanks for your help.

 

[sbcsu]

Try putting the CF back in and from the Comwin Initialize it STA-INIT:A1,A1H61;

If you DIS-DDSM;
you should see the Active Load Area
It could be that Area J of the Hard Disk is the active load area.

 

[Ademat]

I did a physical restart of the PBX to get it back to working normally. The UNIX server is up and working now and the active load area is Area E PDS). HBR is now in idle state, ready for the next scheduled backup.

Thank you very much for your help.

 

[sbcsu]

Good that you got it back and running.
If it were me I would not backup to the MO/CF using the Assistant, instead use the Assistant to backup to a 'Backup Server' using SFTP or FTP depending on HiPath versions.
Then in Comwin do a backup of the Areas E&F to the A1H61 etc. make sure that the times of the CRON backups do not conflict with the times of the Assistant backups.
Also do a COPY-DDRSM to the area J of the Hard Disk as a backup area:

EXE-UPDAT:BP,ALL;
EXE-UPDAT:A1,ALL;
DEA-DSSM:A1,1,J;
COPY-DDRSM:A1,1,E,1,J,N;


Here is a default CRON setup
DEL-CRON:1&&256;
ADD-CRON:1,P,0,2,*,*,*,"EXE-UPDAT:BP,ALL;";
ADD-CRON:2,P,10,2,*,*,*,"EXE-UPDAT:A1,ALL;";
ADD-CRON:3,P,20,2,*,*,0,"COPY-DDRSM:A1,1,E&F,6,E&F,N;";
ADD-CRON:4,P,40,2,*,*,0,"COPY-DDRSM:A1,1,E,1,J,N;";
ADD-CRON:5,P,0,3,*,*,*,"STA-DEL:AS:VEGAS/DATEI;";
ADD-CRON:6,P,10,3,*,*,*,"STA-REGEN:CRONAMO,L3190xxZxxxxA00001,N,,,,,,ALL;";
ADD-CRON:7,P,0,0,*,*,*,"DIS-ZAUSL:,Y;";

Replace the 'L3190xxZxxxxA00001' above with your own system number from REG-ANUM;

 

[Ademat]

Great idea!

I've deleted the scheduled MO/CF backup in Assistant and leave only the backup to "Backup Server" using FTP. I now have a scheduled backup (COPY-DDRSM) to Area J and to MO using CRON. I'm also thinking of deleting the daily backup to HDD from Assistant and add it to CRON.

The reason why i'm a bit passionate about backup using Assistant is the fact that i can quickly check the status of backup in History and know if any fails.

Thank you.