티스토리 툴바


달력

01

« 2012/01 »

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  •  
  •  
  •  
  •  
http://www.symantec.com/business/support/index?page=content&id=TECH38709

Problem

STATUS CODE: 156 "snapshot error encountered" occurs when utilizing VSP or VSS for open file backups.

Error

snapshot error encountered (156)

Environment

Windows 2003

Netbackup 7.0

Cause

Troubleshooting:
If a backup on a Windows NetBackup (tm) 5.0 or later client fails with status code 156, this indicates that the client is using Windows Open File Backups to protect open or active files. The volume "snapshot" that occurs to facilitate open file backup has failed. This failure is often caused by the VSP/VSS cache file running out of allocated space.
 

Solution

Note:
In versions 7.0 and later VSP is no longer a valid snapshot method. These systems will need to utilize the VSS provider for snapshots.

Overview:
STATUS CODE: 156 "snapshot error encountered" occurs when utilizing VERITAS Volume Snapshot Provider (VSP) or Microsoft Volume Shadow Copy Service (VSS) for a client backup.


Master Log Files:  N/A

Media Server Log Files:  N/A

Client Log Files: 
bpbkar
6:00:14.156 AM: [452.976] <2> tar_base::V_vTarMsgW: ERR - Snapshot Error while reading file: Volume{43877774-d2zz-4rar-r5id-fg9i49fuje7815}\Accounts\Akerfeldt\data\Amm.txt
6:00:14.171 AM: [452.976] <2> tar_base::V_vTarMsgW: FTL - Backup operation aborted!
6:00:14.218 AM: [452.976] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 156: snapshot error encountered


Resolution:
Firstly, if Open file backups are not desired for the client, disable them. This will decrease the resources used by the client during backup and resolve any Status 156 errors. The default NetBackup install options are to have open file backups enabled.

To confirm if VSS or VSP open file backups are activated:
 
1. Within the NetBackup Administration Console, expand Host Properties in the right hand pane
 
2. Within Host Properties, click Master Server and then the double-click the name of the Master Server in the right pane
 
3. Click on the Client Attributes section
 
4. If the client in question is listed here, click on the client name. If it is not listed, add and click on the client name.
 
5. Click the Windows Open File Backup tab
 
6. Ensure that Enable Windows Open File Backups for this client is not selected if open file backups are not required

If open file backup functionality is needed, the most common cause for snapshot errors is cache file configuration. The steps on changing this depend on whether VSP or VSS is used as the Snapshot Provider.

If VSP is being used as the snapshot provider:
Access the Host Property settings for VSP:
 
1. Within the NetBackup Administration Console, expand Host Properties in the left pane
 
2. Within Host Properties, click Clients and then double-click the name of the client in the right pane
 
3. Expand the Windows Client section and click on VSP to display cache settings
 

Make sure the Customize the cache sizes check box is not selected. With this not selected, NetBackup automatically determines the best VSP cache file sizes. In most cases, NetBackup will be able to create a large enough VSP cache file for backups if this is not selected.

If errors still occur with this not selected, it is possible to increase the initial VSP cache size and maximum VSP cache size manually. These settings vary depending on the client's requirements. Use caution when manually specifying sizes for the Initial and Maximum Cache Size, since these settings will be used regardless of volume size.

Refer the NetBackup System Administrator's Guide for more information on changing the configuration of VSP cache file sizes. If backups still abort with error status 156 after making changes to the VSP cache file size configuration, there may not be enough free disk space on the affected client. Free up as much disk space on the drives of the affected client as possible.

For Volume Shadow Copy (VSS)  (Windows 2003 and later versions of windows):
Use the following steps to increase the cache size when VSS is used on Windows 2003 Server clients.
 
1. In Windows, right-click My Computer and select Manage
 
2. In the console tree, right-click Shared Folders, select All Tasks, and then Configure Shadow Copies
 
3. Select the volume on which to make changes, and then click the Settings button
 
4. In the Settings dialog box, change the Maximum Size setting to either No Limit or a size large enough to suit the requirements of the installation and usage of VSS
저작자 표시
Posted by samaim
2012/01/04 10:56

Redhat Linux (RHEL) 서버에 YUM 설치 Server/Linux2012/01/04 10:56

1. 설치 패키지 얻기

http://dag.wieers.com/rpm/packages/yum/

