GreenLake Administration
Operating System - HP-UX
1849154
Members
5655
Online
104041
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2010 09:12 PM
08-16-2010 09:12 PM
ignite
Hi,
We are taking the weekly ignite backup. Its growing so we facing the space problem on ignite server to take the image. Which are the maintaice work we can acrry out to reduce the ignite image size.
Regards,
Rkumar
We are taking the weekly ignite backup. Its growing so we facing the space problem on ignite server to take the image. Which are the maintaice work we can acrry out to reduce the ignite image size.
Regards,
Rkumar
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2010 09:18 PM
08-16-2010 09:18 PM
Re: ignite
Clean up your filesystems. Every cleanup on backupped filesystems will have impact on the size of your ignite backup.
For instance the patch-undo database (command: cleanup -c 1)
Or check out
- /root/.sh_history being large file or a directory containing LOTS of files
- /var/preserve (containing broken-of vi data, ready for recovery)
- /var/spool/mail
- /var/adm/wtmp
- /var/adm/syslog/*
You might also think about skipping some of these directories/files during the ignite backup. In most cases you're not interested in /var/preserve or /var/adm/syslog anyway on a ignite recovered filesystem...
For instance the patch-undo database (command: cleanup -c 1)
Or check out
- /root/.sh_history being large file or a directory containing LOTS of files
- /var/preserve (containing broken-of vi data, ready for recovery)
- /var/spool/mail
- /var/adm/wtmp
- /var/adm/syslog/*
You might also think about skipping some of these directories/files during the ignite backup. In most cases you're not interested in /var/preserve or /var/adm/syslog anyway on a ignite recovered filesystem...
Every problem has at least one solution. Only some solutions are harder to find.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2010 01:29 AM
08-17-2010 01:29 AM
Re: ignite
Do you have non OS specific items in vg00 ?
If so move them to there own filesystems.
HTH
Berd
If so move them to there own filesystems.
HTH
Berd
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP