I'm using the Cisco Prime Infra:
Version : 22.214.171.124
Patch: Cisco Prime Network Control System Version: Update.4.16
Patch: Cisco Prime Network Control System Version: Update-1_12_for_version_1_3_0_20
And, I am receiving the infamous "Low space" messages. So, before execute the ncs cleanup, I am trying execute a NCS Server Backup. A few days ago, they changed the FTP server, and the old one isn't available anymore. On this new one, the job isn't working. The configuration seems to be OK, I don't know why it doesn't work, it's configured to use a ftp server, this is the repository configuration:
user F37113 password hash "hashed password"
BTW, connected through ssh to the PI, I have succefully tested the connection to the ftp site, and even uploaded a test file.
By executing the task with the "Execute now", or waiting for the schedule, the result on the GUI is the same: Unsuccessful: Please check your repository configuration.
|Start Time||End Time||Elapsed Time (Seconds)||Result||Message|
|2015-Feb-10, 15:51: BRST||2015-Feb-10, 15:47:56 BRST||10||Failure||Unsuccessful: Please check your repository configuration.|
Checking the logs I have this:
admin# show logging system tail
ADEOS Platform log:
Feb 10 16:51:25 br001vs0074 debugd: : logging: logutils_cli.c [admin]: Got cfg: Server localhost location /var/log/ade/ADE.log loglevel 6 islocal 1
Feb 10 16:51:25 br001vs0074 logger: warning:[backup-app.sh] application backup script did not backup any files.
Feb 10 16:51:25 br001vs0074 logger: warning:[backup-app.sh] backup file backup-20150210-0451.tar.gpg was not created as no application data exists for this backup
Feb 10 16:51:25 br001vs0074 debugd: : backup-restore:backup: br_backup.c [daemon]: appcomponent backup script failed
Feb 10 16:51:45 br001vs0074 debugd: : logging: logutils_cli.c [admin]: Got cfg: Server localhost location /var/log/ade/ADE.log loglevel 6 islocal 1
Feb 10 16:53:00 br001vs0074 debugd: : logging: logutils_cli.c [admin]: Got cfg: Server localhost location /var/log/ade/ADE.log loglevel 6 islocal 1
I'm lost, where is the problem?
TAC helped me resolve the same recently. I was trying to backup PI 2.2 in preparation for migrating to PI 3.0.
The problem is that even when the repository is remote and the target repository has plenty of free space, the backup is first staged locally. Lack of adequate local disk space was causing the backup to fail.
The TAC engineer was able to cleanup some temporary files used by Oracle to free up adequate local disk space. Once that was done, I was able to backup and migrate.
It was nothing you'd want to try without expert assistance - even as someone who knows PI pretty well it was a bit daunting.
I have done the ncs cleanup for PI 3.0, without stopping ncs
will it face any problem? and its an HA setup.
its been more than 2 hours now. its still Stopping server