wget http://dag.wieers.com/rpm/packages/yum/yum-2.4.2-0.4.el4.rf.noarch.rpm

http://rpmfind.net/linux/rpm2html/search.php?query=libsqlite&submit=Search+...&system=&arch=

wget ftp://rpmfind.net/linux/sourceforge/s/project/sk/skychart/OldFiles/libsqlite-3.2.1-1.i386.rpm

http://rpmfind.net/linux/rpm2html/search.php?query=python-elementtree&submit=Search+…&system=&arch=

wget ftp://rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/python-elementtree-1.2.6-7.el4.rf.i386.rpm

http://rpmfind.net/linux/rpm2html/search.php?query=python-sqlite&submit=Search+…&system=&arch=

wget ftp://rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/python-sqlite-0.5.0-1.2.el4.rf.i386.rpm

http://rpmfind.net/linux/rpm2html/search.php?query=urlgrabber&submit=Search+…&system=&arch=

wget ftp://rpmfind.net/linux/dag/redhat/el4/en/x86_64/dag/RPMS/python-urlgrabber-2.9.7-1.2.el4.rf.noarch.rpm


2. 패키지 설치

$rpm -ivh libsqlite-3.2.1-1.i386.rpm
$rpm -ivh python-elementtree-1.2.6-7.el4.rf.i386.rpm
$rpm -ivh python-sqlite-0.5.0-1.2.el4.rf.i386.rpm
$rpm -ivh python-urlgrabber-2.9.7-1.2.el4.rf.noarch.rpm
$rpm -ivh yum-2.4.2-0.4.el4.rf.noarch.rpm

python-sqlite-0.5.0-1.2.el4.rf.i386.rpm 설치시 이와 같은 에러가 나오면

# rpm -ivh python-sqlite-0.5.0-1.2.el4.rf.i386.rpm
error: Failed dependencies:
        libsqlite.so.0 is needed by python-sqlite-0.5.0-1.2.el4.rf.i386

sqlite-2.8.17-1.el4.rf.i386.rpm, sqlite-devel-3.3.6-0.3.el4.i386.rpm 패키지 설치 후 계속

http://rpmfind.net/linux/rpm2html/search.php?query=sqlite&submit=Search+...&system=&arch=

wget ftp://rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/sqlite-2.8.17-1.el4.rf.i386.rpm

http://rpmfind.net/linux/rpm2html/search.php?query=sqlite-devel&submit=Search+...&system=&arch=

wget ftp://rpmfind.net/linux/epel/4/i386/sqlite-devel-3.3.6-0.3.el4.i386.rpm

$rpm -ivh sqlite-2.8.17-1.el4.rf.i386.rpm
$rpm -ivh sqlite-devel-3.3.6-0.3.el4.i386.rpm


3. YUM Config ( /etc/yum.conf )

[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
tolerant=1
exactarch=1

[base]
name=CentOS-$releasever - Base
baseurl=http://mirror.centos.org/centos/4/os/i386/
gpgcheck=1

[updates]
name=Red Hat Linux $releasever - Updates
baseurl=http://mirror.centos.org/centos/4/updates/i386/
gpgcheck=1

4. Setup the Repository

http://dag.wieers.com/rpm/packages/rpmforge-release/

wget http://dag.wieers.com/rpm/packages/rpmforge-release/rpmforge-release-0.3.6-1.el4.rf.i386.rpm

$ rpm -ivh rpmforge-release-0.3.6-1.el4.rf.i386.rpm


5. Download and install the CentOS GPG Key

wget http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-4

# rpm –import RPM-GPG-KEY-CentOS-4

6. Yum update all packages

# yum update




저작자 표시
Posted by samaim


On CentOS 4 or Red Hat Enterprise Linux 4, you may get an error at startup that suggests an Apache problem.

The error looks like this: Starting httpd: Syntax error on line 6 of /etc/httpd/conf.d/auth_pgsql.conf: Cannot load /etc/httpd/modules/mod_auth_pgsql.so into server: libpq.so.3: cannot open shared object file: No such file or directory [FAILED]

This can result from installing Red Hat or CentOS with the wrong options. You can fix it by creating this symlink:

 ln -s /usr/lib/libpq.so.4 /usr/lib/libpq.so.3

 

저작자 표시
TAG httpd, pqsql
Posted by samaim