Ruud,
After all, the fact that a file is modified does not mean that the entire
file has changed (meaning that all CBT blocks need to be backed up).
Regarding this statement, when you open, edit and save an office file (for
example) it rewrites the entire thing to disk, even if you edit or add a
It may be worth reading this VMware article about how CBT works - I can't
comment on your particular case since you didn't provide any information
about your infrastructure, but there are dependencies such as:
- Virtual hardware version
- ESX version
- type of storage (VMFS, RDM, etc.)
-
Hi Stefan,
Thanks for the tip. We indeed didn't exclude the swap file. We will improve our
configuration.
But for the comparison it was included in listing the modified files as in the
backup made.
If the entire file was changed, we expect that the modified files and the
backup were the same
We are migrating our TSM infrastructure to DHCP assignments for the client
nodes/servers. Up until no everything seems to have worked OK.
Now we moved a bunch of CIFS backups to DHCP and having problems logging in
to an administrator ID via the WEB client on the box.
Every attempt to login
Hi,
Compare q no f=d output of the node with the current ip address of that
node. Some of the registered ip's of that node might have not been updated.
Having dhcp enabled on your backup clients and having them switch ips
constantly will cause issues for tsm server to tsm client communications
