|
I've heard of people who despite the lack of BRMS, the lack of IBM i save
commands, the lack of IPL D, still went with solutions like Commvault. It
was cheaper. Some of these people have since decided that maintaining
their own system was not their business plan and moved to cloud managed IBM
i solutions.
We're using EMC Data Domain's. We're on our second generation of such.
Quite happy. We run them with BRMS but could do IBM i save commands if
needed. I have done full system restores, including IPL from "tape",
multiple times. Normally during system migrations. Another chunk of the
Data Domains is being used by IBM Storage Protect for tiered storage. This
is how our Windows PC's and servers are saved. I often have four LPARs of
IBM i doing full system saves simultaneously to the same Data Domain. Each
with four drives in parallel.
One of those lpars:
% of Size in
Description Disk 1,000,000 bytes
User libraries 44.81 5131858.74
User directories .74 84910.31
Folders and documents .00 .92
QSYS .05 5393.92
Other IBM libraries .47 53427.56
Licensed Internal Code .03 3499.85
Temporary space 1.54 175997.64
Unused space 52.19 5977838.67
System internal objects .10 11516.51
Objects not in a library .00 .02
QTEMP libraries .00 285.56
TOTAL 99.93 11444729.70
Display BRM Log Information
Date sent Time sent Message
3/09/24 7:12:39 Begin processing for control group DTFULL type *BKU.
3/09/24 7:13:27 Starting SAVSYS to devices USSI7VTL
3/09/24 7:17:00 SAVSYS is complete.
3/09/24 7:17:00 Starting *IBM backup, type *FULL.
3/09/24 7:17:54 Backup *IBM, type *FULL complete.
3/09/24 7:17:54 Starting *ALLUSR backup, type *FULL.
3/09/24 9:44:54 Backup *ALLUSR, type *FULL complete.
3/09/24 9:44:55 Starting save of list *LINK to devices *MEDDFN.
3/09/24 9:46:16 223596 objects saved.
3/09/24 9:46:34 Save of list *LINK complete.
3/09/24 9:46:50 Control group DTFULL type *BKU processing is complete.
Another LPAR (heavily IFS - multiple Domino servers)
% of Size in
Description Disk 1,000,000 bytes
User libraries 2.72 70170.91
User directories 61.87 1594250.30
Folders and documents .00 .11
QSYS .36 9168.05
Other IBM libraries 1.20 30835.20
Licensed Internal Code .10 2503.44
Temporary space .91 23488.66
Unused space 32.54 838473.71
System internal objects .01 351.41
Objects not in a library .00 .02
QTEMP libraries .00 25.88
TOTAL 99.71 2569267.69
Display BRM Log Information
3/09/24 7:53:07 Begin processing for control group DTFULL type *BKU.
3/09/24 7:53:54 Starting SAVSYS to devices USSI7VTL.
3/09/24 7:57:28 Save System (SAVSYS) command has completed processing.
3/09/24 7:57:28 SAVSYS is complete.
3/09/24 7:57:29 Starting *IBM backup, type *FULL.
3/09/24 7:58:14 Backup *IBM, type *FULL complete.
3/09/24 7:58:14 Starting *ALLUSR backup, type *FULL.
3/09/24 7:59:31 Backup *ALLUSR, type *FULL complete.
3/09/24 7:59:32 Starting save of list *LINK to devices *MEDDFN.
3/09/24 8:23:09 369695 objects saved.
3/09/24 8:23:43 Save of list *LINK complete.
3/09/24 8:23:46 Control group DTFULL type *BKU processing is complete.
On Thu, May 30, 2024 at 6:17 PM Evan Harris <auctionitis@xxxxxxxxx> wrote:
Hi guysi.
I am working with some people that are exploring VTL options for the IBM
There are a couple of strong options on the table (FalconStore andlist
Cybernetics) but there are a few others floating around that people are
looking at. I've used DSI and EMC Data Domain in the past.
One that has come up is CommVault.but that is a completely
unknown quantity to me in the i space and the documentation is lacking in
some detail.
Has anyone else done any work with CommVault or used it in anger ?
The lines for me are that if it does not support BRMS, native IBM i save
commands and ALT-D IPL it doesn't get out of the box.
Anyone got any thoughts or comments ? Feel free to go into bat for your
favourite VTL solution even if you can't comment on CommVault!
--
Regards
Evan Harris
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
