03-06-2006 08:38 AM - edited 03-13-2019 12:25 PM
4.0.7 would archive successfully to tape but 4.0.9 puts the following in the log:
[09:16:47 AM] Successfully backed up Cisco CallManager on 192.168.0.251.
[09:16:48 AM]
[09:16:48 AM] Staging complete. Size of staging directory is 184MB.
[09:16:48 AM] Building archive on Tape.
[09:16:49 AM]
[09:17:22 AM] [Error] Could not build archive successfully.
Any ideas?
03-06-2006 09:06 AM
There is a bug filed on this issue:
CSCsd25578.
This bug is viewable on Cisco.com with login.
The current workaround for the bug is the following:
Workaround:
1. Use Local or remote location for backups instead tape.
2. If required to use tape, ignore the message "Could not build archive successfully" and
open the windows task manager and under the processes tab, check "Tar.exe" running. Wait
for to get it completed. Backup will be created successfully on tape as well.
FYI, tar is successfully getting created on tape. It is only progress bar error which
gives this wrong status due to 'overflow' error. AND user has to wait till tar completes
its operation on tape (given in workaround). "Could not build archive successfully.",
this message can be ignored for the time being for the tape backups.
03-06-2006 10:17 AM
Thanks for the response. I'll look into the bug report.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide