Backing up VAX/VMS?

Thanks again for the info... Agreed. I'm not going to worry about it. Uh-huh ... yup yup ... thats exactly it (and there's even a label on the column "FREE") ... Foolish me. Looking at the total counts with /FULL everything makes sense now. Main reason I want to do this without adding software etc. is that I've just gotten the system, and I want to preserve the system disk exactly as I received it *before* I go adding/changing/removing things... Good news is that it all worked. I put the drive in my NetBSD VAX and dd'd the content into a file, then FTP'd it over to the PC where I mounted it under SIMH - I could read it just fine, however VMS 5.5 wouldn't boot under SIMh - it reported a whole bunch of bad licenses (not surprising) and crash/dumped almost all the way through the boot process - I tried it a few times trying to "catch" the output with CTRL-S to see what exactly was failing, but I was unsuccessful (I guess I need a slower system for SIMh). Anyway, using VMS 7.2 BACKUP I created a save set from the VMS 5.5 disk which I copied to a CD image with VMS 7.2 stand-alone restore. Then I burned a disk from that with Nero - and amazingly it all works - I can boot the CD on the original system (4000 VLC) and restore the save set to a never-vmsed-before drive and it then boots up and runs! (whew!) I do have one question relating to a difference - see later: Yeah - I tried booting it from a DAT drive once ... I have it on the SYSE boot of my system disk, and also on CD (it's not bad from CD). I read about doing this - but what about the system disk case. You can't boot from an LD disk can you? (I assume the LD doesn't exist until you are booted?) If the system crash-dumps it could wipe out the root of the drive due to the 1G wraparound. I'd really like to be able to use my 1.09G drives as system drives in the 3100's (next closest I have is a few RZ23's (100m). Now my question: I see a difference when I boot the system from the original drive, and the backups - this happens with BOTH the direct drive to drive backup that I origianlly made, and also when restored from the saveset (Both restores boot the same, which is different from the original drive). Basically I'm getting a message from AUTID$SERVER saying that there is an event (security alarms disabled) that does not occur when booting A couple of other messages come out in a slightly different order - I expect this is just due to asynchronous processes during startup, and I have not verified that they always come out in this order... Here is an abbreviated listing of the console output during booting the system: B> Indicates output that occurs on both Old and New drives O> Indicates output that occurs on the Old drive N> Indicates output that occurs on the New drive Most of the N> / O> differences are rearranged messages that I indicated above, however the audit message occurs only on the N>ew drive ... Can you tell me what this means, and what is different about the restored system from the original? I can send you the complete console boot logs if needed. B> VAX/VMS Version V5.5 Major version id = 1 Minor version id = 0 B>%STDRV-I-STARTUP, VMS startup begun at 1-JAN-2000 00:15:43.09 B>The VAX/VMS system is now executing the system startup procedure. B>%SET-I-NEWAUDSRV, identification of new audit server process is 00000048 B>%%%%%%%%%%% OPCOM 1-JAN-2000 00:16:37.16 %%%%%%%%%%% B>Operator _MAGVS8$OPA0: has been enabled, username SYSTEM B>%%%%%%%%%%% OPCOM 1-JAN-2000 00:16:37.31 %%%%%%%%%%% B>Operator status for operator _MAGVS8$OPA0: B>%%%%%%%%%%% OPCOM 1-JAN-2000 00:16:37.59 %%%%%%%%%%% B>Logfile has been initialized by operator _MAGVS8$OPA0: B>%%%%%%%%%%% OPCOM 1-JAN-2000 00:16:37.60 %%%%%%%%%%% B>Operator status for operator MAGVS8::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;354 B>%%%%%%%%%%% OPCOM 1-JAN-2000 00:16:40.33 %%%%%%%%%%% B>Message from user SYSTEM on MAGVS8 B>Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$MAGVS8.LM$JOURNAL) B> %RMS-E-FNF, file not found B> TP server process waiting B>The VAX/VMS system is now executing the site-specific startup commands. B>%RUN-S-PROC_ID, identification of created process is 0000004C B>%%%%%%%%%%% OPCOM 1-JAN-2000 00:16:43.71 %%%%%%%%%%% B>Message from user DECNET on MAGVS8 B>DECnet starting N>%NCP-I-NOINFO, No information in database N>%RUN-S-PROC_ID, identification of created process is 0000004E B>%%%%%%%%%%% OPCOM 1-JAN-2000 00:16:49.54 %%%%%%%%%%% B>Message from user DECNET on MAGVS8 B>DECnet event 4.10, circuit up O>%NCP-I-NOINFO, No information in database O>%RUN-S-PROC_ID, identification of created process is 0000004E O>%MOUNT-F-NOSUCHDEV, no such device available --- This is the additional message I get on the backups --- N>%%%%%%%%%%% OPCOM 1-JAN-2000 00:16:51.87 %%%%%%%%%%% N>Message from user AUDIT$SERVER on MAGVS8 N>Security alarm (SECURITY) and security audit (SECURITY) on MAGVS8, system id: 1632 N>Auditable event: Security audit alarms disabled N>Event time: 1-JAN-2000 00:16:51.77 N>PID: 00000043 N>Username: SYSTEM N>Auditing flags: ACL,MOUNT,AUTHORIZATION,INSTALL N> BREAKIN: (DIALUP,LOCAL,REMOTE,NETWORK,DETACHED) N> LOGIN: (BATCH,DIALUP,LOCAL,REMOTE,NETWORK,SUBPROCESS, N> DETACHED) N> LOGFAIL: (BATCH,DIALUP,LOCAL,REMOTE,NETWORK,SUBPROCESS, N> DETACHED) N> LOGOUT: (BATCH,DIALUP,LOCAL,REMOTE,NETWORK,SUBPROCESS, N> DETACHED) N> FAILURE: (READ,WRITE,EXECUTE,DELETE,CONTROL) N> SUCCESS: (READ,WRITE,EXECUTE,DELETE,CONTROL) N> SYSPRV: (READ,WRITE,EXECUTE,DELETE,CONTROL) N> BYPASS: (READ,WRITE,EXECUTE,DELETE,CONTROL) N> GRPPRV: (READ,WRITE,EXECUTE,DELETE,CONTROL) N> READALL: (READ,WRITE,EXECUTE,DELETE,CONTROL) O>%MOUNT-F-NOSUCHDEV, no such device available B>*** Start Configure VCP300 KL- May /93 *** B>%RUN-S-PROC_ID, identification of created process is 0000004F B> LAT Control Program B>%SYSTEM-W-NOSUCHDEV, no such device available B>*** Done Configure VCP300 KL- May /93 *** B>%SET-I-INTSET, login interactive limit = 64, current interactive value = 0 B> 1-JAN-2000 00:17:06 B>%RUN-S-PROC_ID, identification of created process is 00000051 B> SYSTEM job terminated at 1-JAN-2000 00:17:33.82 B> Accounting information: -- The I/O counts, page faults etc. are slightly different Thanks again. Dave -- dave06a (at) Dave Dunfield dunfield (dot) Firmware development services & tools: www.dunfield.com com Collector of vintage computing equipment: http://www.classiccmp.org/dunfield/index.html