Data Recovery Scenarios

Transcription

1 Appendix A Data Recovery Scenarios CSS GROUP, INC IH 10 West, Suite 611 San Antonio, Texas Phone: Fax: info@ cssgroup.net

2 : Repair of Datafile Without Lost Time. Scenario 1: DataManager datafile (Datafile 1) must be taken down for repair or datafile maintenance. DataFile 1 DataFile 2 Trash While all users are logged out, allow one last full replication to take place. Replace DataFile 1 with DataFile 2. Trash Datafile 1. New DataFile 1 Replication New DC DataFile

3 : Repair of Datafile Without Lost Time. Scenario 2: datafile (DataFile 2) must be taken down for repair or datafile maintenance. DataFile 1 DataFile 2 Trash DataFile 2. Trash Replication DataFile 1 New DataFile 2 Shut down DataManager and replace DataFile 2 with DataFile 1. Restart DataManager.

4 : Repair of Datafile Without Lost Time. Scenario 3: DataManager and datafiles must be taken down for repair or datafile maintenance. DataFile 1 DataFile 2 Run maintenance tools on DataFile 2. While all users are logged out, allow last replication to be completed. DataFile 1 Replication Repaired DataFile 2 Trash Replace DataFile 1 with DataFile 2. Trash DataFile 1.

5 : Repair of Datafile Without Lost Time. Scenario 4: User mistakenly deletes a large number of Jobs/records from DataManager. DataFile 1 DataFile 2 Backup Trash Because runs at regularly set intervals, if the user deletes a large number of records, both DataFile 1 and DataFile 2 will most likely be affected. The user will have to take the most recent backup of the datafile prior to the mass deletion, replace DataFile 1, and use that as the primary datafile. Replication New DataFile 1 New DataFile 2 Once both DataFile 1 and DataFile 2 are replaced with the backup datafile, the original DataFile 1 and DataFile 2 should be trashed.

6 Appendix B Error Codes CSS GROUP, INC IH 10 West, Suite 611 San Antonio, Texas Phone: Fax: info@ cssgroup.net

7 Error Codes 4D Backup Errors Error Error Message Text - Commentary 1000 An error occurred. An error occurred during the backup Wrong project. The project does not correspond to the open database Not a project. The specified document is not a 4D Backup Project Nothing to back up. No files were specified for the backup Wrong enclosure. This file cannot be added because it is a data, structure, or log file Duplicate enclosure. This file already exists in the list of enclosures Too many enclosures. This file cannot be added because the maximum number of enclosures has been reached This is not an enclosure. Impossible to remove this file from the list of enclosures; it is not in the list Backup already started. The backup process has already been created Backup not started. The backup process has not been created. Call BK Begin Full Backup or BK Begin Mirror Update Wrong destination. The destination volume cannot be found or the access path has been modified Can t launch the backup. Verify that you have correctly installed 4D Backup A manual backup is needed to create a new backup segment. This message is returned when you backup with scheduler or us 4D Backup commands and a new backup segment is needed.

8 4D Backup Errors Cont d D Backup is not installed in 4D Server. You should install 4D Backup in the structure file and in the 4D Server application No log file. The database is working without a log file. 101 The disk is probably damaged. Verify this media with a disk recovery utility. 102 Initialization failed. Your floppy disk is damaged: Try another one. 103 Backup failed. Your database has not been backed up. 104 Backup completed successfully. Backup has completed successfully. 105 Could not create file. This file may already exist or the folder is locked. 106 Module is damaged. Check for viruses and reinstall the backup module. 108 Backup aborted. The backup process has stopped. Some data may not have been saved. 109 Invalid license number. The backup module CANNOT be used on this server. 111 Warning! This disk also contains the database (or a data segment). You should not store the database and its backup copy on the same disk. You may lose both! 112 This is one the database s files. You cannot enclose the data file or structure file of the database you want to back up. 113 This version of 4D is too old. The minimum version of 4D required by 4D Backup is The file 4D Prefs could not be opened. This file is necessary for serialization. Check for its availablity. 115 The project file can t be used. It doesn t match this database, or it has been damaged.

9 4D Backup Errors Cont d 117 Backup cannot be launched. Make sure that installation was done properly, and that no backup is currently in progress on another 4D Client or 4D Server. 119 Can t open the enclosure. This file may be in use. You should back it up later. 120 Can t initialize disk. Some files might be in use on this disk, or file sharing is active 121 Backup can t execute correctly. Quit 4D, then verify the disks and your network. 129 This is not the previously selected volume. You must select the icon of the disk where you wish to back up your database D Backup is not installed in 4D Server. Verify that the Mac4DX or WIN4DX folder contain the 4D Backup module. Use the installer from the stand alone application 4D Backup to install the backup module in 4D Server. System Error Codes Error Error Message Text - Commentary -34 The disk is full. -36 I/O error. Check the disk with Dick Doctor. -43 File not found. -44 Volume is locked by a hardware setting. -48 Duplicate file name. -49 File already open with write permission Not enough room in heap zone.

10 Error Codes Error Error Message Text - Commentary D Open read/write/bind error DM Structure and DCN structure do not match based on table counts Unable to match versions Unknown user or invalid password Maximum number of users connected D engine version not compatible with 4D Server version Other connection problem-likely network related Server not found -601 Failed to initialize TCP/IP TCP/IP not available Error sending notification(s) No users set up for notification No host IP/Name set for notification.