This document describes setting up NT and D3 to do a backup in D3 first to a file, then an NT backup to tape. Backups can still be done within the D3 environment only, but since that only backs up what is in D3 that is not going to work. Also, NT backup skips files that are in use so the D3 backup has to complete before the NT backup starts or else the file will not be backed up. All other programs and files on the server should be closed when a backup is run.

Setup the Iomega Drive

• Connect Iomega drive to server via USB cable (drive should load automatically and will appear as CD Drive)
• Place driver CD in CD Rom drive and once menu appears, click Automatic Install
• Accept Agreement and click Continue
• Exit the Register Online option and once D3 is shutdown then click Shutdown Now in menu
• Once Server is rebooted, click YES to confirm the device in windows then OK, OK
• Close Iomega Web Site and click Advanced Setup on the Iomega Backup Program window
• Check Turn Off and uncheck Put In Startup Tray then click OK

Setup the REV Disk

• Insert the disk into the Iomega drive and it should auto load
• Delete AUTORUN.INF on the disk and create a folder on disk called BACKUP
• Close Window and Eject the disk and then reinsert it into the drive
• If a Window box pops then select Take No Action and Do Every time.
• If not then disk is ready to back up to

Create BACKUP.BAT

• Start > Programs > Accessories > Wordpad
• File > Open,  change File Type to Text Document (txt), browse to C:\tech\Docs\wxp-backup.txt, Open
• Copy the following backup.bat, then New > Text Document, then paste, then Save as C:\backup.bat

mkdir c:\oldlogs

move /y "c:\Documents and Settings\administrator\Local Settings\Application Data\Microsoft\Windows NT\NTbackup\Data\backup*.log" c:\oldlogs

ntbackup backup systemstate C:\ /m normal /l:s /v:yes /f “e:\backup\ntbackup.bks”

copy "c:\Documents and Settings\administrator\Local Settings\Application Data\Microsoft\Windows NT\NTbackup\Data\backup*.log" c:\WINDOWS\BACKUP.LOG /y

C:\PRINTLOG.BAT

NOTE: the following section should be placed at the beginning of the backup.bat by the installer on site.

DEL S:\FS.BACK3

REN S:\FS.BACK2 FS.BACK3

REN S:\FS.BACK1 FS.BACK2

COPY C:\SAVES\FS S:\

REN S:\FS FS.BACK1

DEL C:\SAVES\FS.BACK3

REN C:\SAVES\FS.BACK2 FS.BACK3

REN C:\SAVES\FS.BACK1 FS.BACK2

COPY C:\SAVES\FS C:\SAVES\FS.BACK1

                                                    

Create PRINTLOG.BAT

Now the PRINTLOG.BAT batch file needs to be created.

• Start > Programs > Accessories > Wordpad
• File > Open,  change File Type to Text Document (txt), browse to C:\tech\Docs\D3-Backup.txt, Open
• Copy the following printlog.bat, then New > Text Document, then paste, then Save as C:\printlog.bat

PATH C:\program files\d3\d3programs

D3TCL -c "SP-ASSIGN F0" -c "RUN PM.PROGRAMS,UTIL.PGM, PRINT.BACKUP.LOG C:/WINDOWS (P"

(Change this to the correct sp-assign statement for the printer you want to print to)

This will print a pared down version of the backup log created by NT backup. It will not print the skipped file messages or the directories backed up. It will print a total of directories and skipped files at the end. Also note the forward slash (/) in C:/WINNT. The slash is reversed when running programs in the D3 environment.

Create shortcuts, folders, and files

