Chinaunix

标题: ？？？？？？？ NBU 4.5 open file 不能備份問題，高手請指教 [打印本页]

作者: romexp 时间: 2006-10-11 09:30
标题: ？？？？？？？ NBU 4.5 open file 不能備份問題，高手請指教
我們的NBU總是報錯，說有文件被鎖定，無法備份，
錯誤代碼是1

還有一個就不能完全進行全備份，有時累積備份也不行，總是出現
錯誤代碼是11 (此問題已解決)

http://bbs.doit.com.cn/viewthrea ... =page%3D1#pid336059

[ 本帖最后由 romexp 于 2006-10-26 09:39 编辑 ]

veritas_error1.GIF (16.07 KB, 下载次数: 106)

作者: romexp 时间: 2006-10-11 09:32
2006/10/11 W 01:49:39 - Error bpbrm(pid=1192) from client zhagms: ERR - OTM Error:0xe0001005 (WIN32 -536866811: Unknown error)
2006/10/11 W 01:49:43 - Error bpbrm(pid=1192) from client zhagms: ERR - OTM Error while reading file: D:\AGMS\strg\style\CutTrade\Data\1200923-B#1.sty
2006/10/11 W 01:49:43 - Critical bpbrm(pid=1192) from client zhagms: FTL - Backup operation aborted!
2006/10/11 W 01:49:45 - end writing; write time: 00:26:31
system call failed(11)
2006/10/11 W 01:49:45 - Error bpsched(pid=1424) suspending further backup attempts for client zhagms, policy Zhagms, schedule Zhagms_Cumu_Tuesday because it has exceeded the configured number of tries
2006/10/11 W 01:49:45 - Error bpsched(pid=1424) backup of client zhagms exited with status 11 (system call failed)

作者: sonorous 时间: 2006-10-11 09:45
我也碰到过，好像是非法文件名的问题

作者: 科学球 时间: 2006-10-11 11:03
把数据库停了再执行策略

作者: romexp 时间: 2006-10-11 11:10

原帖由 科学球 于 2006-10-11 11:03 发表
把数据库停了再执行策略

怎么停止啊，請大俠赤腳

作者: 科学球 时间: 2006-10-11 11:19
你什么数据库？因为数据库在运行，很多库文件被锁了，所以你完全备份不成功。必须把数据库停了，再备份，才能完全成功。

作者: romexp 时间: 2006-10-11 12:31

原帖由 sonorous 于 2006-10-11 09:45 发表
我也碰到过，好像是非法文件名的问题

不會吧。文件名很正常啊。。

作者: romexp 时间: 2006-10-11 12:32

原帖由 科学球 于 2006-10-11 11:19 发表
你什么数据库？因为数据库在运行，很多库文件被锁了，所以你完全备份不成功。必须把数据库停了，再备份，才能完全成功。

沒有啊。只是文件，沒有安裝數據庫呀

原來可以，現在換新的服務器，重安裝veritas client 就不行了。（指的是錯誤碼為11的那個）

[ 本帖最后由 romexp 于 2006-10-11 12:35 编辑 ]

作者: 光头佬 时间: 2006-10-12 13:00
备份主机上-客户端属性-master server-双击备份主机-客户机属性-add这台备份报错的客户端，然后还是在各个窗口下的windows open file backup,把那个enable的钩去掉

作者: romexp 时间: 2006-10-12 13:14

原帖由 光头佬 于 2006-10-12 13:00 发表
备份主机上-客户端属性-master server-双击备份主机-客户机属性-add这台备份报错的客户端，然后还是在各个窗口下的windows open file backup,把那个enable的钩去掉

不知道在哪個地方啊。你能說詳細點嗎？

