Error Bpduplicate Socket Read Failed
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom netbackup socket read failed errno = 62 - timer expired Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français netbackup socket read failed 23 Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Optimized duplication error 13 Article:000086378 Publish: Article
Read From Input Socket Failed 636 Netbackup
URL:http://www.veritas.com/docs/000086378 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe
Exited With Status 23 Socket Read Failed
Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Optimized duplication failed with error 13 after a fixed period of time, in this case, it is always 2 hours. Error Message Job details: 09/05/2012 05:35:25 - Error bpduplicate (pid=19559) socket read failed: errno = 110 netbackup error code 24 - Connection timed out09/05/2012 05:35:25 - Error bpduplicate (pid=19559) host mediasvr1 backup id clien1_1346706905 optimized duplication failed, file read failed (13). Cause Firewall terminates the idle/inactive TCP socket between the master server and media server. Solution 1) If possible, change the firewall setting to a higher value so that it won't terminate the TCP socket. In most environment, it is set to 2 hours. 2) In most situations, however, customer may not be able to change firewall setting due to their company policy. To workaround this, reduce the TCP keepalivetime value of master server. In this case, it is also set to 2 hours, which matches the timeout and failure happens. OS_config.txt:net.ipv4.tcp_keepalive_time = 7200 sysctl -w net.ipv4.tcp_keepalive_time = 900 (for permanent change, refer to http://www.starquest.com/Supportdocs/techStarLicense/SL002_TCPKeepAlive.shtml) Subsequent duplication that takes more than 2 hours will continue until completion instead of timing out and failing.Applies ToNetbackup 7.x Unix master server Windows media servers with OpenStorage setup NOTE: This issue can also be seen between any Optimized Duplication between MSDP, PDDO or 52xx Appliance-type of media servers. Terms of use for this information are
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom
Netbackup Error Code 25
Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français bpclntcmd Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet General Error: Status code 23, socket read failed, during client backups or restores, or when loading client properties. Article:000090314 Publish: Article URL:http://www.veritas.com/docs/000090314 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a https://www.veritas.com/support/en_US/article.000086378 Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem General Error: Status code 23, socket read failed, during client backups or restores, or when loading client properties. Error Message Status code 23, socket https://www.veritas.com/support/en_US/article.TECH57100 read failed Cause The keyfile.dat file in the
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/symantec-netbackup-18/bpduplicate-socket-read-failed-98043/ Central Forums Forum Index » Symantec NetBackup » bpduplicate socket read failed https://adsm.org/lists/html/Veritas-bu/2009-05/msg00118.html The time now is Mon Oct 10, 2016 5:24 am View previous topic | View next topic Page 1 of 1 bpduplicate socket read failed Author Message loh Joined: 14 Jul 2008 Posts: 18 bpduplicate socket read failed Hi folks, My setup enviroment NetBackup Enterpriese 6.5.3 on W2K3 socket read SP2 Backing up to SATA disk and staging to LTO4-FC daily I am using Basic Disk Staging with schedule, but the staging to tape was partially successful with below error messages. What could be the real causes and how to rectify it. Thanks in advance. 07:06:12 - Error bpduplicate (pid=3640) socket read failed: errno = 10054 - An existing socket read failed connection was forcibly closed by the remote host. 05/09/2009 07:11:12 - Error bptm (pid=2104) Could not open file Global\NetBackup Media Manager SHM Info Path
singnet.com DOT sg> To: veritas-bu