• Create a shortcut on the desktop for the C:\BACKUP.BAT file, the C:\WINDPWS\BACKUP.LOG file and the C:\PRINTLOG.BAT file. This will allow easy access to these files for support.
• Create a shortcut on the desktop for command prompt to C:\Program Files\D3\D3PROGRAMS (Right click desktop, command line is CMD, save it, right click, properties, shortcut tab, start in: "C:\program files\d3\d3programs" [ " marks are needed ] )
• Create a shortcut to the D3TCL prompt ( right click desktop, new, shortcut, browse to C:\program files\d3\d3programs\D3TCL ).
• Make a directory on the C drive called Saves. (ex: C:\SAVES)
• Make an empty file: C:\WINDOWS\BACKUP.LOG
• In the DM account: Make sure the dev-make command (ex: dev-make -t tape -a "C:\saves\fs,p") is created in the USER-COLDSTART.

Test Backup

Before Registry edits can be performed, a backup must be performed. To run a test backup, go to Start, Programs, Accessories, System Tools, Backup.

You may get a message warning about a new import media. At this screen, check Always allocate this media to Backup if it is compatible, then OK.

Click backup tab, browse to C:\tech\Docs and check the docs folder. Change Backup Destination to the ntbackup folder on the rev drive to click Start Backup, click Advanced, check Verify data after backup, click OK, click Start Backup, close all applets when done

Registry Edits

• Start Registry Editor (Regedt32.exe).
• To skip open files, you will have to change some information in the Registry.  The following was clipped from a Microsoft knowledge base article:

You can modify the following registry entries to adjust the skipped files options:

HKey_current_user\Software\Microsoft\Ntbackup\User Interface

   Name:            Skip open files

   Type:            REG_SZ

   Default:         0

   Definition:

   0 = do not skip, wait

   1 = skip files that are opened unreadable

   2 = wait on open files for "Wait time"

   Name:            Wait time

   Type:            REG_SZ

   Data:            30

   Definition:

   Maximum time (seconds) to wait for open files. Default is 30 seconds.

   Maximum value is 65535

Recommended method: Set "Skip open files" to 1 and "Wait time" to 1

Task Scheduling

NOTE: Before you can edit the registry settings a backup using NTBACKUP and Task Scheduling must be done first.

• Open a command prompt and type the following:                AT  (time + 3 minutes) C:\BACKUP.BAT /interactive

This Last Section Must Be Done After Data Is Loaded

Please create and verify that the following steps are complete.

3. Make a directory on the D drive called Saves. (ex: D:\SAVES)

4. In the DM account: Make sure the dev-make command (ex: dev-make -t tape -a "d:\saves\fs,p") is created in the USER-COLDSTART.

5. Type in T-STAT to verify the device# for the T-SELECT command.

6. At TCL in the Account that you are doing the D3 backup from (usually PM), type: U MASTER FS.TAPE.COMMAND and enter the T-SELECT command with the proper unit number.

7. At TCL in the Account that you are doing the D3 backup from (usually PM), type: U MASTER VERIFY.CMD and enter the verify command (ex: T-VERIFY (TP99).

MASTER NTBACKUP.CMD

1. Create a MASTER file entry called NTBACKUP.CMD. This will execute automatically as a Scheduling Job as soon as the D3 backup is done. The only drawback is that if the D3 backup fails and gets stuck then the NT backup will not execute either.
2. At TCL in the Account that you are doing the D3 backup from (usually PM).
3. U MASTER NTBACKUP.CMD and put the path and batch file name of the NT backup. (Ex. C:\BACKUP.BAT).

The file-save program will automatically issue the command: "AT time+90seconds C:\BACKUP.BAT /interactive". This will cause the batch file to execute in 90 seconds from the current time the file-save finished.

Either way, you will get TWO file-save reports. One from D3 and one from NT backup.

YOU ARE NOT DONE UNTIL YOU TEST THE ENTIRE BACKUP PROCESS.

Run the file save program from the system menu in PM. Watch the entire process and look for any error messages. After it is done you will have two printouts. Look for any error messages on those printouts.

If you do not get two printouts then it is NOT working so you will have to fix something.

If you can seem to make it work, do a manual NT Backup to make sure you get a tape backup. Do that in: Start -> Programs -> Administrative Tools -> Backup.

Troubleshooting

If you get a "TUSB6250 Boot Device detected" error when you connect the Iomega® REV® USB drive?

Do the following steps to resolve this issue:

1. Close all TUSB6250 Boot Device installation screens.
2. Leave the USB cable connected to the computer and the REV drive.
3. Disconnect the power cable from the back of the REV drive (Leave the power cable plugged into the wall outlet).
4. Reconnect the power cable into the back of the REV drive. 
5. Your REV drive should now be correctly detected as a REV USB drive.

If you get a blue screen/stop error:

Check your firmware version. You might have to upgrade it along with the REV software.

To check your firmware version go to Start Programs then Iomega, click Rev System Software and Rev Diagnostics.

The current firmware version is 22.b (9/27/06). It is in \\Perf2k\Files\tech\Iomega\iom_rev_fw-w32-x86-22b.exe

    Note: A higher firmware version might not necessarily be the newest. Please check Iomega.com and click Support then click REV and find the correct model then click your OS and you should see the latest firmware and software versions on their website.

To upgrade, the firmware first make sure to remove all media then click on the firmware executable file then click setup and

follow the instructions. Once the firmware is upgraded, check the current version in the Rev Diagnostics.

The current Rev software version is 41139 (9/27/06). It is in \\Perf2k\Files\Tech\Iomega\

rev_system_software-en-w32-x8641139.exe

Both the software and firmware should be upgraded together.