？？？？？？？ NBU 4.5 open file 不能備份問題，高手請指教

romexp

沒有高手知道嗎？

是不是我的版本的問題，沒有OPEN FILE 的選項啊

romexp

斑竹叱。怎么沒有高手啊

romexp

up

romexp

原帖由 maping 于 2006-10-16 15:16 发表
一直在帮你找原因，但因为版本比较老，都找不到软件过来测试。

謝謝啊。。。真是好人一個啊。

OTM的問題已經解決了。
但還是說有的文件在用不能備份啊

romexp

原帖由 maping 于 2006-10-16 17:01 发表
把你现象在说说


OTM是怎么解决的？

Exact Error Message
exit status code 1: the requested operation was partially successful; or exit status code 11: system call failed

Details:
This TechNote provides some general guidelines and recommendations for configuring Open Transaction Manager (OTM).

When utilizing OTM, the following two error conditions have been seen in some environments:

Exit Status Code 1
The Backup is started but the required quiescent period is not achieved. OTM is not enabled during the course of the Backup. The backup job will end with an exit status code 1 as open or active files are not included in the back up.

Exit Status code 11
The backup is started and OTM is successfully initialized (quiescent period achieved and snapshot taken). When OTM reaches this point but experiences a resource limitation within the system, the backup job will end in an exit status code 11.


Guidelines:

Disk Cache settings are an integral component for OTM operations. The documented defaults for the cache settings are "initial = 10MB" and "max = 50MB". However, best results have been achieved with the OTM cache settings as "initial=100MB" and "max=0MB".  Because of the diversity of environments, these settings will vary.  Manually configured values may be needed due to low free disk space or the amount of data to be backed up. Below are some recommendations to allow OTM to work as dynamically as possible. Sufficient disk space is required for OTM to be operational. Insufficient system resources may prevent implementation of OTM in the operating environment. Also, OTM may not be a viable open file manager solution on NT servers that are extremely busy. OTM needs a "quiescent" or inactive period of time (5 seconds by default) to create a snapshot of a disk partition.  Backup jobs that run when the level of disk activity is high, or a "quiescent", or inactive period of time cannot be achieved, will end with an "exit status code:  1".  This indicates the backup was only partially successful.

romexp

接上面

Recommendations:

These settings will allow the most scalability with OTM.  These settings are not guaranteed to work on all NT servers. Depending on free disk space or available memory, these settings may have to be manually configured.

1.  SNAPSHOT TYPE: Set OTM snap shot type to "Individual" unless multiple data streams is enabled.  The "Individual" setting will allow OTM to create a snapshot per drive and will allow the cache file to be minimum size as a snapshot of one drive at a time will occur.  This setting is recommended for servers with low disk space and when Multiple Data Stream backups are not enabled.  

2.  INITIAL CACHE SIZE: Set Initial cache size to 100MB.  OTM will create the initial cache file before the backup starts. An initial cache setting of 100MB will allow the backup to start faster, but may slow performance slighty if the cache file needs to grow during the course of the backup due to open file activity.  Setting this value higher will create a longer delay at the start of the backup until the cache file has been created.  Creating a larger Initial cache file may increase performance during backups if frequent disk writes occur during the backup.  The time for building the initial cache file will primarily depend on CPU speed and server activity.

3.  MAX CACHE SIZE: Set Max cache size to 0MB.  With the Max Cache Size set to 0MB, OTM will calculate 10 percent of the used disk space as its maximum.  
- When "Global" is set for the snap shot type, OTM will calculate 10 percent of all used disk space for all disks included in the file list to be backed up.                                       
- When "All Available" is set for the snap shot type, OTM will calculate 10 percent of all used disk space for all local disks on the server including drives that are not specified in the file list of files to be backed up.  This value may need to be manually configured on some NT server that have over 35GB to be backed up (See below in        Caveats).