作者: romexp 时间: 2006-10-12 14:41
2006/10/11 W 01:49:39 - Error bpbrm(pid=1192) from client zhagms: ERR - OTM Error:0xe0001005 (WIN32 -536866811: Unknown error)
2006/10/11 W 01:49:43 - Error bpbrm(pid=1192) from client zhagms: ERR - OTM Error while reading file: D:\AGMS\strg\style\CutTrade\Data\1200923-B#1.sty
2006/10/11 W 01:49:43 - Critical bpbrm(pid=1192) from client zhagms: FTL - Backup operation aborted!
2006/10/11 W 01:49:45 - end writing; write time: 00:26:31
system call failed(11)
2006/10/11 W 01:49:45 - Error bpsched(pid=1424) suspending further backup attempts for client zhagms, policy Zhagms, schedule Zhagms_Cumu_Tuesday because it has exceeded the configured number of tries
2006/10/11 W 01:49:45 - Error bpsched(pid=1424) backup of client zhagms exited with status 11 (system call failed)

以下是OTM出現錯誤，OTM是什么啊。起什么作用啊我能不能關掉它

veritas_OTM.GIF (21.99 KB, 下载次数: 46)

作者: maping 时间: 2006-10-12 16:26
一个常见的原因是服务器的文件系统已满；确保系统的虚拟内存没有用尽。如果是虚拟内存问题，请关闭不使用的应用程序或增加虚拟内存量。

作者: romexp 时间: 2006-10-12 16:56

原帖由 maping 于 2006-10-12 16:26 发表
一个常见的原因是服务器的文件系统已满；确保系统的虚拟内存没有用尽。如果是虚拟内存问题，请关闭不使用的应用程序或增加虚拟内存量。

好像不是呀。我的server 很單純的，我是新的server 更換後才出現的這樣的問題，只是重新安裝了client soft 而已，在這之前是不會有OTM的錯誤的。我在網上找到的一個原因，http://seer.support.veritas.com/docs/233254.htm
不知道能行不，與大家分享啊

還是不明白OTM是什么意思！

作者: maping 时间: 2006-10-12 17:38
用的是NBU3.4啊？
OTM是Open Transaction Manager。
for windows open file backup
另外有个建议是添加一个open file backup 客户端试试。

status code 1 mean there are some files can't be backed up and status code 11,it seems file write error

作者: romexp 时间: 2006-10-12 17:59

原帖由 maping 于 2006-10-12 17:38 发表
用的是NBU3.4啊？
OTM是Open Transaction Manager。
for windows open file backup
另外有个建议是添加一个open file backup 客户端试试。

status code 1 mean there are some files can't be backed up ...

是4.5FP_3GA版本
我怎么添加open file backup 啊

作者: june_cai 时间: 2006-10-12 18:05
不是在client属性，是在服务器属性里面添加openfile备份客户端。

作者: romexp 时间: 2006-10-12 18:41

原帖由 june_cai 于 2006-10-12 18:05 发表
不是在client属性，是在服务器属性里面添加openfile备份客户端。

是在這里面加嗎？

好像也沒有open file啊

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

veritas_server.GIF (21.5 KB, 下载次数: 52)

作者: romexp 时间: 2006-10-13 09:05
沒有高手知道嗎？

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

作者: romexp 时间: 2006-10-14 15:18
斑竹叱。怎么沒有高手啊

作者: romexp 时间: 2006-10-16 14:41
up

作者: maping 时间: 2006-10-16 15:16
一直在帮你找原因，但因为版本比较老，都找不到软件过来测试。

作者: romexp 时间: 2006-10-16 15:26

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

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

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

作者: maping 时间: 2006-10-16 17:01
把你现象在说说

OTM是怎么解决的？

作者: romexp 时间: 2006-10-17 09:24

原帖由 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 时间: 2006-10-17 09:25
接上面

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 时间: 2006-10-17 09:41
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 时间: 2006-10-17 09:43
這樣他們說的是可以做到的，OTM現在沒有問題了，

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

希望版主幫忙啊！？

作者: romexp 时间: 2006-10-18 08:17
up

作者: romexp 时间: 2006-10-18 10:17
*******************************************************************************
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 编辑 ]

作者: yddll 时间: 2006-10-18 11:14
找服务商吧,别鼓捣了

作者: romexp 时间: 2006-10-18 11:52

