Hi All,
Following to IBM's decision to withdraw the web GUI in the latest versions of
their clients (thus making NDMP hardly usable), as well as to the renewal of
our NAS infrastructure (now using Netapp), I'm trying to implement netapp
snapdiffs in our shop.
So far we succeeded in defining
Hi Arnaud,
>> ... there's still the limitation that this GUI will be usable only once
logged on the machine hosting the Spectrum Protect client
What do you mean by "that machine"?
The Backup-Archive client is not in the data path for an NDMP backup or
restore. The data path is between the
Zoltan,
If I understood well, your storage is Isilon based : in this case do not even
think of using CONTAINER pools, as performance will be horrible.
Not much time to talk about this, but to make a very long story short, we are
about to dump/trash /resell the brand new Isilon arrays we bought
Oh, and don't forget that your server requires a significant amount of CPU's
when switching to container pools since all deduplication and compression is
done inline during your backup window. So when you want to switch in place from
file to container, make sure your server has enough cores
Brion:
Here at Cornell, we have a TSM client on a Linux system backing up NFS shares
via NFS mounts and snapdiff differentials - and have been doing so for years.
First, the gory details:
- For TSM
TSM Client Version 7, Release 1, Level 6.0 (*red faced, thought I had upgraded
to SP 8.1.2.0
Hi Arnaud,
Not related to SnapDiff ... but just some info on NDMP and B/A Client...
In Spectrum Protect BA client 8.1.6 that GAs this coming Friday (21
September) you will be able to use the native Java GUI to handle NDMP
backups/restores.
Del
Hi Del,
Thanks for the information, which I got as well thru other channels (IBM
support), but there's still the limitation that this GUI will be usable only
once logged on the machine hosting the Spectrum Protect client.
This means that I will be forced to grant some of my colleagues (which
Don't forget backupsets, you will lose them too with containerpools.
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Solomon Miler
Sent: dinsdag 18 september 2018 16:11
To:
Thanks for the tip. Should not be an issue for us since this will be on
the Replication Target server only - for now.
On Tue, Sep 18, 2018 at 10:14 AM Solomon Miler
wrote:
> Dedup containers do not support 'migrate / export / move node '.The
> only way to get rid of data : expire /
Thanks for the tip. Should not be an issue for us since this will be on
the Replication Target server only - and we don't use backupsets.
On Tue, Sep 18, 2018 at 10:24 AM Loon, Eric van (ITOPT3) - KLM <
eric-van.l...@klm.com> wrote:
> Don't forget backupsets, you will lose them too with
Well, if you run out of space, options nearly always were to move data to
LTO, now options are to buy an expansion to an existing storage array, which
cost slightly more than lto.
-Original Message-
From: ADSM: Dist Stor Manager On Behalf Of Zoltan Forray
Sent: Tuesday, September
That space movement issue is our biggest concern - especially since this
server is maxed-out on ISILON storage (no where to grow) and to even think
of converting to container would be an ordeal. No possibility of tape or
expanding disk.
On Tue, Sep 18, 2018 at 10:38 AM Solomon Miler
wrote:
>
Hello Arnaud, maybe it would be: The NetApp snapshot indicates which files are
modified on the LUN (for which their backup is triggered); but the
Backup-Archive client cannot "take" them because they are locked by the
application.
Perhaps you can solve by inserting the appropiate rules in
Container pools work but you don't have defrag functionality until 8.1.4 -
which means it does not release the space it no longer uses.
Also you don't get much if any benefit from dedup if you commingle 2 or
more container pools into one on the replica.
For example you have 2 servers doing
Dedup containers do not support 'migrate / export / move node '.The only
way to get rid of data : expire / delete node.
We are on 8.1.1.0
Solomon Miler
Senior Data Protection Engineer, VP
--
Desk: 201.577.313
Cell : 917.287.2332
We are investigating using CONTAINER pools for our offsite replica server
vs the current FILE method which is killing us with the constant dedup,
reclaims, etc.
So, what are the "gotchas' ? We are still at V7.1.7.400 so I figure we
will have to do without any new features added in the V8
Hi Tommaso,
The backup command I'm using (dsmc i /Airwarder -snapdiff -snapdiffhttps
-diffsnapshotname="daily.*" -diffsnapshot=latest -useexistingbase
-optfile=dsm_netapp.opt) includes the "useexistingbase" statement.
Based on my understanding of the documentation, this means that the S.P.
17 matches
Mail list logo