4.  CACHE FILE FIELD: Ensure the "Cache file" field is not configured or left blank. The Cache file field is used to allow the user to define the location of the Cache File. If this field is blank, OTM will dynamically and automatically place the cache file on a drive that has the most free space. OTM will attempt to place the cache file on a drive that is not being backed up. Due to available disk space, the cache file may end up on the drive that is active during the backup. When this occurs, the Initial cache file setting is not used and OTM will create an Initial cache file the same size as the maximum cache file size.

5.  OTM ERROR CONTROL: Set "OTM Error Control" to "Retry OTM".  This will allow NetBackup to pause the backup when the cache file fills up. OTM will then destroy the cache file, create another snapshot of the drive(s), and continue the backup.

6. CACHED FILES: It is NOT recommended to change this field from the default value of 0. When this field is set to 0, the cache file will not grow beyond the size of the configured "initial cache file" size if the "max cache file" size is set to any value other than 0.  Since the recommended "max cache file" size setting is 0, the above limitation is not a factor (see bullet number 3).  It has been found that leaving this value at its default value of 0 will allow OTM to operate more efficiently and dynamically on most servers.

romexp

Exact Error Message
status 11: system call failed

Details:
When there is a cache full condition within Open Transaction Manager, backups may fail with an exit code of 11 (system call failed).  The cache full condition is usually reached because the system is busy at the time of the backup and files are changing.  There is another condition as well - just normal file transversal.  As the backups proceed, the last access time is updated on each file and this information ends up being cached.  Thus, if the system has a lot of files, a lot of access time update information ends up being cached which, depending on the size of the cache file, can end up in a cache full condition.

If disabling the last access time will not impair the operation of any applications that are running on this machine, doing so will stop it from increasing the size of your cache file.

A value must be added to the registry in order to disable the last access time update.

The key is:
HKEY_LOCAL_MACHINE:\SYSTEM\CurrentControlSet\Control\FileSystem

and the value is:

NtfsDisableLastAccessUpdate with a type of REG_DWORD and a value of 1.

A reboot is required of the system after adding this value.

As an example, a test machine was setup with 10,000 subfolders and each one of those subfolders has 20 files.  Without this value, the amount of data sent to the cache file was 260MB.  With this value added, the amount of data sent to the cache file was 0MB.  

Otherwise, increasing the cache size for OTM within the VERITAS registry keys or from the Configuration Application from an NT Master server will also help alleviate this condition.  This is documented within the "VERITAS NetBackup for Windows NT Server System Administrator Guide" on page 502.

romexp

這樣他們說的是可以做到的，OTM現在沒有問題了，

但是在open file 不能備份的問題還是沒有解決。

希望版主幫忙啊！？

romexp

up

romexp

*******************************************************************************
MEDIA SUMMARY FOR SERVER bk1 ON Wed Oct 18 2006 10:12:12
*******************************************************************************
ACTIVE        FULL        SUSPENDED        FROZEN        IMPORTED
2        7        0                1        0
Number of NON-ACTIVE media that:
       1 - are currently EXPIRED
            4863L1 expired 02/17/2005 22:08 (FROZEN)
       3 - will expire within 1 week
            4865L1 expires 10/20/2006 09:05
            4861L1 expires 10/22/2006 15:03
            4868L1 expires 10/24/2006 01:27
       4 - will expire between 1 and 2 weeks
            4871L1 expires 10/26/2006 01:23
            4864L1 expires 10/29/2006 12:05
            4862L1 expires 10/29/2006 15:05
            4872L1 expires 11/01/2006 01:14
Number of ACTIVE media that, as of now:
       1 - will expire within 1 week
            4870L1 expires 10/24/2006 13:33
       1 - will expire between 1 and 2 weeks
            4867L1 expires 11/01/2006 09:05
Summary by retention level of ALL media
     Level   # Media        Megabytes
       1        10          1371029.1


有誰能幫我看看我的帶庫的信息是什么意思啊。

ACTIVE        FULL        SUSPENDED        FROZEN        IMPORTED
分別是什么意思啊。。不是很理解啊。

[ 本帖最后由 romexp 于 2006-10-18 10:19 编辑 ]