Edit D:\app\Administrator\product\11.2.0\dbhome_1\owb\lib\int\oracle\sysman\resources\VtorMsg.class
?? /r 2? 1@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopq contents [[Ljava/lang/Object; <init> ()V Code LineNumberTable getContents ()[[Ljava/lang/Object; <clinit> SourceFile VtorMsg.java 67 45 [Ljava/lang/Object; java/lang/Object 2000 ?his database is not registered in this recovery catalog. You can either register the target database in the recovery catalog by pressing 'Register', or press 'Cancel' to choose a different recovery catalog where the database is registered 2001?t is not possible to uniquely identify the target database in the recovery catalog. Your target database is not in the 'mounted' or 'open' state, and your recovery catalog has multiple entries with the same database name. You can either mount or open the target database, then press 'OK' or if you cannot mount the target database, you can recover the control file, then mount or open the target database, and then press 'OK' 2002 ? recovery catalog does not exist in the user's schema. Either enter a different location where a recovery catalog exists or create a recovery catalog in this user's schema. 2003`Logon is denied to the recovery catalog. Either the user name or password is incorrect, or the user does not exist on the recovery catalog. You can either press 'OK' and enter the correct user name and password in the recovery catalog credentials or create a user (e.g. using Security Manager) and then create a recovery catalog in the user's schema. 2004The recovery catalog cannot be connected to. The recovery catalog database is not open. You can either open the recovery catalog database, press 'Cancel' and then press 'Apply' or 'Create' or press 'Accept' to create a backup configuration without recovery catalog validation. 2005 ?he following database(s) already have an active predefined strategy: Do you wish to remove the active predefined strategy from the job system and create a new one? 2006 _The directory must be fully specified and ended appropriately for the OS (eg. '\', '/' or ']'). 3001 Backup Configuration 3002 &General 3003 Name: 3004 Description: 3005 OA backup configuration is a set of defaults used for backup related operations. 3006 Cha&nnels 3008 Backup set 3009 Image copy 3010 Enter the channel parameters. 3011 -Each channel corresponds to an output device. 3012 Disk 3013 Tape 3014 ?ou must specify a base location where you can copy all the selected files to. The base location must be ended appropriately for the OS (eg. '\', '/' or ']'). 3015 Channel Name: 3016 Format: 3017 <Directory>b_%u_%p_%c 3018 Channel limits... 3100 Parallelism: 3102 <Directory> 3101 Base Location: 3103 ?hoose whether the configuration will be used for backups using an image copy or for backups using a backup set. A backup set can be either on disk or tape, but an image copy can only be on disk. 3019 OK 3020 Cancel 3021 Definition of Channel : {0} 3022 Channels defined : 3023 Specify a name for the channel 3024 &Recovery Catalog 3025 $In the target database's controlfile 3026 In a recovery catalog 3027 3Where do you want backup information to be stored? 3028 Username: 3029 Password: 3030 Service Name: 3031 Parameter Files: 3032 &Backup Set 3033 "Override Recovery Manager defaults 3034 Datafile backups 3038 Archivelog backups 3035 "Maximum files within a backup set. 3036 Maximum size of a backup set. 3037 Backup set size: 3039 Introduction 3040 Backup Wizard : Introduction 3041 ?he Backup Wizard helps you to back up various objects such as the database, datafiles, tablespaces and archivelogs, or to make an image copy of the datafiles and the current controlfile. 3042 ?he wizard will step you through the process of choosing the objects you want to back up or the objects of which you want to make an image copy. Then it will guide you in submitting a backup job through Enterprise Manager to complete the operation. 3043 Configuration 3044 "Choose a predefined configuration: 3045 !Description of the configuration: 3046 View Backup Configuration... 3047 Strategy choice 3048 ODo you want to use a predefined backup strategy or customize your own strategy? 3049 Predefined backup strategy 3050 Customize backup strategy 3051 Backup Selection 3052 &Choose the object you want to back up. 3053 Entire database 3054 =Select the datafiles of which you want to make an image copy: 3055 Tablespaces 3056 Datafiles 3110 Use an image copy 3057 Archivelogs 3058 Available tablespaces: 3059 Available datafiles: 3060 Selected tablespaces: 3061 Selected datafiles: 3062 Select at least one tablespace. 3063 Select at least one datafile. 3064 3065 3066 <Select the tablespace(s) of which you want to take a backup. 3067 :Select the datafile(s) of which you want to take a backup: 3068 Schedule 3069 Backup Options 3070 3Choose a full or incremental level for this backup. 3071 Selected file(s): 3072 Copy file(s) to: 3074 $Base location field can not be empty 3073 M/d/yyyy 3075 3Do you want to include archived logs in the backup? 3076 *Which archived logs do you want to backup? 3077 Archived Logs 3078 Yes, the selected archived logs 3079 Yes, all archived logs 3080 No 3081 Selected archived logs 3082 all archived logs 3083 7Delete the archived logs after they have been backed up 3104 Location 3105 ?pecify a new location for the image copies. You can specify a base location for all files to be copied to or specify a separate location for each file. 3106 Copy all files to base location: 3107 Customize: 3108 ?he current backup configuration is for image copy only. Please either edit the current configuration to use backup set or select another configuration which uses backup set. 3109 ?he current backup configuration is for backup set only. Please either edit the current configuration to use image copy or select another configuration which uses image copy. 3084 Date: 3085 Time: 3086 From: 3087 Until: 3088 Backup Time 3090 Backup 3091 ;Backup of databases, datafiles, tablespaces, or archivelogs 3092 Script: 3093 3094 Recovery Wizard : Introduction 3095 bThe recovery wizard helps you recover various objects like a database, tablespaces, and datafiles. 3096 ?he wizard will step you through the process of specifying what you want to recover and submit a recovery job through Enterprise Manager to complete the operation. 3097 ,Select the datafiles(s) you want to restore. 3099 -Select the tablespace(s) you want to recover. 4000 Object Selection 4001 Select what you want to recover: 4002 4004 4005 4006 4106 Recover data blocks only 4007 Recovery 4008 ;Restores and recovers databases, datafiles, or tablespaces 4010 4011 )Catalog maintenance wizard : Introduction 4012 tThe maintenance wizard helps you perform maintenance operations on the target databases and on the recovery catalog. 4133 ?sing this wizard, you can set up backup and retention policies in a target database, or register, reset or re-synchronize the target database with the recovery catalog. 4013 ?he wizard will step you through the process of specifying either a target maintenance operation or a recovery catalog maintenance operation and submit a job through Enterprise Manager to complete the operation. 4017 Operation choice 4018 5Choose the maintenance operation you wish to perform. 4134 =Modify backup and retention policies in the target database. 4135 2Maintain a target database in the recovery catalog 4019 Register database 4020 Resynchronize catalog 4021 Reset database 4136 Backup Policy 4137 ?utomatically backup controlfile and server parameter file (SPFILE) with every backup and database structural change. It is highly recommended to set this option. 4138 ?ontrolfile and SPFILE will be automatically backed up after each backup or after a datafile is added to the database. It is highly recommended to set this option. 4139 <Directory>%F 4141 ?ptimize backup by skipping unchanged files that have been backed up. The unchanged files typically include read-only and offline datafiles. 4142 wRead-only and offline tablespaces will be skipped from a complete database backup if they have been backed up recently. 4143 ~Exclude the following tablespaces from a complete database backup. You may back them up separately using a tablespace backup. 4144 KThese tablespaces can be backed up separately by doing a tablespace backup. 4145 Change... 4146 Retention Policy 4147 Set retention policy of backups 4148 No retention policy is set 4155 DYou need to delete old backups separately by submitting an RMAN job. 4149 kBy default, obsolete backups are deleted after each backup. You may unset this option in the Backup Wizard. 4150 ,Specify how the backups need to be retained: 4151 Number of days: 4153 Number of backups: 4154 Backup to: 4156 ?he current backup and retention policy in the target database has not been changed. You must modify at least one parameter to proceed. 4189 2These options reflect the current database policy. 4022 4023 Create 4024 Apply 4025 Recovery catalog session is null 4026 Register 4027 Accept 4028 Summary 4029 ?This is the summary of the backup operation you have requested. 4030 Backup Wizard 4031 AThis is the summary of the recovery operation you have requested. 4032 Recovery Wizard 4033 LThis is the summary of the catalog maintenance operation you have requested. 4034 Maintenance Wizard 4035 Predefined Strategy Error 4036 Yes 4037 4038 Range Selection 4039 ?ou may recover the entire database to the latest time. If you want to recover the entire database to a point-in-time in the past, then enter a date and time, or an SCN, or a log sequence number below. 4040 %Include controlfile with this backup. 4041 Rename 4042 ?o you want to restore the files to a different location? If so, enter a new path and name in the corresponding 'New Name' field. Any renamed files will be switched automatically. 4043 Original Name 4044 New Name 4045 ?he database is in an 'OPEN' state. It is therefore only possible to recover tablespaces or datafiles. To recover the entire database, the database must be in the 'MOUNT' state. 4046 <The database is in an 'OPEN' state and in 'ARCHIVELOG' mode. 4047 ?he default configuration for this database does not use a recovery catalog. The controlfile can only be restored if it was backed up using a recovery catalog. 4048 ?The database is in a 'MOUNT' state and in 'NOARCHIVELOG' mode. 4049 5You will only be able to restore the entire database. 4050 (The database is in the 'NOMOUNT' state. 5057 0You will only be able to restore the controlfile 4157 8The database is in a MOUNT state and in ARCHIVELOG mode. 4158 LThe database will be mounted after the controlfile is successfully restored. 4159 Restore and recover 4160 AYou may recover only tablespaces or datafiles to the latest time. 4161 ?ou may recover the entire database to the latest time or to a point in time in the past. You can also recover tablespaces or datafiles to the latest time. 4162 Advanced Options: 4163 Restore only: 4164 BYou may restore datafiles or archived logs (for Log Miner Viewer). 4165 Recover only: 4166 >You may perform a recovery if you have already restored files. 4167 tIf datafiles with corrupt blocks exist, you can restore and recover the blocks without taking the datafiles offline. 4168 OYou will only be able to restore the controlfile from a controlfile autobackup. 4169)If you have configured the database to automatically backup controlfile, the controlfile autobackups are located on disk and tape if you have performed backups to tape. The latest autobackup will be used to restore the controlfile. Modify the default values of DBID and disk location if necessary. 4170 Target database DBID: 4171 $Location for the autobackup on disk: 4172 <Default> 4173 ?ou may restore tablespaces or datafiles from either the latest backup or an older backup. You may also restore archived logs by specifying the start point and the end point in time, SCN or log sequence number. 4174 ?ou may restore the entire database, tablespaces or datafiles from either the latest backup or an older backup. You may also restore archived logs by specifying the start point and the end point in time, SCN or log sequence number. 4175 Recover to the latest time 4176 &Recover to a point-in-time in the past 4177 ?ou may restore the datafiles from the latest backup. If you wish to restore from an older backup, enter a date and time, an SCN or a log sequence number. You will restore from the latest backup at or before that point-in-time. 4178 Restore from the latest backup 4179 Restore from an older backup 4180 ?ou must specify the range of the archivelogs you want to restore. You may specify the range by time, an SCN or a log sequence number. If you do not select the "Until" option, the archivelogs until the most recent ones will be restored. 4181 Time 4182 SCN 4183 Log Sequence Number 4184 View Corruption List... 4185 Block# 4186 Number of Blocks 4187 Corruption Change# 4188 Corruption Type 4051 Backup configuration library 4052 Name 4053 Description 4054 Use Recovery Catalog 4055 Edit... 4056 Create Like... 4057 Delete 4058 Close 4059 Help 4060 No row is selected 4061 ?re you sure you want to delete this configuration? If you delete this configuration it will affect all the jobs saved in the library using this configuration 4062 Limits 4063 Maximum Capacity: 4064 Maximum Read Rate: 4065 Maximum Open Files: 4066 Multiple Targets 4068 Save / Submit 4070 'The database is in 'NOARCHIVELOG' mode. 4071 ?ou will only be able to perform a full database backup. If the database is open at the time of backup, it will be shutdown during the backup and will be brought up once the backup is complete. 4072 Backup Frequency 4073 <Choose the type of description that best fits your database. 4074 +My database is not frequently updated (DSS) 4075 Full backup once a week 4076 Backup day: 4077 >My database is moderately updated (OLTP) and is not very large 4078 Full backup everyday 4079 8My database is frequently updated and is large or medium 4080 7Full backup once a week and incremental backup everyday 4081 Full backup day: 4082 Sunday 4083 Monday 4084 Tuesday 4085 Wednesday 4086 Thursday 4087 Friday 4088 Saturday 4089 Backup Date: 4090 Backup Time: 4091 nSpecify a time when the backup should be made. An appropriate time would be when the database is least active. 4092 ?he database is running in 'NOARCHIVELOG' mode. When the backup job runs, the database will be closed and the backup taken. Then the database will be reopened. 4093 ,Maximum size of a backup set for archivelogs 4094 Kbytes 4095 Mbytes 4101 Kbytes/s 4102 Mbytes/s 4103 0Error: field can not be empty. Reset value to 1 4104 /Error: field can not be zero. Reset value to 1 4105 2Value can not be over {0} when the unit is MBytes. 4096 &Preferred Credentials 4097 lYou can override the job system's preferred credentials for backup jobs which use this backup configuration. 4099 ?he database you have chosen is in 'NOMOUNT' mode. The database must be 'OPEN' or 'MOUNTED' to perform a backup or a maintenance operation. 4100 dThe database you have chosen is closed. The database must be 'OPEN' or 'MOUNTED' to perform backups. 5000 TEnterprise Manager backup management features only support Oracle8 and up databases. 5001 rThe database you have chosen is closed. The database must be 'NOMOUNT', 'MOUNTED' or 'OPEN' to perform a recovery. 5002 hThe database is in 'NOARCHIVELOG MODE' and 'OPEN'. The database must be 'MOUNTED' to perform a recovery. 5003 GYou do not have any backup configurations which use a recovery catalog. 5004 bThe database you have chosen is closed. The database must be 'OPEN' to perform catalog operations. 5005 2None of the selected targets are of type database. 5006 [Using the backup configuration's overridden credentials, the following error has occurred: 5007 HUnknown error occurred while making a connection to the target database. 5008 ;Using preferred credentials, the following error occurred: 5010Last used configuration {0} does not have preferred credentials overridden. Press 'Cancel' and override the preferred credentials in the backup configuration or 'Cancel' and set the preferred credentials to 'SYSDBA' or 'OK' to accept the selected backup configuration as default. 5011 ?he preferred credentials are not set to 'SYSDBA' and there is no default backup configuration. You can either update the preferred credentials for this database in the console or create a backup configuration and override the preferred credentials. 5012 ?he preferred credentials are not set to 'SYSDBA' You can either press 'Cancel' and change the preferred credentials or press 'OK' to accept the selected backup configuration as default. 5013 Role: 5014 SYSDBA 5015 kNode credentials are not set for this node. Set the credentials for this node in the preferred credentials. 5065]You cannot run this operation because the credentials do not include the SYSDBA role. The credentials for this operation come from the backup configuration {0}. A backup configuration specifies credentials -- either the preferred credentials for the database (as set in the Preferences dialog) or specific credentials for the backup configuration. 5017 vReview this information and press 'OK' to complete the operation or press 'Cancel' to go back and change your request. 5018 (Enter recovery catalog logon credentials 5021 kThe backup operation will run as an Enterprise Manager job. When and how often do you want your job to run? 5022 -Use the preferred credentials (set as SYSDBA) 5023 .Override preferred credentials for backup jobs 5024 Enter credentials 5025 Connection error 5026 Choose a configuration: 5027 ?f you update this configuration, all the jobs using this configuration in the library will be affected. If you still want to continue then refresh all the jobs in the library using this configuration. Do you want to continue? 5028 TThe following datafile(s) selected in this job do not exist in the target database. 5029 VThe following tablespace(s) selected in this job do not exist in the target database. 5031 Full backup 5032 Incremental backup 5033 Incremental level: 5034 Cumulative 5035 Non-cumulative 5036 Backup of the entire database. 5037 Backup of selected tablespaces. 5038 Backup of selected datafiles. 5039 Backup of archivelogs. 5040 .Backup of the entire database and archivelogs. 5041 3Backup of the selected tablespaces and archivelogs. 5042 1Backup of the selected datafiles and archivelogs. 5043 JPredefined backup strategy to take the backup of entire database everyday. 5044 MPredefined backup strategy to take the backup of entire database once-a-week. 5045 ?redefined backup strategy to take the backup of entire database incremental level 0 once a week and incremental level 1 every other day. 5046 Recovery of the entire database. 5047 %Recovery of the selected tablespaces. 5048 #Recovery of the selected datafiles. 5049 Recovery of the controlfile. 5050 8Register the target database(s) in the recovery catalog. 5051 #Resynchronize the recovery catalog. 5052 @Reset the target database's information in the recovery catalog. 5053 Summary of the configuration: 5054 DWhile validating the recovery catalog the following error occurred: 5055 1Perform recovery without restoring the datafiles. 5056 Media Management Information: 5058 No backup parameters specified 5059 No recovery parameters specified 5060 Backup Server: 5061 Local 5062 Remote 5063 ?ob cannot be submited to run. An active job exists with the same name. Rename the current job or edit the existing active job. 5064 xJob cannot be saved to library. A job with the same name already exists in the library. Please rename the current job. 4107 %Block Media Recovery Method Selection 4108 =Data blocks may be recovered in one of the following methods. 4109 JSpecify the datafiles and the block IDs in the database that need recovery 4110 GSpecify the tablespaces and the data block addresses that need recovery 4111 |Recover all data blocks that have been labeled CORRUPTED during the backup and copy operations performed by Recovery Manager 4112 Corruption List 4113 Data Block Selection by Datafile 4115 ?pecify the data blocks that need media recovery by selecting datafiles and entering the block numbers for each selected datafile. More than one data block can be entered for one datafile. Separate block numbers by space or comma. 4114 "Data Block Selection by Tablespace 4116 ?pecify the data blocks that need media recovery by selecting tablespaces and entering the data block addresses for the each selected tablespace. More than one address can be entered for one tablespace. Separate addresses by space or comma. 4117 PData Block Numbers must be a list of integers separated by either space or comma 4118 'Please enter at lease one block number. 4119 Datafile Name 4120 File# 4121 Block Numbers 4122 Tablespace Name 4123 Data Block Addresses 4124 RData Block Addresses must be a list of integers separated by either space or comma 4125 -Please enter at lease one data block address. 4126 %Recovery of the selected data blocks. 4127 Recover to a point-in-time: 4128 SCN: 4129 Sequence: 4130 Thread#: 4131 Recover to the latest 4132 3113 Optimize Backup 3114 Oracle Recovery Manager may optimize your database or archivelog backups by skipping read-only files which have been backed up. 3115 Optimize backups 3116 Do not optimize backups 3112 &Generate/View Script through Wizard... 3117 IUse proxy copy supported by media management software to perform a backup 3118 _If the proxy copy fails, continue and let Oracle Recovery Manager perform a conventional backup 3119 EIf the proxy copy fails, halt the backup and return the error message 3120 Channel 3121 Choose a backup mode 3122 Online Backup 3123 Offline Backup 3141 7The backup will be performed when the database is OPEN. 3142 ?he database will be shut down and brought to MOUNT state before the backup is performed. The database will be opened after the backup. 3124 Choose an existing service: 3125 Enter a new service: 3126 Host Name: 3127 Port: 3128 SID: 3129 #Excluded from Whole Database Backup 3130 $Override Backup and Retention Policy 3131 Override backup policy: 3132 Override retention policy: 3133 Keep this backup or copy until: 3134 ZKeep the backups of the subsequent logs for a point-in-time recovery until the above date. 3135 rDo not use this backup for a point-in-time recovery. The subsequent logs may be deleted when they become obsolete. 3136 9Include all the tablespaces in a complete database backup 3137 ^You need to set this option if you want to include all tablespaces in a whole database backup. 3138 Do not optimize this backup 3139 EBackup all files even if they have not changed since the last backup. 3140 View Current Policies ... 3145 Backup Policy: 3146 Retention Policy: 3147 Backup and Retention Policy 3148 Archived Log Deletion 3149 ?o you want the archived logs to be deleted after every backup? You may select one of the following options based on your available disk space and desired recovery time. 3150 *No, I will delete the archived logs later. 3151 uYou must have enough disk space for your archived logs. Your database will stop running if you run out of disk space. 3152 jYes, delete archived logs that are older than the specified days and have the specified number of backups. 3153 HYou must have enough disk space to keep the logs until they are deleted. 3154 Days: 3155 1Yes, delete all archived logs after every backup. 3156 ?his option may result in less disk space usage than the above options. However, the recovery may be slower since the latest archived logs may need to be restored from backups. 3157 oDatabase and archivelog backups are optimized so that unchanged files that have been backed up will be skipped. 3158 kBackup optimization is not set in the database. All files including the unchanged files will be backed up. 3159 FThe following tablespaces are excluded from an entire database backup: 3160 :All tablespaces are included in an entire database backup. 3161 _No retention policy is set. No backups or image copies will be considered obsolete and deleted. 3162Retention policy is set so that the database may be recovered to any point-in-time in the past {0} days. Any backups and copies necessary for such a recovery are kept. Backup and copies not needed for such a recovery are considered obsolete and may be deleted. 3163 RRetention policy is set so that each datafile has at least {0} backups or copies. 3164 qRetain at least the specified number of backups for each datafile and delete obsolete backups after every backup. 3111The preferred database credentials are not set to 'SYSDBA' and the current backup configuration does not override preferred credentials. You can either edit the current backup configuration or select another configuration which overrides the preferred credentials 5066cYou will only be able to perform a full database backup. If the database is open at the time of backup, it will be shutdown during the backup and will be brought up once the backup is complete. Please note that only the current cluster database instance will be stopped and restarted. Do not proceed with backup if all other instances are not stopped. 3143 )Delete obsolete backups after this backup 3144 rYou may specify how the backups are considered obsolete by setting the retention policy in the Maintenance Wizard. 3165 Excluded Tablespaces oracle/sysman/resources/VtorMsg java/util/ListResourceBundle !oracle/sysman/resources/VtorMsgID !12 3 45 67 8 *? ? 9 1 :; 8 ? ? 9 @ <7 8 N 6? Y? YSYSSY? YSYSSY? Y SY SSY? Y SY SSY? Y SYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY ? YSYSSY ? YSYSSY ? YSY SSY ? Y SY SSY ? Y SY SSY? Y!SY"SSY? Y#SY$SSY? Y%SY&SSY? Y'SY(SSY? Y)SY*SSY? Y+SY,SSY? Y-SY.SSY? Y/SY0SSY? Y1SY2SSY? Y3SY4SSY? Y5SY6SSY? Y7SY8SSY? Y9SY:SSY? Y;SY<SSY ? Y=SY>SSY ? Y?SY@SSY ? YASYBSSY ? YCSYDSSY ? YESYFSSY!? YGSYHSSY"? YISYJSSY#? YKSYLSSY$? YMSYNSSY%? YOSYPSSY&? YQSYRSSY'? YSSYTSSY(? YUSYVSSY)? YWSYXSSY*? YYSYZSSY+? Y[SY\SSY,? Y]SY^SSY-? Y_SY`SSY.? YaSYbSSY/? YcSYdSSY0? YeSYfSSY1? YgSYhSSY2? YiSYjSSY3? YkSYlSSY4? YmSYnSSY5? YoSYpSSY6? YqSYrSSY7? YsSYtSSY8? YuSYvSSY9? YwSYxSSY:? YySYzSSY;? Y{SY|SSY<? Y}SY~SSY=? YSY?SSY>? Y?Y?SY?? Y?Y?SY@? Y?Y?SYA? Y?Y?SYB? Y?Y?SYC? Y?Y?SYD? Y?Y?SYE? Y?Y?SYF? Y?Y?SYG? Y?Y?SYH? Y?Y?SYI? Y?Y?SYJ? Y?Y?SYK? Y?Y?SYL? Y?Y?SYM? Y?Y?SYN? Y?Y?SYO? Y?Y?SYP? Y?Y?SYQ? Y?Y?SYR? Y?Y?SYS? Y?Y?SYT? Y?Y?SYU? Y?Y?SYV? Y?Y?SYW? Y?Y?SYX? Y?Y?SYY? Y?Y?SYZ? Y?Y?SY[? Y?Y?SY\? Y?Y?SY]? Y?Y?SY^? Y?Y?SY_? Y?Y?SY`? Y?Y?SYa? Y?Y?SYb? Y?Y?SYc? Y?Y?SYd? Y?Y?SYe? Y?Y?SYf? Y?Y?SYg? Y?Y?SYh? Y?Y?SYi? Y?Y?SYj? Y?Y?SYk? Y?Y?SYl? Y?YfSSYm? Y?Y?SYn? Y?Y?SYo? Y?Y?SYp? Y?Y?SYq? Y?Y?SYr? Y?Y?SYs? Y?Y?SYt? Y?Y?SYu? Y?Y?SYv? Y?Y?SYw? Y?Y?SYx? Y?Y?SYy? Y?Y?SYz? Y?Y?SY{? Y?YfSSY|? Y?Y?SY}? Y?Y?SY~? Y?Y?SY? Y?Y?SY ?? Y?Y?SY ?? Y?SY SSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? Y SY SSY ?? Y SY SSY ?? Y SYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSY SSY ?? Y SY SSY ?? Y SY SSY ?? Y!SY"SSY ?? Y#SY$SSY ?? Y%SY&SSY ?? Y'SY(SSY ?? Y)SY*SSY ?? Y+SY,SSY ?? Y-SY.SSY ?? Y/SY0SSY ?? Y1SY2SSY ?? Y3SY?SY ?? Y4SY5SSY ?? Y6SY7SSY ?? Y8SY9SSY ?? Y:SY;SSY ?? Y<SY=SSY ?? Y>SY?SSY ?? Y@SYASSY ?? YBSYCSSY ?? YDSYESSY ?? YFSYGSSY ?? YHSYISSY ?? YJSYKSSY ?? YLSYMSSY ?? YNSYOSSY ?? YPSY?SY ?? YQSYRSSY ?? YSSYTSSY ?? YUSYVSSY ?? YWSYXSSY ?? YYSYZSSY ?? Y[SY\SSY ?? Y]SY^SSY ?? Y_SY`SSY ?? YaSYbSSY ?? YcSYdSSY ?? YeSYfSSY ?? YgSYhSSY ?? YiSYjSSY ?? YkSYlSSY ?? YmSYnSSY ?? YoSYpSSY ?? YqSYrSSY ?? YsSYtSSY ?? YuSYvSSY ?? YwSYxSSY ?? YySYzSSY ?? Y{SY|SSY ?? Y}SY~SSY ?? YSY?SSY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ? Y?Y?SY? Y?Y?SY? Y?SY SSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY? Y SY SSY? Y SY SSY ? Y SYSSY ? YSYSSY ? YSYSSY ? YSYSSY ? YSYSSY? YSYSSY? YSYSSY? YSY SSY? Y SY SSY? Y SY SSY? Y!SY"SSY? Y#SY$SSY? Y%SY&SSY? Y'SY(SSY? Y)SY*SSY? Y+SY,SSY? Y-SY.SSY? Y/SY0SSY? Y1SY2SSY ? Y3SY4SSY ? Y5SY6SSY ? Y7SY8SSY ? Y9SY:SSY ? Y;SY<SSY!? Y=SY>SSY"? Y?SY@SSY#? YASYBSSY$? YCSYDSSY%? YESYFSSY&? YGSYHSSY'? YISYJSSY(? YKSYLSSY)? YMSYNSSY*? YOSYPSSY+? YQSYRSSY,? YSSYTSSY-? YUSYVSSY.? YWSYXSSY/? YYSYZSSY0? Y[SY\SSY1? Y]SY^SSY2? Y_SY`SSY3? YaSYbSSY4? YcSYdSSY5? YeSYfSSY6? YgSYhSSY7? YiSYjSSY8? YkSYlSSY9? YmSYnSSY:? YoSYpSSY;? YqSYrSSY<? YsSYtSSY=? YuSYvSSY>? YwSYxSSY?? YySYzSSY@? Y{SY|SSYA? Y}SY~SSYB? YSY?SSYC? Y?Y?SYD? Y?Y?SYE? Y?Y?SYF? Y?Y?SYG? Y?Y?SYH? Y?Y?SYI? Y?Y?SYJ? Y?Y?SYK? Y?Y?SYL? Y?Y?SYM? Y?Y?SYN? Y?Y?SYO? Y?Y?SYP? Y?Y?SYQ? Y?Y?SYR? Y?Y?SYS? Y?Y?SYT? Y?Y?SYU? Y?Y?SYV? Y?Y?SYW? Y?Y?SYX? Y?Y?SYY? Y?Y?SYZ? Y?Y?SY[? Y?Y?SY\? Y?Y?SY]? Y?Y?SY^? Y?Y?SY_? Y?Y?SY`? Y?Y?SYa? Y?Y?SYb? Y?Y?SYc? Y?Y?SYd? Y?Y?SYe? Y?Y?SYf? Y?Y?SYg? Y?Y?SYh? Y?Y?SYi? Y?Y?SYj? Y?Y?SYk? Y?Y?SYl? Y?Y?SYm? Y?Y?SYn? Y?Y?SYo? Y?Y?SYp? Y?Y?SYq? Y?Y?SYr? Y?Y?SYs? Y?Y?SYt? Y?Y?SYu? Y?Y?SYv? Y?Y?SYw? Y?Y?SYx? Y?Y?SYy? Y?Y?SYz? Y?Y?SY{? Y?Y?SY|? Y?Y?SY}? Y?Y?SY~? Y?Y?SY? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?SY SSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? Y SY SSY?? Y SY SSY?? Y SYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSY SSY?? Y SY SSY?? Y SY SSY?? Y!SY"SSY?? Y#SY$SSY?? Y%SY&SSY?? Y'SY(SSY?? Y)SY*SSY?? Y+SY,SSY?? Y-SY.SSY?? Y/SY0SS? ? 9 C = >
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de