ADSM-L

Re: [ADSM-L] tsm for ve, nfs datastores and cbt

2015-01-15 10:13:27
Subject: Re: [ADSM-L] tsm for ve, nfs datastores and cbt
From: Matthew McGeary <Matthew.McGeary AT POTASHCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Jan 2015 09:11:57 -0600
Lee,

The VMWare documentation is a bit confusing, but it appears that while NFS datastores may support CBT, they don't support it fully.  Any backup software that leverages the VMWare APIs for backup will have the same issue as TSM for VE when backup is initiated on a VM that's stored on a NFS datastore.  In order to perform incremental-style backups on VMs stored on an NFS datastore, you'd need something like VEEAM, which has its own changed-block-tracking mechanism and doesn't leverage the VMWare API for that purpose.

__________________________

Matthew McGeary
Technical Specialist - Operations
PotashCorp
T: (306) 933-8921
www.potashcorp.com





From:        "Lee, Gary" <glee AT BSU DOT EDU>
To:        ADSM-L AT VM.MARIST DOT EDU
Date:        01/15/2015 08:14 AM
Subject:        [ADSM-L] tsm for ve, nfs datastores and cbt
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>





We are running vmware 5.1, using tsm for ve 6.4.2, and using nfs data stores.
It appears that change block tracking does not work with tsm for ve on nfs data stores.
This is forcing full backups every night.
Our environment is currently over 14 tB and growing.
With this limitation, we will not be able to continue using tsm for ve.

Have any on the list encountered this situation, and if so, have you found a work around?

Further information is here.
http://www-01.ibm.com/support/docview.wss?uid=swg21681916

<Prev in Thread] Current Thread [Next in Thread>