原帖由 yddll 于 2006-10-18 11:14 发表
找服务商吧,别鼓捣了

找他們也只能是要我們換版本啊。再說了，要換的話也不能馬上解決問題呀

我們的版本是4.5FP_3GA

不知道是package 幾好多都是sp 8了。
我的能不能打補丁

作者: yddll 时间: 2006-10-18 20:51
不行的话，全卸载，重新装一遍，重起机器

作者: romexp 时间: 2006-10-19 09:36
我做了啊。。當然只是客戶端了，

我不太喜歡重裝啊。只是我們沒有搞清楚它的原因啊。

作者: romexp 时间: 2006-10-20 08:33
up

作者: bc_tech2 时间: 2006-10-20 15:45
执行available_media.cmd, 看一下.

C:\Program Files\VERITAS\NetBackup\bin\goodies>available_media.cmd

media media robot robot robot side/ ret size status
ID type type # slot face level KBytes
----------------------------------------------------------------------------
DataStore pool

NetBackup pool

----------------------------------------------------
----------------------------------------------------
None pool

----------------------------------------------------
----------------------------------------------------
NT_fs_pool pool

作者: romexp 时间: 2006-10-24 19:09
C:\veritas\NetBackup\bin\goodies>available_media.cmd
media media robot robot robot side/ ret size    status
ID    type type    #    slot face level  KBytes
----------------------------------------------------------------------------
DataStore pool

NetBackup pool

5053L1  HCART TLD    0    10    -    -    -       DBBACKUP

None pool

scratch pool

4866L1  HCART TLD    0    22    -    -    -       AVAILABLE
4868L1  HCART TLD    0    20    -    -    -       AVAILABLE
4869L1  HCART TLD    0    19    -    -    -       AVAILABLE
4870L1  HCART TLD    0    18    -    -    -       AVAILABLE
4873L1  HCART TLD    0    4    -    -    -       AVAILABLE
5054L1  HCART NONE    -    -    -    -    -       AVAILABLE
5055L1  HCART NONE    -    -    -    -    -       AVAILABLE
5056L1  HCART NONE    -    -    -    -    -       AVAILABLE
5057L1  HCART NONE    -    -    -    -    -       AVAILABLE
5058L1  HCART NONE    -    -    -    -    -       AVAILABLE
5059L1  HCART NONE    -    -    -    -    -       AVAILABLE
5060L1  HCART NONE    -    -    -    -    -       AVAILABLE
5061L1  HCART NONE    -    -    -    -    -       AVAILABLE
5062L1  HCART NONE    -    -    -    -    -       AVAILABLE
5063L1  HCART NONE    -    -    -    -    -       AVAILABLE
5064L1  HCART NONE    -    -    -    -    -       AVAILABLE
5065L1  HCART NONE    -    -    -    -    -       AVAILABLE
5066L1  HCART NONE    -    -    -    -    -       AVAILABLE
5067L1  HCART NONE    -    -    -    -    -       AVAILABLE

Windows pool

4863L1  HCART TLD    0    25    -    1    11071536 FROZEN/MPX
4862L1  HCART TLD    0    26    -    1    161502156       FULL/MPX

4864L1  HCART TLD    0    24    -    1    223290682       FULL/MPX

4865L1  HCART TLD    0    23    -    1    165512167       FULL/MPX

4867L1  HCART TLD    0    21    -    1    168932892       FULL/MPX

4871L1  HCART TLD    0    2    -    1    259380629       FULL/MPX

4872L1  HCART TLD    0    3    -    1    178361824       FULL/MPX

4861L1  HCART TLD    0    27    -    1    123253023       MPX

作者: romexp 时间: 2006-10-25 16:00
本論壇好像都沒有高手啊。

作者: romexp 时间: 2006-10-26 09:34
大家都去那里了呀，，，沒有人回或

作者: romexp 时间: 2007-02-07 19:03
真的沒辦法了嗎？

up

[ 本帖最后由 romexp 于 2007-4-16 15:46 编辑 ]

欢迎光临 Chinaunix (http://bbs.chinaunix.net/)