How to setup a Flashbackup-Windows policy on Linux for NTFS?

[brant]

Hello,

Em..., I have several question about it.

Question 1:

Since the guide is so complicated, and I am just going to setup a Flashbackup-Windows policy on Linux for NTFS。
Does someone can share steps-by-steps with me?
Thank you very much.


Question 2 (Important to ME):

Actually, I have had a try.
Environment:
  Master/Media/Client:  RedHat 53, NBU6.5
  Client: Windows Server Standard Edition 2003R2 SP2.
  Policy Type: Flashbackup-Windows
  Snapshot Option: AUTO
  Schedule: Full Backup
  Backup Selection: \\.\F:
The backup/restore jobs finished successfully.

But if the "backup selection" is \\.\F:\tmp
The backup job failed.

Does Flashbackup-Windows not support backup directory path on drivers?


Question 3:
When I only have a Windows 2003 system as a NBU client, without such as VxMS, VxVM installed on it, 
What kind of Flashbackup-Windows I can do ?
In otherwords, I mean what the Snapshot Options I can use.


Question 4:
I konw FlashBackup-Windows is for Windows system, FlashBackup used in UNIX/Linux.
Does someone can tell me the differences between them?
It seems in below scenario, they are same:
Policy Type is FlashBackup-Windows, snapshot is VSS, client is Windows system
Policy Type is FlashBackup,                    snapshot is VSS, client is Windows system.


OK.
Waiting you exports reponses.
Appreciate!

-BR/Brant.

[Anton_Panyushki · Accepted solution]

1 & 2. When creating FlashBackup-Windows policy use backup the entire volume (even free space). Hence:
\\.\F: - correct selection list
\\.\F:\tmp - wrong selection list (status code 11 is normal in this case).

3. You need a spanshot provider to implement Flashbackup.  In case of Wintel clients you 've got 2 options.  МЫЗ - shipped with NetBackup Advanced client. Used for win2000 and win2003 clients flashbackup. VSS - built in win2003 feature - used for w2003 clients only.
In short: МЫЗ is for win2000 and VSS is for win2003.

4. FlashBackup is for Unix clients and FlashBackup-Windows is for Wintel clients. They are not officially interchangeble.

 

[brant]

Thank you Anton!