Backup failed, not enough disk space for database

[federico_3]

/var/opt/omni is at 99% of the total space allocated for it .
what should i do? Should i increase it after stopping omni and then restarting it?


Thanks

Federico

[Alex Glennie]

Your options I think are :

Purge Obsolete restore data from database:

# /usr/omni/bin/omnidbcheck -purge #days

The above will purge obsolete(overwritten) backup sessions.
Also failed/aborted sessions.
This command can take many hours to run. I have seen some cases
its taken 24hours to complete. Only purge back a few days at a
time or run command frequently.

Purge Detail Catalog from database:

# /usr/omni/bin/omnidb -strip
If you combine this command with -session, list all sessionID's
in database. Combine with -session sessionID will delete all
objects(filesystems)backup up in this session.

Combine with with #days -filesystem filesystemID, all versions
of the specified filesystem older that #days are deleted from the database.

To Shrink the size of database file:

# /usr/omni/bin/omnidbcheck -info

This command to see how many records are used and how many are
occupied by data. If the numbers vary considerably, it is feasible to shrink the database.


# /usr/omni/bin/omnidbcheck -writeascii DIRECTORY_NAME -full

The above to copy the database to a empty directory on system;

DIRECTORY_NAME, as ascii files.


# /usr/omni/bin/omnidbcheck -readascii DIRECTORY_NAME -full

Use the above to read the database back from ascii files
into /usr/omni/config/db directory

See "Openview Omniback II Admin Guide" page 7-4
Managing Growth of database

Also see man pages for omnidbcheck(1M) and omnidb(1M)

[Dan Hetzel]

Hi Frederico,

The size of /var/opt/omni can be safely increased once the Omniback daemon has been stopped.

I did it many times with different clients because they usually under-estimate /var/opt/omni. We all do, don't we ? ;-)

Best regards,

Dan