cms backup

[Klees]

I am stuck on what I need to enter during my monthly back up wher it says:

Please lable the back up tape...

#...

anyone? thanks

 

[Klees]

From what I can tell the back up was completed. I can get to the log and see:

finished back up Thur April ...

this is my first time running this, can I assume this was successful? I expected it to take longer. Thanks

 

[inerguard]

How long did it take?

The log should look like: -

2600 2/15/09 2:37 AM 2 1 INFO
ARCHIVER status: Weekly Archive for week (Sun) Feb. 08, 2009
through (Sat) Feb. 14, 2009 Successful





[Started on Version 3 software 15 years a go]

 

[4merAvaya]

There are 2 different CMS backups: cmsadm, which backups up the UNIX OS but not the CMS data (/cmsadm, option 3). and the cms maintenance backup, which backs up the CMS data (From the main menu choose maintenance, then backup, run). The cmsmaint backups can be scheduled to run automagically as long as there is a tape in the drive.

The cmsadm backup should be done monthly at a minimum. The cmsmaint should be done daily.

The labeling information is just for you to keep track of what backup is on what tape.

Kevin

 

[Stinney]

Assuming you are talking about the CMSADM backup?

Mine only takes 8 minutes on a new v890. Used to take 30 min on the old Sunblade 150.

If it's telling you to label the tape and you have the # prompt you're all set.

Otherwise, you should get an error message. For example:

cpio: Cannot read "opt/informix/lib/sqlexec", errno 5, I/O error
1 errors
Request failed. See /cms/install/logdir/backup.log for more information.
/cms/install/bin/backup[25]: test: argument expected

Of course, checking the log doesn't hurt.


- Stinney

Favorite all too common vendor responses: "We've never seen this issue before." AND "No one's ever wanted to use it like that before.

 

[Klees]

I ran the cmsadm back up (opt 3). It probably took 10 min max. I assumed this was the montly back up I needed to do, the daily is scheduled. I read that it could take 4 hours I think that is where I got concerned. thanks

 

[Stinney]

4 hours is probably in regards to the Full Maintenance Backup, which is dependent on the amount of historical data involved and the system.

Ours takes an hour and 15 minutes. It used to take 2 and 1/2 with the same amount of data on a Sunblade 150.

- Stinney

Favorite all too common vendor responses: "We've never seen this issue before." AND "No one's ever wanted to use it like that before.