cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
667
Views
0
Helpful
1
Replies
Highlighted

Back up Collection Manager

Hi,

Has anyone encountered some problem on backing up the Cisco Collection Manager. We will be upgrading the firmware of our SCE8000 from 3.6.5 to 3.8.x, and need to upgrade also the Collection Manager. We are encountering the error below when backing up:

-bash-3.2$ locate sybback.sh

/opt/CM/scripts/sybback.sh

-bash-3.2$ /opt/CM/scripts/sybback.sh -d /home/jsoriano

/opt/CM/scripts/sybback.sh: line 19: ~sybase/SYBASE.sh: No such file or directory

Error - cannot import Sybase definitions - exiting

-bash-3.2$

Is there any exact procedure on backing up the system or databse of the Collection Manager.

Thanks,

Bryan

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Hi Brian,

It seems like the sybback.sh script is trying to use a file which cannot be found in your system. The file is

~sybase/SYBASE.sh.

I understand that you are using here a bundled distribution of CM (using Sybase DB). Is that correct? If so, can you try to locate SYBASE.sh file in the server? Perhaps the script is referring to a wrong location and that's why it's failing. It could also be a permission problem.

The procedure to backup the CM DB may depend on the type of DB being used. For external DB, you may need rely on the DB capabilities to backup.

In any case, a CM upgrade shouldn't normally need a DB backup. During the upgrade process the DB structures is upgarded and the data is adapted to the new structure. You can find the upgrade procedure to 3.8.x here:

http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel38x/cmug/Installing_the_Collection_Manager.html#wp1064529

As you can see, there is no mention of DB backup needed for the upgrade procedure. Also, take into account that an upgrade from 3.6.5 to 3.8.x cannot be done directly. To upgrade from Version 3.6.x or earlier, you must first upgrade to Version 3.7.x.

You can always backup your DB if you want, of course.

Regadrs

View solution in original post

1 REPLY 1
Highlighted
Cisco Employee

Hi Brian,

It seems like the sybback.sh script is trying to use a file which cannot be found in your system. The file is

~sybase/SYBASE.sh.

I understand that you are using here a bundled distribution of CM (using Sybase DB). Is that correct? If so, can you try to locate SYBASE.sh file in the server? Perhaps the script is referring to a wrong location and that's why it's failing. It could also be a permission problem.

The procedure to backup the CM DB may depend on the type of DB being used. For external DB, you may need rely on the DB capabilities to backup.

In any case, a CM upgrade shouldn't normally need a DB backup. During the upgrade process the DB structures is upgarded and the data is adapted to the new structure. You can find the upgrade procedure to 3.8.x here:

http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel38x/cmug/Installing_the_Collection_Manager.html#wp1064529

As you can see, there is no mention of DB backup needed for the upgrade procedure. Also, take into account that an upgrade from 3.6.5 to 3.8.x cannot be done directly. To upgrade from Version 3.6.x or earlier, you must first upgrade to Version 3.7.x.

You can always backup your DB if you want, of course.

Regadrs

View solution in original post